search

arindam-bandyopadhyay / issue-test

0 stars 0 forks source link

Reconnect does not happen when the endpoint release throws exception #31

Open arinban opened 6 years ago

arinban commented 6 years ago

When a connection with the broker fails the generic ra tries to reconnect to the broker ( if configured in the activation spec). During this time, the ra tries to release the endpoint ( stop the pool) before reconnecting to the broker. If the release endpoint ( which inturn calls afterDelivery() on the enpoint) fails then the reconnect does not happen. There are 2 issues here

1. There is a timeout in the inbound resource pool to release all the resources in the pool, but there is no timeout for releasing a single resource. So ideally the total pool release timeout should be divided across the resources in the pool ( simplest solution of course).

2. If releasing one of the resources in the pool causes an exception, ( which is not handled now) then the other resources are not released properly. This indirectly affects the reconnection feature in the following way. When an existing MQ connection throws an exception then the ReconnectHelper in the RA tries to reconnect to the broker, before doing this the jms resource pool is stopped and reinitialized, and if there is an exception while stopping the pool ( which is dependendent on releasing the endpoint) then the pool does not get re-initialized and the reconnection does not happen. So, the exceptions need to be handled appropriately.

This issue can can be reproduced by installing a broker on a remote machine and the app server and ra on one machine and then causing a network outage when the messages are in transit.

Environment

Operating System: All Platform: All

Affected Versions

[v1.6]

arinban commented 6 years ago

Original Issue:https://github.com/javaee/glassfish-genericjmsra/issues/24 Raised By:@glassfishrobot Created at:Fri May 19 03:15:17 IST 2006 Assigned To:@glassfishrobot

arinban commented 6 years ago

@glassfishrobot Commented on Fri May 19 03:15:17 IST 2006 Reported by rampsarathy

arinban commented 6 years ago

@glassfishrobot Commented on Thu Jun 15 08:02:23 IST 2006 rampsarathy said: changing to INVALID

arinban commented 6 years ago

@glassfishrobot Commented on Thu Jun 15 08:04:18 IST 2006 rampsarathy said: incorrectly marked as INVALID, so re-opening

arinban commented 6 years ago

@glassfishrobot Commented on Mon Mar 30 06:52:53 IST 2009 marogl said: Created an attachment (id=2) Example of fails

arinban commented 6 years ago

@glassfishrobot Commented on Mon Mar 30 06:52:52 IST 2009 File: [issue 24.txt](https://java.net/jira/secure/attachment/12201/issue 24.txt) Attached By: marogl

arinban commented 6 years ago

@glassfishrobot Commented on Fri May 19 03:15:17 IST 2006 Was assigned to rampsarathy

arinban commented 6 years ago

@glassfishrobot Commented on Mon Apr 24 13:02:28 IST 2017 This issue was imported from java.net JIRA GENERICJMSRA-24