in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5676000.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration
://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5676000.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http
.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5676000.html
Sent from the Camel - Users mailing list archive at Nabble.com.
in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5667039.html
Sent from the Camel - Users mailing list archive at Nabble.com.
jee:jndi-lookup id=mqJmsConnectionFactoryJNDI jndi-name=java:wmqcf
/
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5667039.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http
-JMS-connection-being-created-for-every-message-tp5637735p5667139.html
Sent from the Camel - Users mailing list archive at Nabble.com.
configuration that pooling was in the resource adapter
(the MQ RA has a default of 10 maxConnections).
But when Camel closes the connection this somehow seems to close the RA's
underlying connection, too.
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5664989.html
Sent from the Camel - Users mailing list archive at Nabble.com.
)
at
org.springframework.jms.connection.SingleConnectionFactory.createSession(SingleConnectionFactory.java:406)
Has anybody an idea what that means?
I guess I should try the MQ connection pool instead of Spring's.
Thanks,
Juergen
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message
)
at
org.springframework.jms.connection.SingleConnectionFactory.createSession(SingleConnectionFactory.java:406)
Has anybody an idea what that means?
I guess I should try the MQ connection pool instead of Spring's.
Thanks,
Juergen
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message
Hi,
we found that Camel together with the JMS component over Websphere MQ is
quite slow, it takes up to a second for Camel to forward a message.
There is an old bug which might explain this behaviour:
New JMS connection being created for every message
https://issues.apache.org/jira/browse/CAMEL
with the JMS component over Websphere MQ is
quite slow, it takes up to a second for Camel to forward a message.
There is an old bug which might explain this behaviour:
New JMS connection being created for every message
https://issues.apache.org/jira/browse/CAMEL-604
I did a trace of MQ within Camel
12 matches
Mail list logo
