[JBoss JIRA] Updated: (JBESB-401) During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider]
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-401?page=all ]
Mark Little updated JBESB-401:
------------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 4.2)
> During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider]
> -----------------------------------------------------------------------------------------------
>
> Key: JBESB-401
> URL: http://jira.jboss.com/jira/browse/JBESB-401
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.0
> Environment: JBoss ESB 4.0 GA + JBoss AS 4.0.5GA - Win 2000 - Fedora Core 6
> Reporter: Bruno Georges
> Assigned To: Kevin Conner
> Fix For: 4.2 Milestone Release 2
>
>
> During Trailblazer DEMO, JMS doesn't reconnect when App Server restart: ERROR [JmsCourier] JMS error. Attempting JMS reconnect.
> ant runJMSBank
> [java] 10:00:01,759 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect
> [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
> [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
> [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> [java] at java.lang.Thread.run(Thread.java:595)
> [java] Caused by: java.io.IOException: ping timeout.
> [java] ... 3 more
> ant runESB
> [java] 09:58:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect.
> [java] javax.jms.IllegalStateException: The consumer is closed
> [java] at org.jboss.mq.SpyMessageConsumer.checkClosed(SpyMessageConsumer.java:963)
> [java] at org.jboss.mq.SpyMessageConsumer.receive(SpyMessageConsumer.java:360)
> [java] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:349)
> [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:184)
> [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:166)
> [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:246)
> [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:228)
> [java] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:114)
> [java] at java.lang.Thread.run(Thread.java:595)
> [java] 09:59:51,775 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect
> [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
> [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
> [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> [java] at java.lang.Thread.run(Thread.java:595)
> [java] Caused by: java.io.IOException: ping timeout.
> [java] ... 3 more
> [java] 09:59:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Updated: (JBESB-425) Easy proxy for EJB3, Spring-POJO, WS
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-425?page=all ]
Mark Little updated JBESB-425:
------------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 4.2)
> Easy proxy for EJB3, Spring-POJO, WS
> ------------------------------------
>
> Key: JBESB-425
> URL: http://jira.jboss.com/jira/browse/JBESB-425
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta, Documentation, Examples, Configuration
> Reporter: Mark Little
> Assigned To: Daniel Marchant
> Fix For: 4.2 Milestone Release 2
>
>
> Make it really, really easy to proxy an existing EJB3, Spring, MDB or WS onto the bus as an action.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Updated: (JBESB-446) getTemporaryReplyTo broken
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-446?page=all ]
Mark Little updated JBESB-446:
------------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 4.2)
> getTemporaryReplyTo broken
> --------------------------
>
> Key: JBESB-446
> URL: http://jira.jboss.com/jira/browse/JBESB-446
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.0
> Reporter: Mark Little
> Assigned To: Esteban Schifman
> Priority: Critical
> Fix For: 4.2 Milestone Release 2
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> In some circumstances getTemporaryReplyTo can generate an EPR that will be functionally identical to the original To EPR. If the client and service share the same transport mechanism (e.g., JMS queue) then it's possible that replies to the client may be lost because they get picked up by the service again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months