[
https://issues.apache.org/jira/browse/QPID-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078903#comment-13078903
]
Keith Wall commented on QPID-2899:
----------------------------------
Hi Robbie,
Are we still logging the exception stack and its underlying(s)? I worry this
change might make problem determination more difficult. I'd be tempted to add
to the new catch block.
_logger.error("Exception processing command, e);
What do you think?
> SelectorTest#testRuntimeSelectorError fails against the Java broker when
> running the 0-10 profiles
> --------------------------------------------------------------------------------------------------
>
> Key: QPID-2899
> URL: https://issues.apache.org/jira/browse/QPID-2899
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Fix For: 0.13
>
>
> org.apache.qpid.test.client.message.SelectorTest#testRuntimeSelectorError
> fails against the Java broker when using 0-10 because the broker fails to
> close the Session when the deliberate error occurs, as it does when using
> 0-8/0-9.
> QpidBrokerTestCase behaviour is to close connections during teardown that
> were created using the getConnection() utility method, and the teardown close
> is failing in this test because it tries to sync outstanding 0-10 commands
> with the broker and times out, as the previous exception has crippled it. The
> exception should be caught and used to close the producer Session with an
> ExecutionException.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
