Bug 1631775 - [GSS](6.4.z) HORNETQ-1575 Fix new connection establishment after failure during failover
Summary: [GSS](6.4.z) HORNETQ-1575 Fix new connection establishment after failure duri...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.21
Hardware: All
OS: Linux
unspecified
high
Target Milestone: CR1
: EAP 6.4.22
Assignee: Radovan Netuka
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6422-payload 1631773 1638078
TreeView+ depends on / blocked
 
Reported: 2018-09-21 14:29 UTC by Matthew Robson
Modified: 2023-09-14 04:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:40:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1575 0 Major Closed Fix new connection establishment after failure during failover 2020-02-25 14:33:54 UTC

Description Matthew Robson 2018-09-21 14:29:21 UTC
Description of problem:
With camel and the standard jms component there is a reconnection issue if the application is waiting inside a blocking operation (sending a message) when live is killed. When the client fails over the connection, the thread is unblocked and an exception is thrown to the client. The client (camel) handles that by closing the sessions and creating a new connection. Because the connection factory used to build the camel route only has a connector pointing to the live server, the new connection will always fail while the live server is down.

11:58:42,885 ERROR [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (Camel (camel-1) thread #3 - JmsConsumer[testQueue1]) Could not refresh JMS Connection for destination 'testQueue1' - retrying using FixedBackOff

{interval=5000, currentAttempts=6, maxAttempts=unlimited}
. Cause: Failed to create session factory; nested exception is HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.]


Version-Release number of selected component (if applicable):

6.4 CP21

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

No failures

Additional info:

Comment 1 Matthew Robson 2018-09-21 14:32:47 UTC
PR: https://github.com/hornetq/hornetq/pull/2132

Comment 3 Peter Mackay 2019-05-08 20:26:52 UTC
Regression tests passed
Verified with EAP 6.4.22.CP.CR1

Comment 4 Red Hat Bugzilla 2023-09-14 04:38:49 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.