[jgroups-users] Migration to 4.0.4 with JDBC_PING

Hi,

We are trying to migrate to the latest release 4.0.4 and facing problems
with JDBC_PING.

The same scenario used to work for us while using 3.6.13 release version but
not version 4. We gracefully shutdown the nodes using spring - close the
channel and rpc dispatcher and I see that the stop on the jdbc ping protocol
is called but does not clean up the record s. Is there a way to clean up
records ourselves rather than going over jdbc. And also we will not have the
unique I'd to clean up. At least in this case we are trying to close the
entire cluster between the junit runs. Teardown. 

The "register_shutdown_hook" from FILE_PING is on Java process and we need
an ability to remove it during the teardown. Is there a way to get hold of
the protocol and stop it ourselves.

This behavior is causing issues with the subsequent tests as there is a node
still available in the database from the previous run and the cluster is not
able to elect the coordinator as the channel is closed (connection
exceptions) for the node from previous run.

Could you please let us know if we have to change something with V4 to
achieve the same behavior as in with v3. 


Thanks



--
View this message in context: http://jgroups.1086181.n5.nabble.com/Migration-to-4-0-4-with-JDBC-PING-tp11329.html
Sent from the JGroups - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot