up vote 1 down vote favorite
share [g+] share [fb]

I have a java web app running on a tomcat server with some Rest interfaces that have run without fail for months. Now we put another war in their and it has stopped the rest interfaces completely. The rest of the app runs and can talk to the database, but we get 503 errors when we look for the interfaces. The only thing of note, is the new war immediately throws an exception and fails because of a missing dependency.

What should I be looking for, for the cause of this?

link|improve this question
A 503 error means that you should have an error logged. Check the logs. – Shane Madden Oct 27 '11 at 21:40
@Shane Madden I know, catalina and the applications logs are devoid of anything related. Im thinking its a configuration issue, but my googling skills are failing, and im finding nothing in the configs i can find. – Chris Oct 27 '11 at 21:48
Post your configuration. – quanta Oct 28 '11 at 4:29
feedback

1 Answer

up vote 1 down vote accepted

It was fixed by adding the below to apache's proxy_ajp.conf.
proxy_ajp.conf, however, did have an entry for the working app, so i am still unsure why that would break.

ProxyPassMatch ^/(new_app.*)$    balancer://tomcat_base_dir/$1  stickysession=JSESSIONID timeout=1800
link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.