Hello,
This issue is known but not fixed. See
http://jira.jboss.com/jira/browse/JBAS-3691 for more details.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986767#3986767
Reply to the post :
We use the ojdbc14.jar 10.2.0.1.0 from Oracle.
The modification could look like :
if( ( error_code 2 || error_code = 21000 )
( (error_text.indexOf(SOCKET) -1) //for control socket error
|| (error_text.indexOf(CONNECTION HAS ALREADY BEEN CLOSED) -1)
|| (error_text.indexOf(BROKEN PIPE)
Shall submit that change myself ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970125#3970125
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970125
___
jboss-user mailing list
Hello,
We are using JBoss 4.0.2. I had a look to the OracleExceptionSorter of version
4.0.5CR1, but this particular error (code 17008) is not caught.
Looking into it, it seems that that the TxConnectionManager returns a closed
connection to the JMS layer (we use oracle persistency for JMS).
Hello
We are using JBoss 4.0.2 and Oracle 10 G on a AIX/HACMP cluster, while the DB
is being move from a node to another, we (obviously) experiment database
deconnections. During reconnection, JBoss OracleExceptionSorter catch all
errors but one : CLOSED CONNECTION.
We have subclassed the
