RMI-IIOP messages

To understand RMI-IIOP messages, see the following message descriptions.

JORB0011: An I/O error occurred while attempting to construct {0} from properties url, url={1}, processing continues using default property values
Explanation: An error occurred while trying to read the file identified by the com.ibm.CORBA.ClientStyleImageURL.
User Response: Make sure the file exists and is readable.

JORB0012: property {0} has invalid value {1}; using default value, {2}, instead
Explanation: The value specified for one if the properties in ClientStyleProperties is invalid, the default value is used instead.
User Response: Find out why the invalid value was specified.

JORB0013: Invalid QOP combination specified, processing continues with default values.
The specified invalid combination is: {0}
The default combination used is: {1}

Explanation: An invalid combination of Quality Of Protection attributes was specified, a valid default combination is used instead.
User Response: Find out why the invalid value was specified.

JORB0014: createKey received an unknown connection type and returned a default key. The unknown type was {0}. the default key returned is {1}.
Explanation: com.ibm.CORBA.iiop.ConnectionTable.createKey received an unknown connectionType.
User Response: Probably a programming error.

JORB0015: getConnectionKey returned false, throwing a COMM_FAILURE exception
Explanation: com.ibm.CORBA.iiop.ConnectionTable.get's call of the ConnectionIntercetor's getConnectionKey returned false.

JORB0016: getConnectionData returned null, throwing a COMM_FAILURE exception
Explanation: The ConnectionDataRef object returned by the ConnectionInterceptor contained a null pointer to its ConnectionData object.
User Response: Probably a programming error.

JORB0017: unknown connection type (value = {0}), throwing COMM_FAILURE exception
Explanation: The ConnectionInterceptor returned a ConnectionData object with an unknown connectionType.
User Response: Probably a programming error.

JORB0018: property com.ibm.CORBA.SSLKeyRingFile not found in ClientStyleProperties, KeyRingFileException thrown
Explanation: TheClientStyleProperties did not include a property named com.ibm.CORBA.SSLKeyRingFile.
User Response: Find out why no value was specified.

JORB0019: "IIOPSSLConnection.coalesceCipherSpecs(...)" returned null, INTERNAL exception thrown:
suites enables by the SLLSocket are: {0}
suites desired by ConnectionInterceptor are: {1}

Explanation: The SSLight socket does not support any of the CipherSpecs that were requested by IIOPSSLConnection.
User Response: Check to see that the correct version of SSLight is being used.

JORB0020: The SSLServerConnectionData object passed to createSSLServerSocket returned a value from getTargetSupportsQOP() that is less than 1
Explanation: The ConnectionInterceptor.getServerConnectionData returned an SSLConnectionData object with an invalid TargetSupports value.
User Response: Probably an IBM programming error.

JORB0021: The SSLServerConnectionData object passed to createSSLServerSocket returned a value from getTargetRequiresQOP() that is less than 1
Explanation: The ConnectionInterceptor.getServerConnectionData returned an SSLConnectionData object with an invalid TargetRequires value.
User Response: Probably an IBM programming error.

JORB0022: The SSLServerConnectionData object passed to createSSLServerSocket contains a TargetSupportsQOP() value that is less than its TargetRequirQOP value
Explanation: The ConnectionInterceptor.getServerConnectionData returned an SSLConnectionData object where the TargetSupportsQOP value is less than its TargetRequiresQOP value.
User Response: Probably an IBM Programming error.

JORB0023: {0} threw {1}, rethrown as an INTERNAL exception. The KeyRing class name from the ConnectionInterceptor was {2}.
Explanation: Unable to instantiate the SSLightKeyRing class.
User Response: Verify that the class appears in CLASSPATH.

JORB0024: {0} threw {1}, the CipherSuites being set were: {2}
Explanation: SSLContext.setEnabledCipherSuites failed and threw an SSLException.
User Response: Verify that the correct version of SSlight is being used.

JORB0025: "{0}" threw {1}
Explanation: IIOPSSLConnection was unable to create a new SSLSocket.
User Response: Verify that the correct version of SSLight is being used.

