[
https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719348#comment-13719348
]
Mridul Muralidharan commented on BOOKKEEPER-648:
------------------------------------------------
Flavio, I am not sure what the expectation of this bug is - is it appropriate
debug message for this testcase ?
As I detailed above - the only message possible is : "no message was received
before timeout" - unfortunately, I dont think that is going to help us much in
debugging it.
The reason I did not add descriptive message for every assertion in the tests
is because the corresponding JMS api's detail the error conditions in detail
(when a null can be returned from receive is detailed in JMS api javadocs for
example).
To actually debug/fix the issue, we will need to enable debug logging in
server, client api and jms mode.
Subsequently, when issue is observed, we will need to trace whether message was
actually sent to server, whether server dispatched to both subscribers, whether
client api received it, and whether it was dispatched to jms.
The jms module does nothing different from any other api user of hedwig -
barring bugs in it ofcourse :-)
This is an assertion which is typically not expected to fail unless there is
something broken elsewhere which is causing message loss.
> BasicJMSTest failed
> -------------------
>
> Key: BOOKKEEPER-648
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-648
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-client
> Reporter: Flavio Junqueira
> Assignee: Mridul Muralidharan
>
> While running tests, I got once a failure for this hedwig-client-jms test:
> BasicJMSTest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
