db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4351) With 10.1 client and 10.5 server SQLSTATE(null): An error occurred during a deferred connect reset. with executeUpdate in XATest.morph
Date Fri, 14 Aug 2009 19:08:14 GMT
With 10.1 client and 10.5 server SQLSTATE(null): An error occurred during a deferred connect
reset. with executeUpdate in XATest.morph 
---------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-4351
                 URL: https://issues.apache.org/jira/browse/DERBY-4351
             Project: Derby
          Issue Type: Bug
          Components: Network Server
    Affects Versions: 10.5.3.0
            Reporter: Kathey Marsden


Running the 10.1 tests with 10.1 client and 10.5 server I saw the following failure and disconnect:

FAIL -- unexpected exception ****************
SQLSTATE(null): An error occurred during a deferred connect reset and the connection has been
terminated.  See chained exceptions for details.
SQLSTATE(25001): DERBY SQL error: SQLCODE: -1, SQLSTATE: 25001, SQLERRMC: 25001
org.apache.derby.client.am.DisconnectException: An error occurred during a deferred connect
reset and the connection has been terminated.  See chained exceptions for details.
	at org.apache.derby.client.net.NetAgent.readDeferredResetConnection(Unknown Source)
	at org.apache.derby.client.net.NetAgent.beginReadChain(Unknown Source)
	at org.apache.derby.client.am.Agent.flow(Unknown Source)
	at org.apache.derby.client.am.Statement.flowExecute(Unknown Source)
	at org.apache.derby.client.am.Statement.executeUpdateX(Unknown Source)
	at org.apache.derby.client.am.Statement.executeUpdate(Unknown Source)
	at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest.morph(Unknown Source)
	at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest.main(Unknown Source)

To reproduce I used the following script to set up my environment  (change for your locations):

export JAVA_HOME=C:/p4/marsden_trunk/ibm15
export PATH="$JAVA_HOME/bin;$PATH"
export JUNIT="C:/svn/tools/junit.jar"
export ORO="C:/svn/tools/jakarta-oro-2.0.8.jar"
export TEN5JARS=C:/kmarsden/projects/10.5.3testing/db-derby-10.5.3.0-lib-debug/lib
export TEN1JARS=c:/kmarsden/svnreleases/jars/10.1.3.1
export CLASSPATH=".;$JUNIT;$ORO;$TEN5JARS/derby.jar;$TEN5JARS/derbynet.jar;$TEN1JARS/derbytools.jar;$TEN1JARS/derbyclient.jar;$TEN1JARS/derbyTesting.jar"
java org.apache.derby.tools.sysinfo

and ran the derbynetclientmats suite. I imagine just running XATest with network client will
show the failure too, but have not confirmed.

I have not narrowed down the course of events that cause the failure but because we are seeing
the 25001 error too, I am guessing this is another case where network server is not rolling
back before closing a connection after the DERBY-3319 fix.  If you run with the latest on
the 10.5 branch (with the partial fix for DERBY-1191), you should be able to see where the
error is occurring on the network server side.

I also have not checked to see if this is a problem with versions later than 10.1






-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message