Express (Distributed operating systems), v8.0 > Reference > Messages
ORBX
ORBX0010E: Persistent IOR port number is not provided. Object references will be transient.
Explanation The com.ibm.CORBA.LSDPort property was not set when the ORB was initialized. This situation causes transient object references. Action If persistent object references are required, when initializing the ORB, set the com.ibm.CORBA.LSDPort property to a value that will remain persistent on that host machine.
ORBX0020E: Unique server ID (UUID) is not set.
Explanation The com.ibm.CORBA.ServerUUID property was not set when the ORB was initialized. The Location Service Daemon requires this property to uniquely identify a server. Action When initializing the ORB, set the com.ibm.CORBA.ServerUUID property to the UUID (Universally Unique Identifier) that was assigned to the server. The system administrator usually assigns the UUID to a server.
ORBX0030I: Location Service Daemon is listening with server ID = {0} on port = {1} ...
Explanation The Location Service Daemon is ready to accept requests on the indicated port. Action No action required.
ORBX0040E: Location Service Daemon failed on waiting for requests.
Explanation The Location Service Daemon is not ready to accept requests. It cannot enter into a wait state. Action Restart the Location Service Daemon.
ORBX0050E: ERROR: {0}
Explanation The Location Service Daemon received an unexpected exception. Action Examine the exception for a possible user error.
ORBX0060E: Port {0} is in use. Specify a different port number.
Explanation The Location Service Daemon is attempting to start listening on a port that another process is already using. Action Specify a different port number for the Location Service Daemon, or end the process that is using the port. Then restart the Location Service Daemon.
ORBX0080I: Location Service Daemon has registered a firewall plugin.
Explanation The Location Service Daemon will be interacting with a firewall. The Location Service Daemon will authorize the server's port when the server registers with the Location Service Daemon. Action No action required.
ORBX0090I: Server registered: ServerUUID={0} HostName={1} Port={2}
Explanation The indicated server has been registered with the Location Service Daemon. Action No action required.
ORBX0100I: Server unregistered: ServerUUID={0} HostName={1} Port={2}"
Explanation The indicated server has been unregistered with the Location Service Daemon. Action No action required.
ORBX0110I: Location Service Daemon will start the registered servers.
Explanation A server is considered registered if there is an entry for the server in the IBMLSDServerRegistry.properties file. 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. Action No action required.
ORBX0120I: 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 are notified that they need to listen on an SSL enabled port. Action No action required.
ORBX0130I: 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 uses the indicated timeout value when waiting for a server to start. Action No action required.
ORBX0140I: Location Service Daemon will persistently store the 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. Action No action required.
ORBX0150I: Location Service Daemon is initializing the 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. During startup, the Location Service Daemon uses the specified stored file to restore the list of active servers. Action No action required.
ORBX0160I: Location Service Daemon is starting server {0}.
Explanation The specified server is starting. Action No action required.
ORBX0170I: Location Service Daemon is storing the active server list to {0}.
Explanation The active server list is being stored in the indicated file. Action No action required.
ORBX0180I: The property {0} has a value of {1}. This is not a valid value. The number of JNIReaderThreads is set to the default value of {2}.
Explanation This message does not indicate an error. It provides configuration information for problem determination. Action No action required.
Explanation The software you are running is copyrighted property of the International Business Machines (IBM) Corporation and all use, duplication or disclosure by U.S. government users is restricted to the GSA ADP Schedule Contract between the U.S. government and the IBM Corporation. Action No action required.
ORBX0200I: Before calling the native method addConnection0, the contents of the fdConnectionMap are {0}, and the fileDescriptor for the connection being added is {1}.
Explanation This message does not indicate an error. It provides configuration information for problem determination. Action No action required.
ORBX0210I: after calling fdConnectionMap.get() with Filedescriptor {0} the returned GIOPConnection was {1}. The fdConnectionMap contains {2}.
Explanation This message does not indicate an error. It provides configuration information for problem determination. Action No action required.
ORBX0220E: None of the native code's reader threads has room in its queue for a new Socket to watch, a COMM_FAILURE was thrown.
Explanation None of the native code's reader threads have room in thrie queue for a new Socket to watch. Action Use the ORB com.ibm.CORBA.numJNIReaders custom property to add more reader threads.
ORBX0290E: service(): An exception occurred while parsing the host name. Query string={0}.
Explanation The IIOPTunnelServlet program cannot parse the host name that was received from the client. The host name was taken from the IOR of the object that the server is servicing. Action Make sure that the host name is correct for the server.
ORBX0300E: service(): An exception occurred while parsing port number. Query string={0}.
Explanation The IIOPTunnelServlet program cannot parse the port number that was received from the client. The port number was taken from the IOR of the object that the server is servicing. Action Make sure that the port number is correct for the server.
ORBX0310E: service(): IOException occurred while setting up client/server sockets. Exception={0}.
Explanation An I/O Exception occurred while attempting to connect to the server from the IIOPTunnelServlet program. Action Make sure that the server is active and is accepting requests.
ORBX0320E: {0}: Exception ={1}
Explanation An exception occurred while attempting to connect to the server from the IIOPTunnelServlet program. Action See the description of the exception for more information.
ORBX0330E: service(): HTTP method type "{0}" is not supported; only "POST" method type is supported.
Explanation The IIOPTunnelServer program only supports the HTTP POST method. Action Make sure your Web server and the servlet engine supports the POST method.
ORBX0340I: The servlet used to tunnel IIOP packets through an HTTP Server.
Explanation This message states the return value for the standard servlet method getServletInfo. Action No action required.
ORBX0350E: handleRequest(): IOException occurred while redirecting the client request packet to the server. Exception={0}.
Explanation An I/O exception has occurred. This exception is the result of a failed or interrupted I/O operation. Action Make sure the server is active and is accepting requests. We can also try to ping the target machine that you are trying to reach to make sure that the network is functioning properly.
ORBX0360E: handleReply(): IOException occurred while redirecting the server reply packet back to the client. Exception={0}.
Explanation An I/O exception has occurred. This exception is the result of a failed or interrupted I/O operation. Action Make sure the server is active and is accepting requests. We can also try to ping the target machine that you are trying to reach to make sure that the network is functioning properly.
ORBX0370E: A throwable exception occurred while redirecting the IIOP packets. Exception={0}.
Explanation An underlying transport level problem has occurred. See the description of the exception for more information. Action Make sure the server is active and is accepting requests. We can also try to ping the target machine that you are trying to reach to make sure that the network is functioning properly.
ORBX0380E: Redirector(.): Exception occurred while calling GlobalORBFactory init method. Exception={0}.
Explanation The ORB failed to initialize in response to a call to the GlobalORBFactory.init method. See the description of the exception for more information. Action Make sure the server is active and is accepting requests.
ORBX0390E: Cannot create listener thread. Exception=[ {0} ].
Explanation The ORB service could not create a listener thread. See the descripiton of the exception for more information. Action Resolve the error reported in the exception and restart the ORB service.
ORBX0400E: A ClassCastException was encountered while attempting to add a connection to a JNI Reader thread. The input stream of the connection type being passed to the reader thread could not be cast to a FileInputStream. This is most likely because the JSSE2 security provider has been configured in conjunction with JNIReaderThreads. JNIReaderThreads and the JSSE2 security provider cannot be used together; if this is the case, either unconfigure JNIReaderThreads, or change the JSSE2 security provider to JSSE.
Explanation The ORB service could not complete a connection to a JNI reader thread. See the descripiton of the exception more information. Action Resolve the error reported in the exception and restart the ORB service.