You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "f.pascal" <f....@pw-consultants.com> on 2013/04/15 13:55:29 UTC
JMS Request/Reply
Hi,
After few days of exploitation, JMS ReplyManager could not find the
correlation request in this TimeoutMap !
It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
same Queue, with different TimeoutMap – in the log bellow, one time we have
1 in timeout map with thread #211 and for the other threads we have 0 !
How it's possible ? The result is that the reply manager doesn't find the
original request in the timeout map.
Thank you very much for your help.
*Environnment :*
Camel : 2.10.0
Redhat : 6.3 (santiago)
Java : java version "1.6.0_41"
Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
MQ Series : serveur : 7.0.1.3 et client 7.5.0
*LOG :*
[2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
PersistentQueueReplyManager[T2P.ENROL.R]-1]
org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
Early reply not found handler at attempt 1. Waiting a bit longer.
[2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 1 in the timeout map
[2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: JMS Request/Reply
Posted by "f.pascal" <f....@pw-consultants.com>.
Claus,
Some precision, we don’t have this problem with ActiveMQ, only with MQSeries. The difference it's that we use a custom DestinationResolver with MQSeries for set clientTarget option like it's written in the camel documentation.
Our custom DestinationResolver :
package fr.pwgroup.camel.t2p.stecard;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.Session;
import org.springframework.jms.support.destination.DestinationResolver;
import com.ibm.mq.jms.MQQueueSession;
public class StecardResolver implements DestinationResolver {
public StecardResolver() {
super();
}
@Override
public Destination resolveDestinationName(Session session, String destinationName, boolean pubSubDomain) throws JMSException {
MQQueueSession wmqSession = (MQQueueSession) session;
return wmqSession.createQueue("queue:///" + destinationName + "?targetClient=1");
}
}
Thanks for your help.
François
De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5730930h65@n5.nabble.com]
Envoyé : lundi 15 avril 2013 18:48
À : François Pascal
Objet : Re: JMS Request/Reply
Not sure what happens. Do you stop/start the JMS route / consumer / or
anything, or do any changes in the application?
Also you can try upgrading to a newer Camel version.
On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
> Hi,
>
> After few days of exploitation, JMS ReplyManager could not find the
> correlation request in this TimeoutMap !
>
> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
> same Queue, with different TimeoutMap – in the log bellow, one time we have
> 1 in timeout map with thread #211 and for the other threads we have 0 !
> How it's possible ? The result is that the reply manager doesn't find the
> original request in the timeout map.
>
> Thank you very much for your help.
>
> *Environnment :*
> Camel : 2.10.0
> Redhat : 6.3 (santiago)
> Java : java version "1.6.0_41"
> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>
>
> *LOG :*
>
> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
> PersistentQueueReplyManager[T2P.ENROL.R]-1]
> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
> Early reply not found handler at attempt 1. Waiting a bit longer.
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 1 in the timeout map
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5730930.html
To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731084.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: JMS Request/Reply
Posted by "f.pascal" <f....@pw-consultants.com>.
Hi,
The JMS endpoints is .to(this.getStecardUri())
True, after ~= 20 hours idle , we send a new message that create a new producer
De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5731147h92@n5.nabble.com]
Envoyé : vendredi 19 avril 2013 15:39
À : François Pascal
Objet : Re: JMS Request/Reply
Hi
That route seems to only have direct endpoints. Where is the JMS endpoints?
And so you are saying that it has been idle for 20 hours, and then a
new messages is being processed.
And when that happens, a new producer is created?
On Fri, Apr 19, 2013 at 2:07 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5731147&i=0>> wrote:
> Hi,
>
> The route :
>
> // ------------------------------------------------------------------
> from("direct:Stecard-client.requests").routeId(this.getRouteId())
> // to STECARD
> .choice().when(_isAuditMode).to("direct:Stecard-client.auditRequest").end()
> .transform(new Expression() {
> @SuppressWarnings("unchecked")
> @Override
> public <T> T evaluate(Exchange exchange, Class<T> arg1) {
> return (T) new String(exchange.getIn().getBody(StecardMessage.class).writeData());
> }
> })
> .to(this.getStecardUri())
> .transform(new Expression() {
> @SuppressWarnings("unchecked")
> @Override
> public <T> T evaluate(Exchange exchange, Class<T> arg1) {
> return (T) StecardMessage.parseMessage(exchange.getIn().getBody(byte[].class));
> }
> })
> .choice().when(_isAuditMode).to("direct:Stecard-client.auditResponse").end()
> .end();
> // ------------------------------------------------------------------
>
>
>
> Only 3 messages Ok being routed before re-creating producer.
> Yes, the route been idle for 20 hours
>
> Thanks
> François
>
>
> De : Claus Ibsen-2 [via Camel] [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=5731147&i=1>]
> Envoyé : vendredi 19 avril 2013 09:09
> À : François Pascal
> Objet : Re: JMS Request/Reply
>
> Hi
>
> Can you show details of the route with the request/reply?
> And is there many messages being routed or few?
>
> And before the 20h when re-creating the producer. Has the route been
> idle for a while?
>
>
> On Thu, Apr 18, 2013 at 4:16 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=0>> wrote:
>
>> Hello Claus,
>>
>> We have put stacktrace when camel create, start or stop a JmsProducer for understand what’s append. Attached, I put the logs files and we can to see than camel recreate the JmsProducer 20 hours after camel was started but we don't understand why. Any idea ?
>>
>> Best regards
>>
>> François
>>
>>
>>
>>
>> De : Claus Ibsen-2 [via Camel] [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=1>]
>> Envoyé : lundi 15 avril 2013 18:48
>> À : François Pascal
>> Objet : Re: JMS Request/Reply
>>
>> Not sure what happens. Do you stop/start the JMS route / consumer / or
>> anything, or do any changes in the application?
>>
>> Also you can try upgrading to a newer Camel version.
>>
>> On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
>>
>>> Hi,
>>>
>>> After few days of exploitation, JMS ReplyManager could not find the
>>> correlation request in this TimeoutMap !
>>>
>>> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
>>> same Queue, with different TimeoutMap – in the log bellow, one time we have
>>> 1 in timeout map with thread #211 and for the other threads we have 0 !
>>> How it's possible ? The result is that the reply manager doesn't find the
>>> original request in the timeout map.
>>>
>>> Thank you very much for your help.
>>>
>>> *Environnment :*
>>> Camel : 2.10.0
>>> Redhat : 6.3 (santiago)
>>> Java : java version "1.6.0_41"
>>> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>>> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>>>
>>>
>>> *LOG :*
>>>
>>> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
>>> PersistentQueueReplyManager[T2P.ENROL.R]-1]
>>> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
>>> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
>>> Early reply not found handler at attempt 1. Waiting a bit longer.
>>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 1 in the timeout map
>>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>>
>>>
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion below:
>>
>> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>>
>> broker_MON.log (333K) <http://camel.465427.n5.nabble.com/attachment/5731081/0/broker_MON.log>
>> broker_MON.log.2013-04-17 (98K) <http://camel.465427.n5.nabble.com/attachment/5731081/1/broker_MON.log.2013-04-17>
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731081.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=2>
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
> ________________________________
> If you reply to this email, your message will be added to the discussion below:
>
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731142.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]</user/SendEmail.jtp?type=node&node=5731147&i=2>
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731147.html
To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731148.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: JMS Request/Reply
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
That route seems to only have direct endpoints. Where is the JMS endpoints?
And so you are saying that it has been idle for 20 hours, and then a
new messages is being processed.
And when that happens, a new producer is created?
On Fri, Apr 19, 2013 at 2:07 PM, f.pascal <f....@pw-consultants.com> wrote:
> Hi,
>
> The route :
>
> // ------------------------------------------------------------------
> from("direct:Stecard-client.requests").routeId(this.getRouteId())
> // to STECARD
> .choice().when(_isAuditMode).to("direct:Stecard-client.auditRequest").end()
> .transform(new Expression() {
> @SuppressWarnings("unchecked")
> @Override
> public <T> T evaluate(Exchange exchange, Class<T> arg1) {
> return (T) new String(exchange.getIn().getBody(StecardMessage.class).writeData());
> }
> })
> .to(this.getStecardUri())
> .transform(new Expression() {
> @SuppressWarnings("unchecked")
> @Override
> public <T> T evaluate(Exchange exchange, Class<T> arg1) {
> return (T) StecardMessage.parseMessage(exchange.getIn().getBody(byte[].class));
> }
> })
> .choice().when(_isAuditMode).to("direct:Stecard-client.auditResponse").end()
> .end();
> // ------------------------------------------------------------------
>
>
>
> Only 3 messages Ok being routed before re-creating producer.
> Yes, the route been idle for 20 hours
>
> Thanks
> François
>
>
> De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5731136h51@n5.nabble.com]
> Envoyé : vendredi 19 avril 2013 09:09
> À : François Pascal
> Objet : Re: JMS Request/Reply
>
> Hi
>
> Can you show details of the route with the request/reply?
> And is there many messages being routed or few?
>
> And before the 20h when re-creating the producer. Has the route been
> idle for a while?
>
>
> On Thu, Apr 18, 2013 at 4:16 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=0>> wrote:
>
>> Hello Claus,
>>
>> We have put stacktrace when camel create, start or stop a JmsProducer for understand what’s append. Attached, I put the logs files and we can to see than camel recreate the JmsProducer 20 hours after camel was started but we don't understand why. Any idea ?
>>
>> Best regards
>>
>> François
>>
>>
>>
>>
>> De : Claus Ibsen-2 [via Camel] [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=1>]
>> Envoyé : lundi 15 avril 2013 18:48
>> À : François Pascal
>> Objet : Re: JMS Request/Reply
>>
>> Not sure what happens. Do you stop/start the JMS route / consumer / or
>> anything, or do any changes in the application?
>>
>> Also you can try upgrading to a newer Camel version.
>>
>> On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
>>
>>> Hi,
>>>
>>> After few days of exploitation, JMS ReplyManager could not find the
>>> correlation request in this TimeoutMap !
>>>
>>> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
>>> same Queue, with different TimeoutMap – in the log bellow, one time we have
>>> 1 in timeout map with thread #211 and for the other threads we have 0 !
>>> How it's possible ? The result is that the reply manager doesn't find the
>>> original request in the timeout map.
>>>
>>> Thank you very much for your help.
>>>
>>> *Environnment :*
>>> Camel : 2.10.0
>>> Redhat : 6.3 (santiago)
>>> Java : java version "1.6.0_41"
>>> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>>> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>>>
>>>
>>> *LOG :*
>>>
>>> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
>>> PersistentQueueReplyManager[T2P.ENROL.R]-1]
>>> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
>>> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
>>> Early reply not found handler at attempt 1. Waiting a bit longer.
>>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 1 in the timeout map
>>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>>> purge task to see if any entries has been timed out
>>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>>> are 0 in the timeout map
>>>
>>>
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion below:
>>
>> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>>
>> broker_MON.log (333K) <http://camel.465427.n5.nabble.com/attachment/5731081/0/broker_MON.log>
>> broker_MON.log.2013-04-17 (98K) <http://camel.465427.n5.nabble.com/attachment/5731081/1/broker_MON.log.2013-04-17>
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731081.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=2>
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
> ________________________________
> If you reply to this email, your message will be added to the discussion below:
> http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731136.html
> To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731142.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
RE: JMS Request/Reply
Posted by "f.pascal" <f....@pw-consultants.com>.
Hi,
The route :
// ------------------------------------------------------------------
from("direct:Stecard-client.requests").routeId(this.getRouteId())
// to STECARD
.choice().when(_isAuditMode).to("direct:Stecard-client.auditRequest").end()
.transform(new Expression() {
@SuppressWarnings("unchecked")
@Override
public <T> T evaluate(Exchange exchange, Class<T> arg1) {
return (T) new String(exchange.getIn().getBody(StecardMessage.class).writeData());
}
})
.to(this.getStecardUri())
.transform(new Expression() {
@SuppressWarnings("unchecked")
@Override
public <T> T evaluate(Exchange exchange, Class<T> arg1) {
return (T) StecardMessage.parseMessage(exchange.getIn().getBody(byte[].class));
}
})
.choice().when(_isAuditMode).to("direct:Stecard-client.auditResponse").end()
.end();
// ------------------------------------------------------------------
Only 3 messages Ok being routed before re-creating producer.
Yes, the route been idle for 20 hours
Thanks
François
De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5731136h51@n5.nabble.com]
Envoyé : vendredi 19 avril 2013 09:09
À : François Pascal
Objet : Re: JMS Request/Reply
Hi
Can you show details of the route with the request/reply?
And is there many messages being routed or few?
And before the 20h when re-creating the producer. Has the route been
idle for a while?
On Thu, Apr 18, 2013 at 4:16 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=0>> wrote:
> Hello Claus,
>
> We have put stacktrace when camel create, start or stop a JmsProducer for understand what’s append. Attached, I put the logs files and we can to see than camel recreate the JmsProducer 20 hours after camel was started but we don't understand why. Any idea ?
>
> Best regards
>
> François
>
>
>
>
> De : Claus Ibsen-2 [via Camel] [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=1>]
> Envoyé : lundi 15 avril 2013 18:48
> À : François Pascal
> Objet : Re: JMS Request/Reply
>
> Not sure what happens. Do you stop/start the JMS route / consumer / or
> anything, or do any changes in the application?
>
> Also you can try upgrading to a newer Camel version.
>
> On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
>
>> Hi,
>>
>> After few days of exploitation, JMS ReplyManager could not find the
>> correlation request in this TimeoutMap !
>>
>> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
>> same Queue, with different TimeoutMap – in the log bellow, one time we have
>> 1 in timeout map with thread #211 and for the other threads we have 0 !
>> How it's possible ? The result is that the reply manager doesn't find the
>> original request in the timeout map.
>>
>> Thank you very much for your help.
>>
>> *Environnment :*
>> Camel : 2.10.0
>> Redhat : 6.3 (santiago)
>> Java : java version "1.6.0_41"
>> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
>> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>>
>>
>> *LOG :*
>>
>> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
>> PersistentQueueReplyManager[T2P.ENROL.R]-1]
>> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
>> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
>> Early reply not found handler at attempt 1. Waiting a bit longer.
>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 1 in the timeout map
>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
> ________________________________
> If you reply to this email, your message will be added to the discussion below:
>
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> broker_MON.log (333K) <http://camel.465427.n5.nabble.com/attachment/5731081/0/broker_MON.log>
> broker_MON.log.2013-04-17 (98K) <http://camel.465427.n5.nabble.com/attachment/5731081/1/broker_MON.log.2013-04-17>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731081.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]</user/SendEmail.jtp?type=node&node=5731136&i=2>
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731136.html
To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731142.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: JMS Request/Reply
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Can you show details of the route with the request/reply?
And is there many messages being routed or few?
And before the 20h when re-creating the producer. Has the route been
idle for a while?
On Thu, Apr 18, 2013 at 4:16 PM, f.pascal <f....@pw-consultants.com> wrote:
> Hello Claus,
>
> We have put stacktrace when camel create, start or stop a JmsProducer for understand what’s append. Attached, I put the logs files and we can to see than camel recreate the JmsProducer 20 hours after camel was started but we don't understand why. Any idea ?
>
> Best regards
>
> François
>
>
>
>
> De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5730930h65@n5.nabble.com]
> Envoyé : lundi 15 avril 2013 18:48
> À : François Pascal
> Objet : Re: JMS Request/Reply
>
> Not sure what happens. Do you stop/start the JMS route / consumer / or
> anything, or do any changes in the application?
>
> Also you can try upgrading to a newer Camel version.
>
> On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
>
>> Hi,
>>
>> After few days of exploitation, JMS ReplyManager could not find the
>> correlation request in this TimeoutMap !
>>
>> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
>> same Queue, with different TimeoutMap – in the log bellow, one time we have
>> 1 in timeout map with thread #211 and for the other threads we have 0 !
>> How it's possible ? The result is that the reply manager doesn't find the
>> original request in the timeout map.
>>
>> Thank you very much for your help.
>>
>> *Environnment :*
>> Camel : 2.10.0
>> Redhat : 6.3 (santiago)
>> Java : java version "1.6.0_41"
>> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
>> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>>
>>
>> *LOG :*
>>
>> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
>> PersistentQueueReplyManager[T2P.ENROL.R]-1]
>> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
>> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
>> Early reply not found handler at attempt 1. Waiting a bit longer.
>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 1 in the timeout map
>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
>> purge task to see if any entries has been timed out
>> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
>> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
>> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
>> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
>> are 0 in the timeout map
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
> ________________________________
> If you reply to this email, your message will be added to the discussion below:
> http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5730930.html
> To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> broker_MON.log (333K) <http://camel.465427.n5.nabble.com/attachment/5731081/0/broker_MON.log>
> broker_MON.log.2013-04-17 (98K) <http://camel.465427.n5.nabble.com/attachment/5731081/1/broker_MON.log.2013-04-17>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731081.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
RE: JMS Request/Reply
Posted by "f.pascal" <f....@pw-consultants.com>.
Hello Claus,
We have put stacktrace when camel create, start or stop a JmsProducer for understand what’s append. Attached, I put the logs files and we can to see than camel recreate the JmsProducer 20 hours after camel was started but we don't understand why. Any idea ?
Best regards
François
De : Claus Ibsen-2 [via Camel] [mailto:ml-node+s465427n5730930h65@n5.nabble.com]
Envoyé : lundi 15 avril 2013 18:48
À : François Pascal
Objet : Re: JMS Request/Reply
Not sure what happens. Do you stop/start the JMS route / consumer / or
anything, or do any changes in the application?
Also you can try upgrading to a newer Camel version.
On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <[hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=0>> wrote:
> Hi,
>
> After few days of exploitation, JMS ReplyManager could not find the
> correlation request in this TimeoutMap !
>
> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
> same Queue, with different TimeoutMap – in the log bellow, one time we have
> 1 in timeout map with thread #211 and for the other threads we have 0 !
> How it's possible ? The result is that the reply manager doesn't find the
> original request in the timeout map.
>
> Thank you very much for your help.
>
> *Environnment :*
> Camel : 2.10.0
> Redhat : 6.3 (santiago)
> Java : java version "1.6.0_41"
> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>
>
> *LOG :*
>
> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
> PersistentQueueReplyManager[T2P.ENROL.R]-1]
> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
> Early reply not found handler at attempt 1. Waiting a bit longer.
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 1 in the timeout map
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]</user/SendEmail.jtp?type=node&node=5730930&i=1>
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5730930.html
To unsubscribe from JMS Request/Reply, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5730897&code=Zi5wYXNjYWxAcHctY29uc3VsdGFudHMuY29tfDU3MzA4OTd8NzUxNzMwNTM5>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
broker_MON.log (333K) <http://camel.465427.n5.nabble.com/attachment/5731081/0/broker_MON.log>
broker_MON.log.2013-04-17 (98K) <http://camel.465427.n5.nabble.com/attachment/5731081/1/broker_MON.log.2013-04-17>
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5731081.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: JMS Request/Reply
Posted by "f.pascal" <f....@pw-consultants.com>.
Thanks,
No, we have not touched anything. The problem appears after a few days.
I found in the logs (bellow) messages saying that recreated a camel producer
for the jms uri
LOG :
[2013-04-15 11:07:54,818] [Camel (Sae) thread #197 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
purge task to see if any entries has been timed out
[2013-04-15 11:07:54,818] [Camel (Sae) thread #197 -
JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
are 0 in the timeout map
[2013-04-15 11:07:54,824] [Camel (t2pAdmin) thread #30 -
JmsConsumer[pwgroup.t2pAdmin]]
org.apache.camel.impl.DefaultProducer.doStart(DefaultProducer.java:69) DEBUG
org.apache.camel.component.jms.JmsProducer - Starting producer:
Producer[jms.sae.steria://queue:T2P.ENROL.Q?disableTimeToLive=false&replyTo=T2P.ENROL.R&replyToType=Exclusive&requestTimeout=3000&timeToLive=1200000&useMessageIDAsCorrelationID=true]
[2013-04-15 11:07:54,826] [Camel (t2pAdmin) thread #30 -
JmsConsumer[pwgroup.t2pAdmin]]
org.apache.camel.component.jms.reply.ReplyManagerSupport.doStart(ReplyManagerSupport.java:217)
TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
Using timeout checker interval with 1000 millis
[2013-04-15 11:07:54,828] [Camel (t2pAdmin) thread #30 -
JmsConsumer[pwgroup.t2pAdmin]]
org.apache.camel.component.jms.reply.PersistentQueueReplyManager.createListenerContainer(PersistentQueueReplyManager.java:152)
DEBUG org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
Using exclusive queue:T2P.ENROL.R as reply listener:
org.apache.camel.component.jms.reply.ExclusivePersistentQueueMessageListenerContainer@3c4cd18b
--
View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897p5730933.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: JMS Request/Reply
Posted by Claus Ibsen <cl...@gmail.com>.
Not sure what happens. Do you stop/start the JMS route / consumer / or
anything, or do any changes in the application?
Also you can try upgrading to a newer Camel version.
On Mon, Apr 15, 2013 at 1:55 PM, f.pascal <f....@pw-consultants.com> wrote:
> Hi,
>
> After few days of exploitation, JMS ReplyManager could not find the
> correlation request in this TimeoutMap !
>
> It's clear that we have various JmsReplyManagerTimeoutChecker threads on the
> same Queue, with different TimeoutMap – in the log bellow, one time we have
> 1 in timeout map with thread #211 and for the other threads we have 0 !
> How it's possible ? The result is that the reply manager doesn't find the
> original request in the timeout map.
>
> Thank you very much for your help.
>
> *Environnment :*
> Camel : 2.10.0
> Redhat : 6.3 (santiago)
> Java : java version "1.6.0_41"
> Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
> MQ Series : serveur : 7.0.1.3 et client 7.5.0
>
>
> *LOG :*
>
> [2013-04-15 11:07:55,786] [Camel (Sae) thread #173 -
> PersistentQueueReplyManager[T2P.ENROL.R]-1]
> org.apache.camel.component.jms.reply.ReplyManagerSupport.waitForProvisionCorrelationToBeUpdated(ReplyManagerSupport.java:188)
> TRACE org.apache.camel.component.jms.reply.PersistentQueueReplyManager -
> Early reply not found handler at attempt 1. Waiting a bit longer.
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,809] [Camel (Sae) thread #209 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,810] [Camel (Sae) thread #174 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,819] [Camel (Sae) thread #197 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,837] [Camel (Sae) thread #211 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 1 in the timeout map
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,840] [Camel (Sae) thread #184 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,845] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #205 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,846] [Camel (Sae) thread #172 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:157)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - Running
> purge task to see if any entries has been timed out
> [2013-04-15 11:07:55,869] [Camel (Sae) thread #201 -
> JmsReplyManagerTimeoutChecker[T2P.ENROL.R]]
> org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:167)
> TRACE org.apache.camel.component.jms.reply.CorrelationTimeoutMap - There
> are 0 in the timeout map
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-Request-Reply-tp5730897.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen