[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Reopened] (AMQ-5250) temp queue not working after long run of activemq
From:       "Rural Hunter (JIRA)" <jira () apache ! org>
Date:       2014-08-29 2:18:08
Message-ID: JIRA.12724269.1403921438066.6466.1409278688648 () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/AMQ-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Rural Hunter reopened AMQ-5250:
-------------------------------


No it's definitely not normal behavior. This happened again after my activemq 5.10.0 \
running for about 2 months. I have written some code to test it. The main logic of \
the code is: 1. Create a temp queue(tempQueue) and start a producer to send a \
message(setJMSReplyTo(tempQueue)) to specific queue. 2. Start a comsumer to read the \
specific queue and send a response to the tempQueue. 3. Consume the temp queue to \
check the repsonse message

I put it in cron and run it every minute. It had been run two months without problem \
and suddenly it began to report the same error about every several minutes(yes, not \
every minutes, sometimes every minute, sometimes every 3 minutes, sometimes every 5 \
mintues, not constant).

Since I'm not able to find a way to get the test case to reproduce the issue, I want \
to know if there is anything I could check to trace the root cause when the problem \
happens again.





> temp queue not working after long run of activemq
> -------------------------------------------------
> 
> Key: AMQ-5250
> URL: https://issues.apache.org/jira/browse/AMQ-5250
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.9.0
> Reporter: Rural Hunter
> Fix For: WAITING_FOR_TEST
> 
> 
> We encounterred a problem when using temp queue for request/reply pattern. It \
> worked normally but after a long time lets say several weeks, the applications \
> using temp queue started to report errors: 2014-06-25 08:25:59 [WARNING] Message \
>                 back to the server fails!
> javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: \
> temp-queue://ID:myserver-45345-1403492084155-1:1:259 at \
> org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1748) at \
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289) \
> at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
>  at org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:300)
>  I created a test application to test the temp when the problem happened and found \
> this: On each connection, the temp queue worked once and the second time it failed. \
> I also tried to monitor messages in ActiveMQ.Advisory.TempQueue. But I could only \
> receive one message after I subsribed on it everytime.  I checked the activemq log \
> and there was nothing about the problem. Other applications not using temp queue \
> worked fine. This happened twice in recent month. I just had to restart activemq to \
> fix it. I saw a same error in mailing list but not sure if it's the same problem:
> http://activemq.2283324.n4.nabble.com/Getting-a-quot-Cannot-publish-to-a-deleted-Destination-quot-but-eventually-works-after-a-couple-of-rs-td4682497.html
> 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic