We have 2 JMS components configured in our camel context: one that works with
Solace, and the other one that works with IBM MQ.
When Camel runs DefaultShutdownStrategy, it waits for 300 seconds and
then... still nothing happens. Seems like it hangs in
AbstractJmsListeningContainer#doStop() at 319
Mmh.. In future there might be a lot of places, so I don't think it's a good
idea (though Camel context is up and running because server gets the
messages, the error happens when it tries to send them).
I tried to explicitely invoke ProducerTemplate#start() before sending, and
it's the same - it w
No, it's 2.7 :) So it looks like the connection is too slow today on my
machine and Camel spends too much time to initiate the connection with
broker while first sendin(!). My test thinks that it's too late and
application doesn't respond and closes everything down. And now the magic
happens - ther
Dunno why, but from time to time my integration tests fail with:
/java.lang.IllegalStateException: ProducerTemplate has not been started
at
org.apache.camel.impl.DefaultProducerTemplate.getProducerCache(DefaultProducerTemplate.java:674)
at
org.apache.camel.impl.DefaultProducerTempl
Didn't know, thanks a lot! Will try.
--
View this message in context:
http://camel.465427.n5.nabble.com/interceptFrom-ref-tp4283865p4284572.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yes, but I'm talking about interception, not about route.
--
View this message in context:
http://camel.465427.n5.nabble.com/interceptFrom-ref-tp4283865p4283904.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I guess would be logically correct to include such an attribute to refer to
the endpoints instead of copy/pasting of URIs.
--
View this message in context:
http://camel.465427.n5.nabble.com/interceptFrom-ref-tp4283865p4283865.html
Sent from the Camel - Users mailing list archive at Nabble.com.
When I receive a JMS message, I want to check it whether it's valid:
- if it is, then I want to send acknowledgement to the replyTo and to
continue the workflow
- if it's not valid, then I want to send back an error and stop the chain
of execution
What mechanism in Camel would you advise? Seems l
I've replaced Spring's CachingConnectionFactory with my own implementation
that simply takes Solace implementation and triggers its method:
protected Connection doCreateConnection() throws JMSException {
try {
return factory.createTopicConnection();
} catch (MessageC
Tried Apache MQ with via its VM protocol - it works..
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-doesn-t-listen-to-JMS-channel-tp4263097p4263859.html
Sent from the Camel - Users mailing list archive at Nabble.com.
At last I've found some differents in log (I've switched on TRACE). This line
is always present and periodically appears again and again:
2011-03-25
11:14:28,157[][TRACE][fs/notifications][.jms.JmsMessageListenerContainer] -
Consumer [Cached JMS MessageConsumer:
com.solacesystems.jms.SolTopicSubscr
The broker is Solace firmware. It has its own format of messages, and in the
same time it provides a means to use JMS API (I presume it converts its
format to JMS somehow), thus I really doubt it uses Spring in any way.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-does
Though after posting this I've tried couple of other times and seems like
this log is always present, so it's not relevant. But still couldn't fight
the issue - messages simply don't arrive.
stanislav bashkirtsev
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-doesn-t-li
So if I run my very simple app that listens to the topic 10 times, 9 times
camel just doesn’t receive messages. I’m looking at the log in DEBUG mode
and the difference I’ve noticed is that when it does start normally there
are lines like this:
2011-03-24 14:55:38,838[][INFO ][main
][nec
14 matches
Mail list logo
