Frank, I will try to recreate the problem. Yesterday, I tried the scenario with async sendCAS() and saw no problems after bouncing a broker. Will test the scenario with sendAndReceive().
Jerry C On Wed, Feb 8, 2012 at 9:32 AM, Frank Enders <end...@averbis.de> wrote: > Jerry, thanks for your reply first of all. > Pending messages don't seem to play a role in our scenario. I am just > sending single messages synchronously using sendAndReceiveCAS(). > So when I restart the broker no messages are pending. > I attached jconsole to the broker in order to observe its behaviour: > A strange thing is that when the error occurs I can see that the missing > queue actually should be present: > > i.e.: > The error states: > "javax.jms.InvalidDestinationException: Cannot publish to a deleted > Destination: temp-queue://ID:xubuntu-VirtualBox-42260-1328698333409-0:2:1" > > But in jconsole I can see: > > |- org.apache.acticemq > |- OurBroker > |- TempQueue > |- ID_xubuntu-VirtualBox-42260-1328698333409-0_2_1 > > appearing at the same time (until the UimaASMetaRequestTimeout is reached). > > Each subsequent request I send produces the same error (only the temp > queue's id changes for each request). > > After stopping and redeploying the endpoint, everything works fine again. > > All the best, > Frank >
