The extended tests, the testDeployAgainAndAgain occasionally fails. The failure occurs in the following sequence:
The test starts, it deploys some services, these connect to the broker. It deploys a client, this client sets up a connection to the broker, and creates a temp queue, and then immediately sends a getMeta request using the just created temp queue as the reply destination. The service gets the getMeta, and responds, by attempting to send the reply to that temp queue.
But the Broker hasn't (apparently) quite finished create the queue, and so we get a message to the console log saying:
javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue:// ...
The error is quite intermittent. Sometimes there is no error reported for this testDeployAgainAndAgain. However, if I put that test into a loop, it seems to fail somewhere between 200 - 300 seconds of running on the MacBook.
If I insert a 1/10 second delay after the Client creates the temp queue on the broker, and before the Client uses that temp queue in a getMeta request, then it runs for hours with no error being reported.
Suggestion: insert a short delay after first setting up a temp queue in a broker, before using that queue in messages, to insure it has a chance to get set up. Consider making a test case for this for ActiveMQ.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|17h 34m||1||Jerry Cwiklik||04/Mar/11 15:56|
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||2.3.1AS [ 12315335 ]|
|Resolution||Fixed [ 1 ]|