Custom WebLogic Server (WLS) Work Manager Called "Default" Throws PeerGoneException on RMI Client when Thread Becomes Stuck (Doc ID 1074689.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 9.2 to 10.3
Information in this document applies to any platform.

Symptoms

When a WebLogic Server (WLS) custom Work Manager is called "default," we have this behavior:

This indicates that there was a problem communicating with the server:

weblogic.rjvm.PeerGoneException: nested exception is:
java.io.EOFException
Exception in thread "main" weblogic.rjvm.PeerGoneException: nested exception is:
java.io.EOFException
  at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
  at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
  at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
  at examples.ejb.ejb20.basic.statelessSession.statelessSession_mt9oui_EOImpl_922_WLStub.buy(Unknown Source)
  at examples.ejb.ejb20.basic.statelessSession.Client.example(Client.java:89)
  at examples.ejb.ejb20.basic.statelessSession.Client.main(Client.java:60)

With the default work manager, the RMI client waits for response apparently without limits. This is the behavior we would like to expect also with a work manager called "default."

Note that the weblogic.rjvm.PeerGoneException is not a consequence of work manager shutdown. We have inhibited work manager shutdown configuring the shutdown trigger.

Cause

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