[Jetty-support] Problems with webapps that have complex startup procedures

[Ryan P. <ry...@vi...>]

Hello,

We are attempting to use Jetty with a deployed WAR that incorporates database creation and patching in its controller.  Unfortunately, it has problems using Jetty.  Using Tomcat 5.x or 6 everything works fine.

In Jetty the webapp starts and begins by creating its database tables and progress is recorded in the log file.  After several seconds, another initialization of the same webapp occurs (according to the log file) and fails because only some of the tables are present.  Using a similar project that has a less complicated database structure, everything starts up fine and only one set of startup messages for that webapp are recorded.

This scenario should be easy to duplicate by using a webapp where its controller startup increments a static heartbeat counter for a couple of minutes and logs either a reset of the counter or a startup where the counter is not at its initial value.

Initially the project was using Jetty 6.1.5, but 6.1.8, 6.1.11, 6.1.12.rc2, and 7.0.0pre3 all produced the same results.

Any idea why this is happening or how to stop the two startup sequences of the same webapp?  It seems that Jetty launches the first webapp instance and then gives up on it if the application takes too long to start, launching another one.


Videx Inc. 1105 N. E. Circle Blvd. Corvallis OR 97330 (541) 758-0521
CONFIDENTIAL COMMUNICATION: The email message and any attachments are intended only for the addressee.  They may be privileged, confidential, and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying is expressly prohibited.  If you received this email message in error, please notify the sender immediately by replying to this e-mail message or by telephone