db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5435) org.apache.derby.client.am.SqlException in stressMultiTest: The DDM object 0x1232 is not supported. The connection has been terminated.
Date Thu, 29 Sep 2011 08:04:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117110#comment-13117110
] 

Knut Anders Hatlen commented on DERBY-5435:
-------------------------------------------

If you still have derby.log from the failed run, you may find more useful information there,
like the server-side exception that killed the connection. The protocol error seems to have
happened while receiving the message text for an exception seen during execution of a query.
                
> org.apache.derby.client.am.SqlException in stressMultiTest: The DDM object 0x1232 is
not supported.  The connection has been terminated.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5435
>                 URL: https://issues.apache.org/jira/browse/DERBY-5435
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.9.0.0
>         Environment: Linux CentOS 6.1 on VMWare, with ibm 1.5. SR12FP4.
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> With trunk (10.9.0.0 alpha) svn updated to revision 1176157, there was one failure I
don't remember seeing before:
> testStressMulti(org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest)junit.framework.AssertionFailedError:
Caused by: 
> java.sql.SQLException: The DDM object 0x1232 is not supported.  The connection has been
terminated.
> 	at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.Connection.createStatement(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest$StressMultiRunnable.select(StressMultiTest.java:553)
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest$StressMultiRunnable.run(StressMultiTest.java:429)
> 	at java.lang.Thread.run(Thread.java:811)
> Caused by: org.apache.derby.client.am.SqlException: The DDM object 0x1232 is not supported.
 The connection has been terminated.
> 	at org.apache.derby.client.am.SqlException.copyAsUnchainedSQLException(Unknown Source)
> 	at org.apache.derby.client.am.Sqlca.chainDeferredExceptionsToAgentOrAsConnectionWarnings(Unknown
Source)
> 	at org.apache.derby.client.am.Sqlca.getJDBCMessage(Unknown Source)
> 	at org.apache.derby.client.am.SqlException.getMessage(Unknown Source)
> 	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.Statement.executeQuery(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest$StressMultiRunnable.select(StressMultiTest.java:555)
> 	... 2 more
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest.handleException(StressMultiTest.java:351)
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest.access$200(StressMultiTest.java:70)
> 	at org.apache.derbyTesting.functionTests.tests.multi.StressMultiTest$StressMultiRunnable.run(StressMultiTest.java:445)
> 	at java.lang.Thread.run(Thread.java:811)
> This is a fairly new system for me, only recently have I started running (automated/nightly)
suites.All on it, so if this may be intermittent on this system.
> The issue did not show on a SUSE Linux (10) system which ran the tests at the same revision
level, same jvm level.
> The message looks a bit like  DERBY-2066, but that issue has been fixed in trunk and
the stack trace appears different.
> Interestingly, approximately the same time the tinderbox showed a test failure in testStressMulti
(http://dbtg.foundry.sun.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/1176669-org.apache.derbyTesting.functionTests.suites.All_diff.txt),
but that looks like intermittent NullPointerException previously reported in DERBY-3823. 
> The stressMultiTest failing in both cases may just be a coincidence.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message