Hi, I'm running SAP DB 7.3.00.8 on a Redhat 7.1 box. It's a production system with tomcat / Apache - using JDBC for java access and Poolman as connection pool. The system worked well for weeks but now I'm getting TimeoutExceptions sometimes. The SESSION_TIMEOUT parameter is set to zero.
I've read on this list some old postings about strange timeouts. Are these timeout problems fixed in the latest JDBC patch 7.3.00.18 ? (I'm not yet using it) How can I activate that extendedTrace parameter mentioned below? Greetings Matthias Bild -- [EMAIL PROTECTED] >ANN: JDBC Driver update >II. TIMEOUT handling >TIMEOUT Exceptions are now raised only when inside a transaction. Otherwise, >an implicit reconnect happens and the action is repeated. >Some have reported spurious TIMEOUTs. There is a new connect option >extendedTrace=. This will log only these errors without the >overhead of the general trace. Hopefully, this helps me to find this error.
