You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/10/27 12:36:59 UTC
[jira] Updated: (QPID-2034) [Java-Derby]
[CombinedTest#testForwardAll] SQLException : No Current Connection
[ https://issues.apache.org/jira/browse/QPID-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-2034:
---------------------------------
Fix Version/s: (was: 0.5)
> [Java-Derby] [CombinedTest#testForwardAll] SQLException : No Current Connection
> -------------------------------------------------------------------------------
>
> Key: QPID-2034
> URL: https://issues.apache.org/jira/browse/QPID-2034
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker MessageStore - DerbyStore
> Reporter: Martin Ritchie
> Attachments: TEST-org.apache.qpid.test.unit.client.forwardall.CombinedTest.testForwardAll.out
>
>
> Summary:
> During a test run of the java-derby profile the CombinedTest failed the testForwardAll test due to a Derby issue.
> The end of the stack traces was:
> Caused by: java.sql.SQLException: No current connection.
> This occured whilst the delivery thread was attempting to enqueue and then send the message to a NoAck Subscriber.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org