Bug 778557 (SOA-1029)

Summary: JmsRouter should handle reconnects
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP02   
Target Milestone: ---   
Target Release: 4.2 CP03   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1029
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-17 08:14:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kevin Conner 2008-11-14 18:04:21 UTC
Date of First Response: 2008-12-04 20:37:10
project_key: SOA

Comment 1 Kevin Conner 2008-11-14 18:04:21 UTC
Link: Added: This issue depends JBESB-2191


Comment 2 Kevin Conner 2008-11-14 18:05:20 UTC
Link: Added: This issue is related to SOA-1007


Comment 3 Dana Mison 2008-12-05 01:37:10 UTC
Regards Release Notes:

Can I please have a clarification on how JMSRouter behaves in this situation now

Comment 4 Kevin Conner 2008-12-05 11:27:59 UTC
Hiya Darrin.

The JmsRouter previously obtained a single JMS session/producer which was kept for the duration of the deployment.  If a fault was reported then the session/producer would be closed by the underlying mechanisms and the JmsRouter made no attempt to acquire a new connection.

SOA-1028 helped partially in that any failed connections would not be used for the next request, but here was still no reconnect attempt made within the context of a single request.

The JmsRouter will now make an attempt to obtain a new session/producer for the request, if a failure does occur, so that it may be possible to handle transient connection problems.

Comment 5 Dana Mison 2008-12-09 02:58:01 UTC
Release Note: JmsRouter now attempts to obtain a new session/producer for a request if connection failure occurs instead of immediately closing it.

Comment 6 Jiri Pechanec 2008-12-17 08:14:44 UTC
Verified in CR5 sources