[
https://issues.apache.org/jira/browse/QPIDIT-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-82.
------------------------------------
Resolution: Fixed
The cause of this error is insufficient timeout while the receiver is waiting
for a message. As both the sender and receiver are started on separate threads
in their own JVM, it takes a second or so for each JVM to start. As the timeout
was set to a value of 1000 (ms) and the receiver is started first, followed by
the sender, a few tests were failing because the receiver was timing out
waiting for the sender to start.
This problem was solved by increasing the timeout value from 1000 (ms) to 10000
(ms). The 1 second value would have been reasonable if the JVMs were all
already started or if the producer and consumer were sharing a JVM.
In addition, adding a proper exception to the timeout would allow messages
which are not received because of a timeout to show a meaningful exception:
{noformat}
AssertionError: Caught exception, exiting.
java.lang.Exception: Receiver::run(): No message, timeout while waiting
at
org.apache.qpid.interop_test.jms_hdrs_props_test.Receiver.run(Receiver.java:147)
at
org.apache.qpid.interop_test.jms_hdrs_props_test.Receiver.main(Receiver.java:106)
{noformat}
> JMS tests fail intermittently with null message
> -----------------------------------------------
>
> Key: QPIDIT-82
> URL: https://issues.apache.org/jira/browse/QPIDIT-82
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: JMS Headers and Properties Test, JMS Message Test
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> Running the JMS tests sometimes results in one or two tests failing with the
> following:
> {noformat}
> AssertionError: JMS message body error:
> sent:{'none': [None]}
> received:{u'none': []}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
