[
https://jira.nuxeo.org/browse/NXP-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéfane Fermigier updated NXP-2326:
-----------------------------------
Component/s: Infrastructure
> Make JMS connections more resilient
> -----------------------------------
>
> Key: NXP-2326
> URL: https://jira.nuxeo.org/browse/NXP-2326
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 5.1.4
> Reporter: Thierry Delprat
> Assignee: Alexandre Russel
> Fix For: 5.1.7
>
>
> Probably because of firewalls :
> 2008-04-17 00:00:29,213 WARN [org.jboss.mq.Connection] Connection failure,
> use javax.jms.Connection.setExceptionListener() to handle this error and
> reconnect
> org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
> (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
> at
> EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.io.IOException: ping timeout.
> ... 3 more
> See : http://wiki.jboss.org/wiki/IGetIOExceptionPingTimeoutHowDoIFixIt
> According to JBoss Wiki, this should not happend as we use the
> ResourceAdapter.
> We may set the Exception Handler on each connection ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