JORB0026: "SSLContext.setTimeout(..)" threw an SSLException when setting the {0} timeout. The value that was being set is {1}. Processing continues with value {2}.
Explanation: SSLContext.setTimeout failed, processing continues with default values.
User Response: Verify that the correct version of SSLight is being used.

JORB0027: {0} threw {1}, rethrown as an INTERNAL exception
Explanation: The method indicated in the message threw the exception indicated in the message, the exception was rethrown as an INTERNAL exception.
User Response: Probably a programming error.

JORB0028: Attempted to construct the dummy version of {0}. The dummy version should never be constructed. Probably a configuration error that attempts to use SSL on a client that does not have an SSL library, e.g. somojse.zip, installed.
Explanation: A dummy class that exists only for use at compile time was called at run time.
User Response: Verify that there is an SSLight zip file in the CLASSPATH.

JORB0029: InterfaceDef object of wrong type returned by server
Explanation: On a call to _get_interface_def, if the object returned by the server is not an InterfaceDef object, an UNKNOWN exception is thrown with this string.
User Response: Determine why the server did not return an InterfaceDef object and retry the call to _get_interface_def.

JORB0030: org.omg.CORBA._InterfaceDefStub class not available
Explanation: The class org.omg.CORBA._InterfaceDefStub is missing.
User Response: Compile ir.idl which generates _InterfaceDefStub and compile _InterfaceDefStub. Or contact your IBM service representative.

JORB0032: BAD completion status: {0}
Explanation: A SystemException was thrown with a completion status other than YES, NO, or MAYBE (0, 1, 2).
User Response: Determine why the server threw a SystemException with an invalid Completion Status and retry.

JORB0033: service(): Exception parsing host. query string={0}
Explanation: The IIOPTunnelServlet program was unable to parse the host name that was passed in from the client.
User Response: Check to ensure the host name is correct for the Server. The host name that is being passed here was taken from the IOR of the object that the server is servicing.

JORB0034: service(): Exception parsing port. query string={0}
Explanation: The IIOPTunnelServlet program was unable to parse the port name that was passed in from the client.
User Response: Check to ensure the port number is correct for the Server. The port number that is being passed here was taken from the IOR of the object that the server is servicing.

JORB0035: service(): IOException setting up client/server sockets. exception={0}
Explanation: An IOException occurred while attempting to connect to the server from the IIOPTunnelServlet program.
User Response: Make sure the server is active and is accepting requests.

JORB0036: {0}: Exception ={1}
Explanation: An Exception occurred while attempting to connect to the server from the IIOPTunnelServlet program.
User Response: Make sure the server is active and is accepting requests.

JORB0037: service(): HTTP method type "{0}" not supported, only "POST"
Explanation: The IIOPTunnelServer program only supports the HTTP POST method.
User Response: Make sure your Web Server/Servlet engine supports the POST method.

JORB0038: The IIOP IIOPTunnelServlet via HTTP servlet.
Explanation: This is the return value for the standard servlet method getServletInfo.
User Response: No action required.

JORB0039: handleRequest(): IOException occurred while attempting to redirect client request packet to server. exception={0}
Explanation: An IOException occurred while attempting to redirect client request packet to server.
User Response: Make sure the server is active and is accepting requests.

JORB0040: handleReply(): IOException occurred while attempting to redirect server reply packet back to client. exception={0}
Explanation: An IOException occurred while attempting to redirect a server reply packet back to the client.
User Response: Make sure the client is active and is accepting replies.

JORB0041: Throwable exception occurred while attempting to redirect IIOP packets. exception={0}
Explanation: A Throwable exception occurred while attempting to redirect IIOP packets.
User Response: Make sure the server and client is active.

JORB0042: com.ibm.CORBA.iiop.locate(IOR ior) was called. Should never happen
Explanation: In the IBM ORB, com.ibm.CORBA.iiop.ClientGIOP.locate(IOR ior, org.omg.CORBA.Object targetObjectProxy) should always be used instead of com.sun.rmi.ClientGIOP.locate(IOR ior). So, override the latter and throw an exception -- implies a coding error in the IBM Java ORB.
User Response: Correct the programming error.

JORB0043: invalid attempt to use getEndPoint(type,port,addr) to establish an SSL connection
Explanation: Can't set up non CLEAR_TEXT endpoints this way.
User Response: Probably a programming error.

