OT: tomcat port problem
Date: Mon, 17 Aug 2009 10:50:31 -0400
We have a web server (old old apache) talking to tomcat (old old tomcat) that's on an old sun 5.8 web server. This has been running fine for six years and apache is on port 8000 and the tomcat connector is on 11001 No development is going on, no code changes at all. 10 days ago we had a full nfs mount and since then we lose connectivity to tomcat from apache. I believe this is through mod_jk and going over the connector. If my lingo is wrong excuse me, I've been thrown into this and have spent a few days trying to figure this out. We've thrown tons of debug levels at this but all we get is below.
The only thing we get in the logs is from the mod_jk.log. It's not a busy website at all. I don't know the stats but it is low usage. The most I saw doing a netstat -a on port 8000 was 20 connections.
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp13_worker.c (173)]: In jk_endpoint_t::connect_to_tomcat, failed
> errno = 146 [jk_ajp13_worker.c (584)]: Error connecting to the Tomcat
On the weekend we downloaded and installed the latest tomcat on port 7002, we took apache out completely and just had everything running off of tomcat (java 1.5 tomcat 188.8.131.52). This also loses connectivity after awhile. It doesn't crash, we just lose connectivity. By losing connectivity I mean it just hangs for awhile and then returns 404 error. Netstat -a on port 7002 shows my connections as established.
I think we've ruled out our application as the problem and we have an os/network/port problem. I'm having troubles with IBM support on getting them to help me. If anyone can help me offline with troubleshooting I would appreciate this.
MikeReceived on Mon Aug 17 2009 - 09:50:31 CDT