No, It could be Tomcat 6 / AIX OS 5.3 / Java 1.5

We reverted to Tomcat 4 - identical code base identical DB config and the 
app works like a charm (has been working for 2 years)

The reason to upgrade is 2 fold - to stay current and to use Tomcat's 
Realm LDAP authentication mechanism.





chuck.caldar...@unisys.com 
09/28/2012 10:54 AM
Please respond to
users@tomcat.apache.org


To
users@tomcat.apache.org
cc

Subject
RE: Tomcat 6 serious issues on AIX 5.3






> From: vincent.soo...@daimler.com [mailto:vincent.soo...@daimler.com] 
> Subject: Re: Tomcat 6 serious issues on AIX 5.3

> On machines with higher memory Tomcat does not crash but as I indicated 
we 
> get SocketException:
> [2012-09-25 12:13:35,700] ERROR com.*Action - System Error
> java.sql.SQLException: java.io.IOException: java.net.SocketException: 
> There is no process to read data written to a pipe.
>         at com.ashna.jturbo.driver.x.e(x.java)

Which means Tomcat isn't in the game.  It appears the database server on 
the other end of the pipe has gotten bored and decided to stop listening. 
You should consult the documentation for the jturbo driver to see if can 
be configured to be more resilient.  You may be able to configure Tomcat's 
DB connection pool to recover from this situation, assuming the DB server 
is still alive.  Post your DBCP configuration and let's see what can be 
done with it.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you 
received this in error, please contact the sender and delete the e-mail 
and its attachments from all computers.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.  

Reply via email to