| could not remove module [message #207770] |
Wed, 30 January 2008 07:30  |
Eclipse User |
|
|
|
Originally posted by: adam.hardy.no.spam.cyberspaceroad.spam
Hi All
I have an issue with org.eclipse.jst.server.tomcat.core which throws this error
everytime I restart my server - "could not remove module"
Also org.eclipse.wst.server.core tells me: "Error calling delegate restart()
Tomcat v6.0 Server at localhost"
I have checked all I can think of, including reconstructing my dynamic web
project from scratch.
This is some of my config that might be relevant:
- I have other projects in my J2EE Module Dependencies
- I set 'use tomcat installation' for the server location
- I set 'serve modules without publishing'
Here's the stack trace (which gives me no clue about the problem module):
java.lang.NullPointerException
at java.io.File.<init>(File.java:194)
at
org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishJar(TomcatServerBehaviour.java:331)
at
org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishModule(TomcatServerBehaviour.java:270)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModule(ServerBehaviourDelegate.java:749)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModules(ServerBehaviourDelegate.java:835)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blish(ServerBehaviourDelegate.java:669)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:887)
at org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:874)
at
org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:72)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I am using WTP 2.0.1 in Eclipse 3.3.1.1 with apache-tomcat-6.0.13.
Thanks
Adam
|
|
|
| Re: could not remove module [message #207816 is a reply to message #207770] |
Wed, 30 January 2008 13:17  |
| Eclipse User |
|
|
|
Hi Adam,
With all the versions of Tomcat, all the combinations of options, and
various workspace scenarios, it's challenging to cover all the
possibilities. You have managed to hit one I missed. In my testing, I
typically tested "Serve modules without publishing" disabled first and
then used the same workspace to test with that option enabled. That
scenario avoids the problem.
You should be able to avoid this issue by turning off "Serve modules
without publishing", publish the server once, turn "Serve modules
without publishing" back on, and publish again. On the second publish,
the previously published modules will be removed. It is in an incorrect
attempt to perform this removal that the NPE occurs. You will need to
repeat this each time you add a new project to the server.
I have already entered a Bug[1] for this NPE, where you can find a
little more detail. Feel free to add yourself as a CC if you are
interested in progress fixing it in WTP 3.0. If using the workaround
above gets too annoying, it would not be that difficult to patch the
tomcat.core plug-in to add a null pointer check. It would be a number
of steps, but all are pretty straight forward.
Cheers,
Larry
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=217131
adam hardy wrote:
> Hi All
>
> I have an issue with org.eclipse.jst.server.tomcat.core which throws
> this error everytime I restart my server - "could not remove module"
>
> Also org.eclipse.wst.server.core tells me: "Error calling delegate
> restart() Tomcat v6.0 Server at localhost"
>
> I have checked all I can think of, including reconstructing my dynamic
> web project from scratch.
>
> This is some of my config that might be relevant:
>
> - I have other projects in my J2EE Module Dependencies
> - I set 'use tomcat installation' for the server location
> - I set 'serve modules without publishing'
>
> Here's the stack trace (which gives me no clue about the problem module):
>
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:194)
> at
> org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishJar(TomcatServerBehaviour.java:331)
>
> at
> org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishModule(TomcatServerBehaviour.java:270)
>
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModule(ServerBehaviourDelegate.java:749)
>
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModules(ServerBehaviourDelegate.java:835)
>
> at
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blish(ServerBehaviourDelegate.java:669)
>
> at
> org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:887)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:874)
> at
> org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:72)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
>
> I am using WTP 2.0.1 in Eclipse 3.3.1.1 with apache-tomcat-6.0.13.
>
> Thanks
> Adam
|
|
|
| Re: could not remove module [message #207833 is a reply to message #207816] |
Thu, 31 January 2008 15:47 |
| Eclipse User |
|
|
|
Originally posted by: adam.hardy.no.spam.cyberspaceroad.spam
Thanks Larry.
No problem, I just work on one project, so I won't be removing or adding
projects. Hopefully :)
All the best
Adam
Larry Isaacs on 30/01/08 18:17, wrote:
> Hi Adam,
>
> With all the versions of Tomcat, all the combinations of options, and
> various workspace scenarios, it's challenging to cover all the
> possibilities. You have managed to hit one I missed. In my testing, I
> typically tested "Serve modules without publishing" disabled first and
> then used the same workspace to test with that option enabled. That
> scenario avoids the problem.
>
> You should be able to avoid this issue by turning off "Serve modules
> without publishing", publish the server once, turn "Serve modules
> without publishing" back on, and publish again. On the second publish,
> the previously published modules will be removed. It is in an incorrect
> attempt to perform this removal that the NPE occurs. You will need to
> repeat this each time you add a new project to the server.
>
> I have already entered a Bug[1] for this NPE, where you can find a
> little more detail. Feel free to add yourself as a CC if you are
> interested in progress fixing it in WTP 3.0. If using the workaround
> above gets too annoying, it would not be that difficult to patch the
> tomcat.core plug-in to add a null pointer check. It would be a number
> of steps, but all are pretty straight forward.
>
> Cheers,
> Larry
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=217131
>
> adam hardy wrote:
>> Hi All
>>
>> I have an issue with org.eclipse.jst.server.tomcat.core which throws
>> this error everytime I restart my server - "could not remove module"
>>
>> Also org.eclipse.wst.server.core tells me: "Error calling delegate
>> restart() Tomcat v6.0 Server at localhost"
>>
>> I have checked all I can think of, including reconstructing my dynamic
>> web project from scratch.
>>
>> This is some of my config that might be relevant:
>>
>> - I have other projects in my J2EE Module Dependencies
>> - I set 'use tomcat installation' for the server location
>> - I set 'serve modules without publishing'
>>
>> Here's the stack trace (which gives me no clue about the problem module):
>>
>> java.lang.NullPointerException
>> at java.io.File.<init>(File.java:194)
>> at
>> org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishJar(TomcatServerBehaviour.java:331)
>>
>> at
>> org.eclipse.jst.server.tomcat.core.internal.TomcatServerBeha viour.publishModule(TomcatServerBehaviour.java:270)
>>
>> at
>> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModule(ServerBehaviourDelegate.java:749)
>>
>> at
>> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blishModules(ServerBehaviourDelegate.java:835)
>>
>> at
>> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.pu blish(ServerBehaviourDelegate.java:669)
>>
>> at
>> org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:887)
>> at
>> org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:874)
>> at
>> org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:72)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>> I am using WTP 2.0.1 in Eclipse 3.3.1.1 with apache-tomcat-6.0.13.
>>
>> Thanks
>> Adam
|
|
|
Powered by
FUDForum. Page generated in 0.02922 seconds
Home