Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is a Tomcat webapp failing when an almost identical app starts within the same Tomcat instance?
    primarykey
    data
    text
    <p>We're experiencing slightly strange webapp deployment behaviour under Tomcat 5.5.27 on Linux (both on CentOS in production and Ubuntu 10.04 for development).</p> <p>App A and app B are almost identical (exactly the same libraries, a copied Maven project), App B differs only in that its JPA entities are annotated to access a different table within the same schema (the JNDI database references are identical). </p> <p>When the apps are deployed into either environment, app B will <strong><em>not</em></strong> start. However: </p> <ol> <li>Manually starting the stalled app, from the Tomcat admin console, works fine (???).</li> <li>After any attempt to restart Tomcat, the alphabetically later app fails to start. Point #1 still remains valid (???)</li> <li>Logging <em>is</em> configured (log4j), however, we get nothing from [the yet-to-start] app B's logging, nor errors from Tomcat's 'catalina.out' log file (NB. logging <strong><em>is</em></strong> working once the apps are up and running).</li> </ol> <p>I've done a reasonably thorough search for information (Apache/Tomcat bugzilla, Google) but I've found nothing of real use. Other <a href="https://stackoverflow.com/questions/2737983/tomcat-6-whats-the-significance-of-antiresourcelocking-antijarlocking">posts</a> have sighted the use of the antijarlocking and antiresourcelocking attributes on the server's 'context.xml' 'Context' node, but there is also a suggestion that this is unecessary/inaffective under Linux (hasn't appeared to work here, either).</p> <p>Any ideas?</p> <p>Cheers</p> <p>Rich</p> <p>P.S. Upgrading from Tomcat 5.5.x isn't an option, currently (IT support etc.). </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload