CODEWITHSUNDEEP
jbossjmshornetq
Elad Eldor
Elad Eldor

Reputation: 831

ClientSession is closed by HornetQ

we encountered the following exception in HornetQ (with HornetQ 2.2.5 GA with JBoss 4.3.3, with the InVM connector. both the client and the server are on the same machine):

hornetq-failure-check-thread,Connection failure has been detected: Did not receive data from invm:0. the error code is 3 (which is HornetQException.CONNECTION_TIMEDOUT).

this causes the RemotingServiceImpl.FailureCheckAndFlushThread to run, which writes the following log multiple times:

Client connection failed, clearing up resources for session 95406085-7b3a-11e2-86d3-005056b14e26

note that in our application we reuse our ClientSessions. we have one instance of ClientSession per connection (we open multiple connections, one per each client), and the above problem caused one of the sessions to be closed.

after reading this post: Connection timeout issues - Connection failure has been detected

I understood that we need to configure the following on our ServerLocator instance (which is used to create the ClientSessionFactory that creates our ClientSessions):

ServerLocator locator = HornetQClient.createServerLocatorWithoutHA(connectorConfig);
locator.setClientFailureCheckPeriod(Long.MAX_VALUE);
locator.setConnectionTTL(-1);

this configurtion solved the problem, and the above error was not reproduced.

our problem is the following - in case the sessions will be closed again by HornetQ from some other reason, how can we create new sessions instead of the closed ones?

I'm asking this because after we found the session was closed (and before we set the clientFailure and clientTTL values), we tried to create a new session by calling the createSession(false, true, true) method on the ClientSessionFactory instance (we create that instance upon system startup only once and resue it since) and it failed with the following error:

HornetQException[errorCode=0 message=Failed to create session]

so we didn't succed to create new sessions, and the only solution was restarting the JBoss.

note that we can't restart our application on the client site, so we need to find a way to create new sessions in case the old ones were closed from some reason.

Upvotes: 4

Views: 5735

Answers (1)

Clebert Suconic
Clebert Suconic

Reputation: 5383

Instead of doing that, you should probably configure retry and use a proper value, that way your connection will be reconnected.

But since you're using inVM, and as long as you don't stop the server you should be fine with that configuration. However if you intend to restart just the server, you could use reconnectionRetry (-1) and the session would be reattached or recreated seamesly to you.

anyway I would recommend you going to a newer version beyond 2.2.5.

Upvotes: 2

Related Questions