I figured out my problem, and I thought I should posted it, although I 
apologize if I'm reducing the signal to noise here, as this is pretty specific, 
and it didn't get a lot of attention to begin with.  Here it is:

I mistakenly had iptables blocking traffic from localhost, which I think 
blocked the communication between apache and tomcat.

I first got a hint, when I couldn't list the active ports with 'nmap -sT -O 
localhost', but I could using the server's LAN IP address in place of 
'localhost'. Then I flushed my iptables rules, and sure enough, jsp pages 
started working again.

I've fixed the problem (it works, not sure optimal), by adding the following 
first iptables rule:

    ACCEPT all -- localhost.localdomain anywhere

Please let me know if you suggest doing something different.  I suppose I could 
be more restrictive in what services/ports to permit from localhost, but I'm 
not sure that's necessary, and I don't know what else it might break.

Regards,
Tim

-----Original Message-----
From: Tim Hunt [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 09, 2008 1:49 PM
To: Tomcat Users List
Subject: RE: Tomcat seems to have stopped servicing requests behind Apache

Quick update:

I looked farther back in the logs, and "WARNING: Unable to open config file" 
was in the Catalina log all the time back when it worked, so sorry for the bad 
steer.

I compared my httpd.conf, working_mod_jk2.conf, server.xml, and web.xml files 
to versions on a working server and found very few differences, none of which 
seemed to have any chance of causing my trouble (jsp pages not loading).

'service tomcat status' reports tomcat is running.

If I comment out the 'Include /etc/httpd/conf/working_mod_jk2.conf' line from 
httpd.conf and restart, it serves simple .jsp pages as text (not processed), 
but restoring that line and restarting returns to problem of jsp pages 
returning 503 after long delays.

Please let me know if there are any suggestions to diagnose or fix this.

Thanks,
Tim

-----Original Message-----
From: Tim Hunt [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 09, 2008 10:10 AM
To: Tomcat Users List
Subject: RE: Tomcat seems to have stopped servicing requests behind Apache

Thanks *a lot* for the suggestion, but I was not able to find a file with that 
pattern anywhere on my system.

I tried again to load a few jsp pages, including a very simple one, but they 
all failed, after what seemed like 5 minutes of trying, with 503.  The failed 
requests didn't add anything to the tomcat or apache logs.

Only rebooting added to the logs, but it was the same entry in 
Catalina.[date].log listed below.

Any other suggestions, including ways to diagnose will be *greatly* appreciated!

I'm going to take another look at the config files to see if anything looks odd 
and try to sort out the warning about loading a config file.

Thanks,
Tim

-----Original Message-----
From: Clovis Wichoski
Sent: Tuesday, July 08, 2008 8:55 PM
To: Tomcat Users List
Subject: Re: Tomcat seems to have stopped servicing requests behind Apache

Hi Tim,

check at your tomcat home if exists a file with the pattern hs_err_pid*.log
maybe your JVM was killed, and in that log you will know the reason.

regards

Clóvis

On Tue, Jul 8, 2008 at 6:26 PM, Tim Hunt <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I have a Linux (Centos 4) system running Tomcat (5.5.20) behind
> Apache(2.0.52) via mod_jk, and Tomcat seems to have stopped working. I
> don't know what broke it, and I would really appreciate help diagnosing
> the problem. Here's some more info:
>
> I can still server up static HTML files through just Apache, but jsp
> pages don't work, and eventually return a 503 error.
>
> I'm using the jk adaptor
>
> Checking the catalina.[date].log file shows the following entries during
> start up - note the bit about failing to read the config file about half
> way down:
>
> Jul 8, 2008 3:56:07 PM org.apache.catalina.core.AprLifecycleListener
> lifecycleEvent
>
> INFO: The Apache Tomcat Native library which allows optimal performance
> in production environments was not found on the java.library.path:
> /usr/java/jdk1.5.0_09/jre/lib/i386/server:/usr/java/jdk1.5.0_09/jre/lib/
> i386:/usr/java/jdk1.5.0_09/jre/../lib/i386
>
> Jul 8, 2008 3:56:08 PM org.apache.catalina.startup.Catalina load
>
> INFO: Initialization processed in 1555 ms
>
> Jul 8, 2008 3:56:08 PM org.apache.catalina.core.StandardService start
>
> INFO: Starting service Catalina
>
> Jul 8, 2008 3:56:08 PM org.apache.catalina.core.StandardEngine start
>
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.20
>
> Jul 8, 2008 3:56:08 PM org.apache.catalina.core.StandardHost start
>
> INFO: XML validation disabled
>
> Jul 8, 2008 3:56:10 PM org.apache.jk.config.BaseJkConfig execute
>
> WARNING: Unable to open config file
>
> Jul 8, 2008 3:56:10 PM org.apache.jk.common.ChannelSocket init
>
> INFO: JK: ajp13 listening on /0.0.0.0:8009
>
> Jul 8, 2008 3:56:10 PM org.apache.jk.server.JkMain start
>
> INFO: Jk running ID=0 time=0/110  config=null
>
> Jul 8, 2008 3:56:10 PM org.apache.catalina.storeconfig.StoreLoader load
>
> INFO: Find registry server-registry.xml at classpath resource
>
> Jul 8, 2008 3:56:10 PM org.apache.catalina.startup.Catalina start
>
> INFO: Server startup in 2441 msI've checked the server.xml and web.xml
> files and they both seem okay and readable.
>
> I've also noticed that tomcat does not seem to restart correctly. If I
> issue 'service tomcat restart', the cursor doesn't ever come back.
>
> Any suggestions?
>
> Thanks!!
>
> Tim
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to