IM Instances (IM Consoles, Infocenter, IMWS) Slow Memory Leak With jGroup ChannelNotConnectedException or org.jgroups.protocols.FD_SOCK Errors

(Doc ID 1542884.1)

Last updated on NOVEMBER 03, 2015

Applies to:

Oracle Knowledge - Version to [Release 8.1 to 8.4]
Information in this document applies to any platform.


IM Instances (IM Consoles, Infocenter, IMWS) heap usage steadily and slowly increases over time with below jGroup errors (depending on the sending-end or recieving-end) frequently shown up in the IM wrapper logfile:


2013/02/28 04:27:37.706 | 139834190 [Thread-3] ERROR er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer  - Failed to send remote changes: er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer$LocalChange@7d88bb55.
2013/02/28 04:27:37.706 | ChannelNotConnectedException
2013/02/28 04:27:37.706 | at org.jgroups.JChannel.checkClosedOrNotConnected(
2013/02/28 04:27:37.706 | at org.jgroups.JChannel.send(




2013/02/28 12:28:48.326 | 84103938 [FD_SOCK pinger,InquiraEOFGroup,] ERROR org.jgroups.protocols.FD_SOCK  - socket address for could not be fetched, retrying



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms