Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Unexpected context restarts
Unexpected context restarts [message #661613] Fri, 25 March 2011 10:59 Go to next message
Julien  Flotté is currently offline Julien Flotté
Messages: 8
Registered: March 2011
Junior Member
Hi everyone,

I face a problem with the configuration of my server.

I'm using Tomcat 6.0 with an web application made with Cocoon's framework.

With the old version of Eclipse (Galileo), when I run the server. I could change dynamically my resources without automatically restart context. I didn't loose my session and everything was alright. I just needed to restart the context when I changed the Java code.

But now, with the new version (Helios), whatever the change I do, the context always restart. And sometime, the restart of the context is wrong : I can see a "ClassNotDefFound" exception thrown. In this case, a clean action is neccessary in order to run the application without problems.

Is there an option existing in Eclipse that can solve my problem ?

Cordialy,
Julien.
Re: Unexpected context restarts [message #661627 is a reply to message #661613] Fri, 25 March 2011 11:27 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 3/25/2011 10:59 AM, Julien lott wrote:
> Hi everyone,
>
> I face a problem with the configuration of my server.
>
> I'm using Tomcat 6.0 with an web application made with Cocoon's framework.
>
> With the old version of Eclipse (Galileo), when I run the server. I
> could change dynamically my resources without automatically restart
> context. I didn't loose my session and everything was alright. I just
> needed to restart the context when I changed the Java code.
>
> But now, with the new version (Helios), whatever the change I do, the
> context always restart. And sometime, the restart of the context is
> wrong : I can see a "ClassNotDefFound" exception thrown. In this case, a
> clean action is neccessary in order to run the application without
> problems.
>
> Is there an option existing in Eclipse that can solve my problem ?
>
> Cordialy,
> Julien.

Which version of WTP are you using?

WTP will internally generate a MANIFEST.MF for utility projects to
ensure it contains appropriate dependencies. There was checking in
Galileo to prevent this internally generated MANIFEST.MF from making the
utility project appear to need rebuilding for every publish to the
server. This checking was inadvertently removed in WTP 3.2 and I
believe restored in WTP 3.2.2. Rebuilding of a utility jar in every
publish would trigger this kind of behavior in Tomcat.

Cheers,
Larry
Re: Unexpected context restarts [message #661639 is a reply to message #661627] Fri, 25 March 2011 12:21 Go to previous messageGo to next message
Julien  Flotté is currently offline Julien Flotté
Messages: 8
Registered: March 2011
Junior Member
I'm using the following version of WTP in Eclipse Helios :

Eclipse Web Developer Tools

Version: 3.2.2.v201008100100-7O7CFbKEMf84nUlEJyX7-SPQjhYZ

Do you want any other information to help ?

In Eclipse Galileo, I think that the version 3.1 is used.

Do you still think that my problem is linked to MANIFEST.MF ?

Thanks for your response,
Julien.
Re: Unexpected context restarts [message #661857 is a reply to message #661613] Mon, 28 March 2011 05:19 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 25/03/2011 15:59, Julien lott ha scritto:
> But now, with the new version (Helios), whatever the change I do, the
> context always restart. And sometime, the restart of the context is
> wrong : I can see a "ClassNotDefFound" exception thrown. In this case, a
> clean action is neccessary in order to run the application without
> problems.

Unfortunately, this problem in publishing (resources not published,
"NoClassDefFound" errors...) frequently happens to my team members too
and it also happened to me some times. There must be some bug in the
publishing code, but I couldn't reproduce it in a reproducible way in
order to open a bug report :-(

Mauro.
Re: Unexpected context restarts [message #661874 is a reply to message #661613] Mon, 28 March 2011 07:34 Go to previous messageGo to next message
Julien  Flotté is currently offline Julien Flotté
Messages: 8
Registered: March 2011
Junior Member
Thanks for your reply,

It's seems that we have the same problem. I have found no way to reproduce it.

Do you think that the problem is linked to the checking of MANIFEST.MF like Larry ? If it's a code publishing problem, is there anything we could do to solve it ?

Cordialy,
Julien.
Re: Unexpected context restarts [message #661905 is a reply to message #661874] Mon, 28 March 2011 09:37 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 28/03/2011 13:34, Julien lott ha scritto:
> Do you think that the problem is linked to the checking of MANIFEST.MF
> like Larry ? If it's a code publishing problem, is there anything we
> could do to solve it ?

If I understood it right, the checking of the MANIFEST.MF could be the
cause of the publishing occuring when not needed, while I don't know
what the source of the problem that makes the published webapp to be
corrupted could be.
Maybe Larry can help us suggesting some trials we may do to try to
reproduce...

Mauro.
Re: Unexpected context restarts [message #661919 is a reply to message #661905] Mon, 28 March 2011 10:13 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 3/28/2011 9:37 AM, Mauro Molinari wrote:
> Il 28/03/2011 13:34, Julien lott ha scritto:
>> Do you think that the problem is linked to the checking of MANIFEST.MF
>> like Larry ? If it's a code publishing problem, is there anything we
>> could do to solve it ?
>
> If I understood it right, the checking of the MANIFEST.MF could be the
> cause of the publishing occuring when not needed, while I don't know
> what the source of the problem that makes the published webapp to be
> corrupted could be.
> Maybe Larry can help us suggesting some trials we may do to try to
> reproduce...
>
> Mauro.

It turns out Bug 326456 wasn't fixed until WTP 3.2.3[1]. Are either of
you seeing this behavior with that version?

With respect to seeing odd behavior after a context restart, I think the
first step will be to determine if restarting the server fixes the
behavior. If it does, it suggests that publishing was successful, and
the restart is having some problem picking up all the changes that got
published.

Cheers,
Larry

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=326456
Re: Unexpected context restarts [message #661949 is a reply to message #661613] Mon, 28 March 2011 11:09 Go to previous messageGo to next message
Julien  Flotté is currently offline Julien Flotté
Messages: 8
Registered: March 2011
Junior Member
I'm installing the version 3.23 of WTP.

I'll let you know the impact on publishing when I have tested.

Cheers,
Julien.
Re: Unexpected context restarts [message #662648 is a reply to message #661919] Thu, 31 March 2011 08:31 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 28/03/2011 16:13, Larry Isaacs ha scritto:
> With respect to seeing odd behavior after a context restart, I think the
> first step will be to determine if restarting the server fixes the
> behavior. If it does, it suggests that publishing was successful, and
> the restart is having some problem picking up all the changes that got
> published.

No, when I see the odd behavior, restarting the server doesn't help. I
have to "clean" the server in order to get contents published back
correctly. If I have a look to the publishing directory when the odd
behavior happens, I can see that many classes are missing, while the
whole directory structure seems ok.

Mauro.
Re: Unexpected context restarts [message #662667 is a reply to message #662648] Thu, 31 March 2011 09:34 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 3/31/2011 8:31 AM, Mauro Molinari wrote:
> Il 28/03/2011 16:13, Larry Isaacs ha scritto:
>> With respect to seeing odd behavior after a context restart, I think the
>> first step will be to determine if restarting the server fixes the
>> behavior. If it does, it suggests that publishing was successful, and
>> the restart is having some problem picking up all the changes that got
>> published.
>
> No, when I see the odd behavior, restarting the server doesn't help. I
> have to "clean" the server in order to get contents published back
> correctly. If I have a look to the publishing directory when the odd
> behavior happens, I can see that many classes are missing, while the
> whole directory structure seems ok.
>
> Mauro.

I'm really baffled as to why files would disappear. It suggests the
"delta" publishing is getting confused. The cached information for the
"delta" publishing is stored in a "publish?.dat" file in the
".metadata\.plugins\org.eclipse.wst.server.core\publish" folder in your
workspace, one for each server. Which file belongs with which server is
identified in the "publish.xml" file in the
"org.eclipse.wst.server.core" folder. For your server, how big is this
file for your server?

Cheers,
Larry
Re: Unexpected context restarts [message #663175 is a reply to message #661613] Mon, 04 April 2011 04:38 Go to previous messageGo to next message
Julien  Flotté is currently offline Julien Flotté
Messages: 8
Registered: March 2011
Junior Member
I have update my version of WTP. There's seem to be some kind of amelioration. When I change xsp (equivalent to jsp for coccon) or xsl files, the context doesn't restart.

However, I faced the same problem that Mauro, some classes were missing in the "tmp" directory. For information, my "pushish.dat" file was about 715Ko.
Re: Unexpected context restarts [message #663301 is a reply to message #663175] Mon, 04 April 2011 10:56 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 4/4/2011 4:38 AM, Julien Flotté wrote:
> I have update my version of WTP. There's seem to be some kind of
> amelioration. When I change xsp (equivalent to jsp for coccon) or xsl
> files, the context doesn't restart.

I'm glad that fixed the restart problem and we aren't dealing with a new
bug.

>
> However, I faced the same problem that Mauro, some classes were missing
> in the "tmp" directory. For information, my "pushish.dat" file was about
> 715Ko.

That file is larger than what is worth dealing with. There's only a
small possibility it contains a clue that will help with this separate
problem. I'll see about inspecting the code involved and try to
determine if sufficient "debug" logging is available to make progress on
this. If not, I can try to create "custom" versions of needed plug-ins
to help determine what is happening.

One thing that would help is to do a "clean" publish of the webapp and
save a copy someplace. Later when a class goes missing. Make a second
copy and compare them. I would like to know if anything other than
class files are going missing. If you don't have another comparison
tool, you can create temporary projects in Eclipse and compare them there.

Cheers,
Larry
Re: Unexpected context restarts [message #665695 is a reply to message #662667] Fri, 15 April 2011 09:55 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 31/03/2011 15:34, Larry Isaacs ha scritto:
> I'm really baffled as to why files would disappear. It suggests the
> "delta" publishing is getting confused. The cached information for the
> "delta" publishing is stored in a "publish?.dat" file in the
> ".metadata\.plugins\org.eclipse.wst.server.core\publish" folder in your
> workspace, one for each server. Which file belongs with which server is
> identified in the "publish.xml" file in the
> "org.eclipse.wst.server.core" folder. For your server, how big is this
> file for your server?

That file for the last project I published is about 860Kb big.

Mauro.
Re: Unexpected context restarts [message #665696 is a reply to message #663301] Fri, 15 April 2011 09:57 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 04/04/2011 16:56, Larry Isaacs ha scritto:
> One thing that would help is to do a "clean" publish of the webapp and
> save a copy someplace. Later when a class goes missing. Make a second
> copy and compare them. I would like to know if anything other than class
> files are going missing. If you don't have another comparison tool, you
> can create temporary projects in Eclipse and compare them there.

I'll try to do this too. I'll let you know.

Mauro.
Re: Unexpected context restarts [message #665697 is a reply to message #665695] Fri, 15 April 2011 10:10 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 4/15/2011 9:55 AM, Mauro Molinari wrote:
> Il 31/03/2011 15:34, Larry Isaacs ha scritto:
>> I'm really baffled as to why files would disappear. It suggests the
>> "delta" publishing is getting confused. The cached information for the
>> "delta" publishing is stored in a "publish?.dat" file in the
>> ".metadata\.plugins\org.eclipse.wst.server.core\publish" folder in your
>> workspace, one for each server. Which file belongs with which server is
>> identified in the "publish.xml" file in the
>> "org.eclipse.wst.server.core" folder. For your server, how big is this
>> file for your server?
>
> That file for the last project I published is about 860Kb big.
>
> Mauro.

That's bigger than I want to mess with unless I absolutely have to
(especially since it's binary).

Cheers,
Larry
Re: Unexpected context restarts [message #665790 is a reply to message #661919] Fri, 15 April 2011 19:49 Go to previous messageGo to next message
Ian Brandt is currently offline Ian Brandt
Messages: 2
Registered: July 2009
Junior Member
I'm also experiencing a context reload after I change only a JSP. I start the server in debug mode. I have a single web module with Path "/" added with "Auto Reload" disabled. It has a dependency on a JAR module from the workspace, which in turn pulls in two other transient dependent JAR modules from the workspace (i.e. three JAR modules under my WAR module in the Servers view). It's deployed to a Tomcat v6.0 server (6.0.26 in my case). My "Server Location" is set to "Use Tomcat installation". For "Server Options" I have only checked "Publish module contexts to separate XML files". For "Publishing" I have "Automatically publish when resources change" selected, and under "Select publishing actions" I have "Update context paths" checked.

I have a META-INF/context.xml in my web application that looks as follows:

<?xml version='1.0' encoding='UTF-8'?>
<Context antiJARLocking="true" reloadable="false">

	<!-- Enable Load Time Weaving... -->
	<Loader loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/>

	<!-- Disable session persistence across Tomcat restarts... -->
	<Manager pathname="" />
</Context>


I added the 'reloadable="false"' setting while troubleshooting this issue. When I look at my deployed server location I note there is no context defined in my server.xml (there is in the config copy in my Servers project, so I gather "Publish module contexts to separate XML files" works by filtering server.xml on publish), and the published "conf/Catalina/localhost/ROOT.xml" looks as above, preserving 'reloadable="false"', and adding docBase and source attributes.

Help > Check for Updates offers no upgrades. Here are my version numbers:

Eclipse IDE for Java EE Developers 1.3.2.20110301-1807
Eclipse Platform 3.6.2.M20110210-1200
Java EE IDE Feature 1.3.2.20110301-1807
Eclipse Web Developer Tools 3.2.3.v201102160541-7O7CFbWEMf84qYjGDyP3DNEwcgFU
WST Common UI 3.2.3.v201011031800-7C78FPlEdhO_oXWe4k_elbMgT1Lq
WST Common Core 3.2.3.v201011031800-7B7DFEsF7RZHOaLfS0KpNJ
WST Server UI 3.2.3.v20101104-7B4FBuAtJb1qEKLnCKHHHI347
WST Server Core 3.2.3.v20101104-30F8X8s734D3A4C
WST Server User Documentation 3.1.10.v201005241510-20Bg7w3121162A3236
WST Web Core 3.2.3.v201102160541-7E7AFI3AJrn5TN32vSJ8nRIWLD7_
WST XML Core 3.2.3.v201102160550-7C7OFXcF7RZHQKIkMxMsW_
WST Web User Documentation 3.2.0.v201005241510-31Eo8s734B3E4H7799
WST Server Adapters 3.2.0.v201005241510-51EoAkF77g8HBSc
Maven Integration for Eclipse (Required) 0.12.1.20110112-1712
Maven Integration for WTP (Optional) 0.11.1.20101108-1810

Is Bug 326456 fixed in these versions?

I also am getting an error on the reload:

2011-04-15 16:35:25,565 ERROR [Dispatcher] [ContainerBackgroundProcessor[StandardEngine[Catalina]]]: Dispatcher initialization failed
Unable to load configuration. - [unknown location]
	at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:58)
	at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:374)
	at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:418)
	at org.apache.struts2.dispatcher.ng.InitOperations.initDispatcher(InitOperations.java:69)
	at org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter.init(StrutsPrepareAndExecuteFilter.java:51)
	at org.springframework.web.filter.DelegatingFilterProxy.initDelegate(DelegatingFilterProxy.java:219)
	at org.springframework.web.filter.DelegatingFilterProxy.initFilterBean(DelegatingFilterProxy.java:145)
	at org.springframework.web.filter.GenericFilterBean.init(GenericFilterBean.java:179)
	at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:295)
	at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
	at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
	at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
	at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
	at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1345)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:303)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
	at java.lang.Thread.run(Thread.java:680)
Caused by: Caught exception while loading file struts-default.xml - [unknown location]
	at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:902)
	at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadDocuments(XmlConfigurationProvider.java:143)
	at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:110)
	at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reloadContainer(DefaultConfiguration.java:168)
	at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:55)
	... 26 more
Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration
	at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
	at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
	at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.createDocument(SAX2DOM.java:324)
	at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.<init>(SAX2DOM.java:84)
	at com.sun.org.apache.xalan.internal.xsltc.runtime.output.TransletOutputHandlerFactory.getSerializationHandler(TransletOutputHandlerFactory.java:187)
	at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getOutputHandler(TransformerImpl.java:392)
	at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerHandlerImpl.setResult(TransformerHandlerImpl.java:137)
	at com.opensymphony.xwork2.util.DomHelper$DOMBuilder.setup(DomHelper.java:205)
	at com.opensymphony.xwork2.util.DomHelper$DOMBuilder.<init>(DomHelper.java:190)
	at com.opensymphony.xwork2.util.DomHelper$DOMBuilder.<init>(DomHelper.java:181)
	at com.opensymphony.xwork2.util.DomHelper$DOMBuilder.<init>(DomHelper.java:167)
	at com.opensymphony.xwork2.util.DomHelper.parse(DomHelper.java:107)
	at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:893)
	... 30 more

In my case however the app loads okay after restarting the server. No clean necessary.
Re: Unexpected context restarts [message #666045 is a reply to message #665790] Mon, 18 April 2011 14:47 Go to previous messageGo to next message
Ian Brandt is currently offline Ian Brandt
Messages: 2
Registered: July 2009
Junior Member
As an update it appears that conf/Catalina/localhost/ROOT.xml is being watched as both a reload and redeploy resource:
2011-04-18 09:46:28,068 DEBUG [HostConfig] [ContainerBackgroundProcessor[StandardEngine[Catalina]]]: 
	Checking context[] redeploy resource /[...]/tomcat/6.0.26/home/conf/Catalina/localhost/ROOT.xml
	Checking context[] redeploy resource /[...]/tomcat/6.0.26/home/wtpwebapps/mycompany-web
	Checking context[] reload resource /[...]/tomcat/6.0.26/home/conf/web.xml
	Checking context[] reload resource /[...]/tomcat/6.0.26/home/conf/context.xml
	Checking context[] reload resource /[...]/tomcat/6.0.26/home/conf/Catalina/localhost/ROOT.xml
	Checking context[] reload resource /[...]/tomcat/6.0.26/home/wtpwebapps/mycompany-web/WEB-INF/web.xml
2011-04-18 09:46:38,069 INFO  [HostConfig] [ContainerBackgroundProcessor[StandardEngine[Catalina]]]: 
	Undeploying context []
[...]


Based on last modified timestamp I'm observing that conf/Catalina/localhost/ROOT.xml is updated every time I change a JSP. Per the FAQ on republishing to a running <Host /> where autoDeploy="true" it appears my subsequent redeploy kicks off before the publish is complete, hence the startup errors.

Is my issue that autoDeploy="true" on my <Host />, or that ROOT.xml is being republished for just a JSP change?
Re: Unexpected context restarts [message #666177 is a reply to message #666045] Tue, 19 April 2011 08:13 Go to previous message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
On 4/18/2011 2:47 PM, Ian Brandt wrote:
> As an update it appears that conf/Catalina/localhost/ROOT.xml is being
> watched as both a reload and redeploy resource:
>
> 2011-04-18 09:46:28,068 DEBUG [HostConfig]
> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]: Checking
> context[] redeploy resource
> /[...]/tomcat/6.0.26/home/conf/Catalina/localhost/ROOT.xml
> Checking context[] redeploy resource
> /[...]/tomcat/6.0.26/home/wtpwebapps/mycompany-web
> Checking context[] reload resource /[...]/tomcat/6.0.26/home/conf/web.xml
> Checking context[] reload resource
> /[...]/tomcat/6.0.26/home/conf/context.xml
> Checking context[] reload resource
> /[...]/tomcat/6.0.26/home/conf/Catalina/localhost/ROOT.xml
> Checking context[] reload resource
> /[...]/tomcat/6.0.26/home/wtpwebapps/mycompany-web/WEB-INF/w eb.xml
> 2011-04-18 09:46:38,069 INFO [HostConfig]
> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]: Undeploying
> context []
> [...]
>
>
> Based on last modified timestamp I'm observing that
> conf/Catalina/localhost/ROOT.xml is updated every time I change a JSP.
> Per
> http://wiki.eclipse.org/WTP_Tomcat_FAQ#Can_I_add_or_remove_a _project_from_a_server.2C_or_publish_changes_for_a_project_a lready_on_a_server.2C_while_that_server_is_running.3F
> it appears my subsequent redeploy kicks off before the publish is
> complete, hence the startup errors.
>
> Is my issue that autoDeploy="true" on my <Host />, or that ROOT.xml is
> being republished for just a JSP change?

One of the reasons the contexts are published to "wtpwebapps" instead of
"webapps" is so that autoDeploy won't apply. Also, there is some effort
made in the WTP Tomcat plug-ins to avoid rewriting configuration files
with identical contents, effectively just updating the timestamp.
However, off the top of my head, I don't recall how far that went with
"Publish module contexts to separate XML files" enabled. I also would
not have expected a context to reload with reloadable="false" set on the
context, but perhaps Tomcat gives special handling for the "ROOT" context.

If you disable the "Publish module contexts to separate XML files"
option, do you still get this behavior?

Cheers,
Larry
Previous Topic:Javascript Editor Type Validation
Next Topic:Axis2 1.5.1, Web Service, Tomcat 6.0
Goto Forum:
  


Current Time: Thu Aug 21 06:10:57 EDT 2014

Powered by FUDForum. Page generated in 0.02091 seconds