JORB0044: ConnectionInterceptor.getServerConnectionData returned an SSLConnectionData object with an invalid ConnectionType. The invalid type was {0}. An INTERNAL exception was thrown
Explanation: ConnectionInterceptor.getServerConnectionData returned an SSLConnectionData object with an invalid ConnectionType.
User Response: Probably an IBM Programming error. Possibly a System Management configuration error.

JORB0048: No object resolver
Explanation: Before ORB.register can be called, an ObjectResolver must exist.
User Response: Contact your Systems Manager to determine why an ObjectResolver does not exist.

JORB0049: Unknown Application exception on server: {0}
Explanation: A non-CORBA exception was thrown on the server. The name of the exception is given in this string.
User Response: Determine where the exception is being thrown. If it is being thrown in application code, repair the code and retry. If it is not being thrown in application code, contact your IBM service representative.

JORB0050: UnMatched Quote exception, e={0}
Explanation: An unmatched quote error occurred while parsing the string form of a naming context path into a CosNaming NameComponent array.
User Response: Make sure the string that is being passed to the method _StandardSyntaxModelImpl.name_to_string() has the correct syntax.

JORB0051: IllegalStringSyntax exception, e={0}
Illegal position: {1}
parsed string: {2}

Explanation: An illegal syntax error occurred while parsing the string form of a naming context path into a CosNaming NameComponent array.
User Response: Make sure the string that is being passed to the method _StandardSyntaxModelImpl.name_to_string() has the correct syntax.

JORB0052: exception, e={0}
Explanation: An exception occurred while parsing the string form of a naming context path into a CosNaming NameComponent array.
User Response: Make sure the string that is being passed to the method _StandardSyntaxModelImpl.name_to_string() has the correct syntax.

JORB0053: Null ThreadPool instance in the ORB.
Explanation: ORB.getThreadPool was called, but there was no ThreadPool to get. It had never been initialized. Because ThreadPool is a plugin, this should never happen since there is a default ThreadPool.
User Response: Correct the programming error.

JORB0054: Null input parameter in ORB.setThreadPool() invocation.
Explanation: ORB.setThreadPool() was called with a null ThreadPool input parameter. The ThreadPool must always be set to a valid instance.
User Response: Correct the programming error.

JORB0055: Call to ThreadPool.startWorkerThread() after a ThreadPool.cleanup() request.
Explanation: The ORB's ThreadPool was told to stop (via the ThreadPool.cleanup() method, then it was told to do work (via the ThreadPool.startWorkerThread() method. This is an illegal sequence.
User Response: Correct the programming error.

JORB0056: Unknown Application exception on server:
Explanation: A non-CORBA exception was thrown on the server. The name of the exception is given in this string.
User Response: Determine where the exception is being thrown. If it is being thrown in application code, repair the code and retry. If it is not being thrown in application code, contact your IBM service representative.

JORB0057: BootstrapServer: the file "{0}" is not readable!
Explanation: The BootstrapServer is unable to read the Initial Services Properties file.
User Response: Ensure that read authority is granted to the administrator who is starting the BootstrapServer.

JORB0058: BootstrapServer: setting port for initial object references to: {0}
Explanation: The BootstrapServer is listening on indicated port.
User Response: Informational message - no action required.

JORB0059: BootstrapServer: reading initial services from "{0}"
Explanation: BootstrapServer read the initial services from the indicated file.
User Response: Informational message - no action required.

JORB0060: BootstrapServer: could not open "{0}" for writing: file not found!
Explanation: The BootstrapServer was unable to write to the indicated file.
User Response: Ensure that the file exists.

JORB0061: BootstrapServer: could not open "{0}" for reading: file not found!
Explanation: The BootstrapServer was unable to read the indicated file.
User Response: Ensure that the file exists.

JORB0062: BootstrapServer: caught exception while saving Properties to file "{0}": {1}
Explanation: The BootstrapServer was unable to save the indicated properties file.
User Response: Ensure the file exists and that the administrator has the correct authority.

JORB0063: BootstrapServer: caught exception while loading Properties to file "{0}": {1}
Explanation: The BootstrapServer was unable to load the indicated properties file.
User Response: Ensure the that the file exists and that the administrator has the correct authority.

