Community
Participate
Working Groups
RMITransportManager removeLocalConnection() contains code to clean up when cache-coordination is shutting down, to do this, the service name and RMIRemoteConnection should be unbound and removed from JNDI / RMI registry and the RMI runtime. If the naming unbind fails (for example, if the name was bound within a registry running on another local VM), then the RMIRemoteConnection cannot be removed from the RMI runtime, and the VM will never exit. This needs to be resolved by adding separate try/catch blocks for each operation.
Created attachment 203279 [details] Proposed patch
Patch allows an rmi runtime unexport if an unbind operation fails. This will allow a VM to exit normally.
Created attachment 203291 [details] Proposed patch (v2)
- Added improved JavaDoc comment into patch - Moved RMI runtime 'unexport' code into finally block
Created attachment 203307 [details] Updated patch
Fixed in trunk (2.4) at revision: 10073
Fixed in 2.3.1 at revision: 10074
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink