Content starts here

IIOP Subsystem Messages

The IIOP1.0 catalog contains messages in the range BEA-002000 - BEA-002499. Messages in this catalog are part of the weblogic.iiop Internationalization package and the weblogic.iiop Localization package.

BEA-002000(retired)

Error:

BEA-002001

Info: Received an unknown message type.

Cause

This should not occur. This indicates that the client is sending garbaged messages. It might also indicate that malicious third parties are trying to access the server using IIOP.

Action

Contact Oracle Customer Support.

BEA-002002

Info: Failed to parse method name methName.

Description

The server was unable to find a suitable method implementation for the name in the request.

Cause

This can happen for a variety of reasons. Normally, it is because the caller made a request for a non-existent method. Alternatively, the IDL mangling of the method name may be ambiguous, so WebLogic Server cannot decide which method to call.

Action

If the IDL mangling is causing a problem, try changing the name of the method. In particular, names such as getSomedata() (where somedata is also the name of an attribute or method) can cause problems. Also, some bugs with name mangling in exist in JDK 1.3.1. Try using a JDK 1.4 client.

BEA-002003

Error: Unable to send the message: ioe.

Description

An IOException occurred while preventing transmission of the IIOP message.

Cause

Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action

Verify the client-server network connection is working.

BEA-002004(retired)

Warning: retired sname simpl thr

BEA-002005

Critical: OutOfMemoryError in adapter: thr.

Description

The server has run out of memory.

Cause

This is often caused by marshalling mismatches between client and server and is generally a bug in either client or server or both.

Action

Restart the server and contact Oracle Customer Support.

BEA-002006

Error: Cannot scavenge idle connections, ex

Description

The server was unable to create the connection scavenger.

Cause

The server was unable to schedule a trigger to watch for idle IIOP connections. The fact that it was unable to do so indicates some core failure in the server.

Action

Restart the server. If this occurs again, contact Oracle Customer Support.

BEA-002024

Debug: Exception on socket ioe.

Description

A low-level communication exception occurred while sending a message.

Cause

Internal debug.

Action

None.

BEA-002025

Debug: Exception on socket thr.

Description

A low-level communication exception occurred while processing an incoming message.

Cause

Internal debug.

Action

None.

BEA-002008

Info: Failed to export sname. The following exception occurred: ioe.

Description

The server tried to export a remote object before marshalling it and was unable to do so.

Cause

This is most often caused by the server being unable to find or generate an IIOP stub for the remote object. Make sure that CORBA objects have corresponding _Stub classes in the server classpath. RMI-IIOP object stubs should be generated automatically.

Action

For CORBA objects, ensure that idlj was run on the server class. For RMI-IIOP objects, contact Oracle Customer Support.

BEA-002009(retired)

Error: retired e

BEA-002010(retired)

Error: retired problem

BEA-002011

Error: Failed to marshal exception problem: reason.

Description

The server was unable to marshal an exception for transmission to the caller. A generic SystemException will be sent instead.

Cause

The server could not find appropriate exception definitions in its classpath. For CORBA exceptions, the application must contain the Exception Helper classes as well as the exception classes.

Action

Add missing exception classes to the application.

BEA-002012

Error: Failed to send exception problem: thr.

Description

The server was unable to send the appropriate exception back to the caller but sent a generic SystemException instead.

Cause

This only happens if the connection between the client and server was very unreliable.

Action

Verify the client-server network connection is working. Contact Oracle Customer Support.

BEA-002013

Error: Complete failure to send exception problem: thr.

Description

The server was unable to send the appropriate exception back to the caller and also failed to send a generic SystemException.

Cause

Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action

Verify the client-server network connection.

BEA-002014

Info: IIOP subsystem enabled.

Description

The IIOP subsystem is operational and is listening for incoming IIOP requests.

Cause

The IIOP subsystem is operational and is listening for incoming IIOP requests.

Action

No action required.

BEA-002015

Error: Using javax.rmi.CORBA.UtilClass util; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.

Description

The server was unable to install the WebLogic Server version of javax.rmi.CORBA.UtilDelegate.

Cause

Some application code, or a foreign ORB, set the system property javax.rmi.CORBA.UtilClass or tried accessing javax.rmi.CORBA.Util functions before the IIOP subsystem had initialized.

Action

The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.

BEA-002016

Error: Using javax.rmi.CORBA.PortableRemoteObjectClass pro, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.

Description

The server was unable to install the WebLogic Server version of javax.rmi.CORBA.PortableRemoteObjectDelegate.

Cause

Some application code, or a foreign ORB, set the system property javax.rmi.CORBA.PortableRemoteObjectClass or tried accessing javax.rmi.PortableRemoteObject functions before the IIOP subsystem had initialized.

Action

The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.

BEA-002017

Info: LocateRequest is onoroff.

Description

This indicates whether the server will send IIOP LocateRequest messages in order to obtain object references for remote objects. Some foreign application servers do not handle LocateRequest messages properly and others require LocateRequest messages.

Cause

This is an informational message.

Action

No action required.

BEA-002018

Info: Default GIOP version is 1.version

Description

The default version of the GIOP protocol that will be used by the IIOP subsystem, in general, should be set to 1.2. However, some C++ ORBs decode GIOP 1.2 incorrectly and in this case other GIOP versions can be tried.

Cause

This is an informational message.

Action

No action required.

BEA-002019

Info: LocationForward policy is policy.

Description

The LocationForward policy indicates whether requests for the name service will redirect the caller to a different name service object reference within the cluster.

Cause

This is an informational message.

Action

No action required.

BEA-002020(retired)

Info: Connection idle timeout is timeouts.

Description

The number of seconds that connections can remain idle before being closed automatically by the server. Most ORBs should transparently re-open closed connections but some cannot. In this case, the connection idle timeout may need to be set to a higher value.

Cause

This is an informational message.

Action

No action required.

BEA-002021

Info: SecurityService registered under where.

Description

This indicates the location in JNDI where the server has bound the IIOP security service. This is a proprietary IIOP extension that can be used by foreign ORB clients that do not support CSIv2 to perform client authentication.

Cause

This is an informational message.

Action

No action required.

BEA-002022

Warning: Could not bind SecurityService ex.

Description

The IIOP subsystem was unable to bind the proprietary IIOP security service into JNDI.

Cause

This is an internal JNDI problem.

Action

Contact Oracle Customer Support.

BEA-002023

Warning: Could not resolve SendingContext RunTime: ex.

Description

The SendingContext RunTime provided by the remote server was not resolvable. This will prevent the interoperation of evolved classes.

Cause

The client provided an invalid object reference for SendingContext RunTime.

Action

Contact Oracle Customer Support.

BEA-002026

Info: Transaction mechanism is mech.

Description

The IIOP subsystem will use the CORBA OTS for transaction propagation by default. If you enable JTA, or another transaction mechanism, then WebLogic Server will be forced to use that mechanism for transaction propagation. JTA for IIOP is non-standard and not interoperable with non-WLS application servers.

Cause

This is an informational message.

Action

No action required.

BEA-002027

Error: Complete failure to re-write exception from problem: reason.

Description

The server was unable to marshal an exception for transmission to the caller and was also unable to marshal a generic SystemException.

Cause

This error should not occur.

Action

Contact Oracle Customer Support.

BEA-002028

Warning: An OTS error occurred: str, thr.

Description

An Object Transaction Service (OTS) error occurred.

Cause

OTS errors are generally not bugs but always result in exception information being lost when propagated to the caller. Thus, the root cause is always logged,so that system administrators can determine the real cause. OTS errors are generally caused by some transaction subsystem operation (for instance, a transaction being rolled back).

Action

Make sure this is an expected error.

BEA-002029

Debug: OTS: msg

Description

Debug message concerning the operation of OTS.

Cause

Internal debug.

Action

None.

BEA-002030

Debug: Transport: msg

Description

Debug message concerning the sending and receiving of IIOP messages.

Cause

Internal debug.

Action

None.

BEA-002031

Debug: Marshal: msg

Description

Debug message concerning the format of sent and received IIOP messages.

Cause

Internal debug.

Action

None.

BEA-002032

Debug: Marshal: msg, thr

Description

Debug message concerning the format of sent and received IIOP messages.

Cause

Internal debug.

Action

None.

BEA-002033

Info: Codeset for type data set to cs, OSF registry entry osf.

Description

Indicates the default native codesets that will be used by the server for string and wide string data. Some foreign ORBs incorrectly decode the native default codesets used by WebLogic Server.

Cause

This is an informational message.

Action

No action required.

BEA-002034

Debug: Naming: msg

Description

Debug message concerning the operation of the server CosNaming implementation.

Cause

Internal debug.

Action

None.

BEA-002035

Debug: Security: msg

Description

Debug message concerning the security of sent and received IIOP messages.

Cause

Internal debug.

Action

None.

BEA-002036

Debug: Replacer: msg

Description

Debug message concerning the replacement of IORs with Stubs and vice versa.

Cause

Internal debug.

Action

None.

BEA-002037

Info: CosNaming Service registered under where.

Description

This indicates the location in JNDI where the server has bound the IIOP CosNaming service. It is necessary to bind CosNaming in a clustered environment so that references hold information about all members of the cluster.

Cause

This is an informational message.

Action

No action required.

BEA-002038

Warning: Could not bind the CosNaming Service ex.

Description

The IIOP subsystem was unable to bind the IIOP CosNaming service into JNDI.

Cause

This is an internal JNDI problem.

Action

Contact Oracle Customer Support.

BEA-002039

Warning: Replacer: msg

Description

Warning message concerning the replacement of IORs with Stubs and vice versa.

Cause

The replacer did not have enough information to do proper replacement.

Action

Contact Oracle Customer Support.

BEA-002040(retired)

Info: Connection pending timeout is timeouts.

BEA-002041

Warning: Connection attempt was rejected because IIOP is not enabled on this channel.

Description

The Connection attempt was rejected because IIOP is not enabled on this channel or Listen Address.

Cause

The Connection attempt was rejected because IIOP is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.

Action

Enabled IIOP.

BEA-002042

Debug: Connection: msg

Description

Debug message concerning the socket connections used for IIOP messages.

Cause

Internal debug.

Action

None.

BEA-002043

Warning: Naming exception: e

Description

Debug message concerning the operation of the server CosNaming implementation.

Cause

An standard exception was thrown by the naming implementation.

Action

None.

  Back to Top