JORB0064: Persistent ior port number not provided. Object references will be transient.
Explanation: The com.ibm.CORBA.LSDPort property was not set when the ORB was initialized. This will result in transient object references.
User Response: If persistent object references are desired, set the com.ibm.CORBA.LSDPort property when initializing the ORB to a value that will remain persistent on that host machine.

JORB0065: Unique server id (UUID) not set.
Explanation: The com.ibm.CORBA.ServerUUID property was not set when the ORB was initialized. The Location Service Daemon requires this property as this is the means the Location Service Daemon has of uniquely identifying a server.
User Response: Set the com.ibm.CORBA.ServerUUID property when initializing the ORB using the UUID (Universally Unique Identifier) that was assigned to the server. This value is generally assigned by the Systems Administrator.

JORB0066: Location Service Daemon listening with server id = {0} on port = {1} ...
Explanation: The Location Service Daemon is ready to accept requests on the indicated port.
User Response: Informational message - no action required.

JORB0067: Location Service Daemon failed on waiting for requests.
Explanation: The Location Service Daemon is not ready to accept requests. The Location Service Daemon was unable to enter a wait state.
User Response: Retry starting the Location Service Daemon.

JORB0068: Invalid port number. Specify a different port number.
Explanation: The port number specified is invalid.
User Response: Specify a valid port number.

JORB0069: ERROR: {0}
Explanation: The Location Service Daemon received an unexpected exception.
User Response: Examine the exception for possible user error.

JORB0070: Port {0} in use. Specify a different port number.
Explanation: The port number specified is already in use.
User Response: Specify a different port number or end the process that is using that port and then restart the Location Service Daemon.

JORB0071: Location Service Daemon is SSL enabled.
Explanation: The Location Service Daemon will be listening on an SSL enabled port.
User Response: Informational message - no action required.

JORB0072: Location Service Daemon has Firewall Plugin registered.
Explanation: The Location Service Daemon will be interacting with a Firewall. The Location Service Daemon will authorize the servers port when the server registers with the Location Service Daemon.
User Response: Informational message - no action required.

JORB0073: Server Registered: {0} : {1} : {3}
Explanation: The indicated server has been registered with the Location Service Daemon.
User Response: Informational message - no action required.

JORB0074: Server Unregistered: {0} : {1} : {3}
Explanation: The indicated server has been unregistered with the Location Service Daemon.
User Response: Informational message - no action required.

JORB0075: Location Service Daemon will start registered servers.
Explanation: The Location Service Daemon has been configured to start a registered server if a request comes in for that server and the server is not registered with the Location Service Daemon as an active server. A server is considered registered if there is an entry for the server in the IBMLSDServerRegistry.properties file.
User Response: Informational message - no action required.

JORB0076: Registered servers started by the Location Service Daemon will need to be SSL enabled.
Explanation: The Location Service has been configured to listen on an SSL enabled port. Servers that are started by the Location Service Daemon will be notified that they will need to listen on an SSL enabled port.
User Response: Informational message - no action required.

JORB0077: Registered Servers will have {0} milliseconds to start.
Explanation: The Location Service Daemon has been configured to start servers. When a server is started, the Location Service Daemon will use the indicated timeout value when waiting for a server to start.
User Response: Informational message - no action required.

JORB0078: Location Service Daemon will persistently store list of active servers to {0}.
Explanation: The Location Service Daemon has been configured to persistently store the list of active servers that are registered to the location indicated.
User Response: Informational message - no action required.

JORB0079: Location Service Daemon initializing list of active servers from {0}.
Explanation: The Location Service Daemon has been configured to persistently store the list of active servers that are registered to the location indicated. Upon startup, the Location Service Daemon used the indicated file to restore the list of active servers.
User Response: Informational message - no action required.

JORB0080: Location Service Daemon starting server {0}.
Explanation: The Location Service Daemon has started the indicated server.
User Response: Informational message - no action required.

JORB0081: Location Service Daemon storing active server list to {0}.
Explanation: The Location Service Daemon has stored the list of active servers to the persistent store that is indicated.
User Response: Informational message - no action required.