[ 
https://issues.apache.org/jira/browse/UIMA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002280#comment-13002280
 ] 

Marshall Schor commented on UIMA-2081:
--------------------------------------

I've not seen this error on my Windows or Linux platforms, or on Hudson/Jenkins.

> UIMA-AS extended test intermittent failure - message 
> InvalidDestinationException: Cannot publish to a deleted Destination: 
> temp-queue ...
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-2081
>                 URL: https://issues.apache.org/jira/browse/UIMA-2081
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>         Environment: MacBook Pro, OS 10.6.6 2.53 GHz Intel Core 2 Duo, 4 GB 
> memory
> UIMA-AS 2.3.1 RC5 + changes to trunk as of March 3 2011
>            Reporter: Marshall Schor
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to