CORBA system exception minor codes

In the CORBA model for exception handling, a system exception might contain an associated minor code. This topic provides details of these minor codes, grouped by system exception.

Minor codes are used in several ways:

Each minor code consists of a 5-digit hexadecimal vendor identifier followed by a 3-digit hexadecimal value, which indicates the specific reason for the system exception. A minor code containing a vendor identifier of 0x4F4D0 is an Object Management Group (OMG)-assigned minor code. A minor code containing a vendor identifier of 0x49420 is an IBM-assigned minor code.

Specific minor code values are meaningful only within the context of the particular system exception in which they are contained. Minor code values might be used in more than one system exception type, but the system exception is used to interpret the minor code value. For example, the minor code value 0x4F4D0001 means "the repository ID is already defined in the Interface Repository" when associated with a BAD_PARAM exception, However, the same code means "unable to locate and/or use the appropriate Value Factory" when associated with a MARSHAL exception.

In this topic, the description of each minor code consists of:

The System Exception (in alphabetical order)
A description of the problem that caused the error.
User Response: Actions are needed to resolve the problem, if appropriate.
Minor Code number (prefixed with vendor ID). In some cases, the minor code number is followed by the following entries:
  • Error Text A string that identifies the minor code.
  • Details Details for this specific minor code, in the context of the System Exception.

Minor code definitions

BAD_CONTEXT
Explanation: Cannot find a specified CORBA::Context property.
User Response: Ensure that the specified property name exists in the context object.
0x49420047 SOMDERROR_CtxNoPropFound
Error Text: A string that identifies the minor code.
Details: This error occurs if an invalid property name was passed to CORBA::Context::delete_values.
BAD_INV_ORDER
Explanation: Operations were invoked in an improper order.
User Response: Verify the proper order of the operations and correct the order.
0x4942005D SOMDERROR_BadInvOrder
Details: This is the generic bad invocation order minor code.
0x4F4D0004
Details: The Object Request Broker (ORB) has been shut down, but an ORB operation was requested.
0x4F4D000A
Details: There is an invalid Portable Interceptor call or a valid Portable Interceptor call in an invalid order.
0x4F4D000B
Details: A request was made to add a new service context to the Portable Interceptor. The service context was found to exist already but the requester specified that it not be replaced.
BAD_OPERATION
Explanation: A bad class, method, operation, or object reference was encountered.
User Response: Verify the operation and make sure the correct bindings exist.
0x49420045 SOMDERROR_ClassNotFound
Details: Cannot convert an Interoperable Object Reference (IOR) to an object. The class name was unknown or the proxy factory cannot be created. Verify the class implementation and verify that the bindings exist.
0x4942004DSOMDERROR_WrongRefType
Details: The wrong type of object reference was used. Probably, a client invoked an operation on an object in a server and the object did not support the invoked method. To support a given operation, a server must be compiled and linked with the server-side C++ bindings for the interface that introduces that IDL operation. This error also occurs when a server application invokes CORBA::BOA::get_id and passes in a proxy object rather than a local object. Verify that a server is compiled and linked with all of the server-side C++ bindings for the interfaces.
BAD_PARAM
Explanation: An application supplied an invalid parameter to an operation.
User Response: Check the error log for a message that indicates which operation was given the invalid parameter. Check the documentation for that operation and verify that the passed parameters are valid.
0x49420048 SOMDERROR_BadParm
Details: This is the generic bad parameter minor code.
0x4F4D0001
Details: Interface Repository. An operation specified an object with an ID that already exists in the Interface Repository (IR) database container.
0x4F4D0002
Details: Interface Repository. Repository ID is defined already in the Interface Repository.
0x4F4D0003
Details: Interface Repository. Name is used already in the context in the Interface Repository.
0x4F4D0004
Details: Interface Repository. The target is not a valid container.
0x4F4D0005
Details: Interface Repository. The name clash is in inherited context.
0x4F4D0017
Details: A Portable Interceptor operation cannot find the specified service context.
0x4F4D0018
Details: A null object was passed into register_initial_reference().
0x4F4D0019
Details: A Portable Interceptor operation cannot find the specified tagged component on the target object.
0x4F4D001A
Details: A Portable Interceptor operation was given a profile ID that is not supported. The supported profile id's are IOP::TAG_INTERNET_IOP and IOP::TAG_MULTIPLE_COMPONENTS.
COMM_FAILURE
Explanation: A communications failure occurred. Possible reasons are:
  • A process might have received an unknown or unexpected message type or message content.
  • The process might have encountered a low-level communications failure in attempting to send a message or binding to a socket.
  • An unexpected broken connection might have occurred.
User Response:See the details of the following minor codes.
0x49420038 SOMDERROR_HostAddress
Details: Cannot map a host name on a different machine to a host address. Ensure that the host to which this process is attempting to communicate is known and can be reached via TCP/IP. Ping the remote host by the host name.
0x4942003ESOMDERROR_CannotConnect
Details: A client process cannot connect to a server process when attempting to invoke a method on a proxy to an object residing in that server process. Ensure that the location service daemon is running. Ensure that the object reference is still valid. Ping the remote machine to see that the two machines are connected.
0x49420042SOMDERROR_CommunicationsError
Details. This is the generic communications error minor code. Ensure that communications resources are functioning properly. For example, when using TCP/IP, ping the remote host. Ensure that the process has not failed due to an application error.
0x49420059SOMDERROR_Server_Connection_Broken
Details. The location service daemon might not restore a connection to a server whose connection was broken.
DATA_CONVERSION
Explanation: Cannot perform codeset translation for character data or wide character data. This results from a failure of the translation utilities. It can occur if the process is using a non-standard codeset that does not map to an OSF codeset. Also, it can occur if there is no common codeset between the client and the server.
User Response: When using the translationEnabled configuration setting, ensure that the NLS-related configuration settings are correctly set. Verify that both the client and the server are using standard codesets and that there is some codeset supported by both the client and the server. Refer to the codeset reference section of this document.
0x49420051 SOMDERROR_DataConversion
Details: This is the generic data conversion minor code.
INITIALIZE
Explanation:A configuration or installation error is causing a problem during initialization.
User Response: See the details of the following minor codes.
0x49420015 SOMDERROR_CouldNotLoadLibrary
Details: Client initialization cannot load a required library. Check the activity log for more information.
0x49420035 SOMDERROR_InvalidProtocolInformation
Details: The configuration of the communications protocol is incorrect. Supported communication protocols are TCP/IP and IPC. Verify that at least one valid communications protocol image is configured. Also, verify that for each communications protocol configured, the csProfileTag and portNumber are set and that the portNumber is not use by another process on the system. (The portNumber is the port on which the location service daemon or server listens for requests.) The csProfileTag and portNumber settings must be unique.
0x49420036 SOMDERROR_SOMDDAlreadyRunning
Details: The location service daemon cannot begin listening because another process is using the port number. Probably another instance of the process is running already. If no other location service daemon is running, reconfigure the location service daemon to listen on a different port number.
0x49420037 SOMDERROR_InvalidConfigSetting
Details: A configuration setting or environment variable was not properly set. An error log entry indicates which configuration setting or environment variable is not properly set. If the reported variable is WASORBTOP, verify that the product was properly installed (Set WASORBTOP to the directory where the product was installed.)
0x49420046 SOMDERROR_ServerAlreadyExists
Details. A server cannot register with the location service daemon during CORBA::BOA::impl_is_ready. Another server might be registered already with the location service daemon under the server UUID. Only one instance of a particular server can run on a given host. Terminate the duplicate server process. If no duplicate server process is running, restart the location service daemon.
0x4942004E SOMDERROR_SOMDDNotRunning
Details: A server cannot register with the location service daemon (in CORBA::BOA::impl_is_ready) because it cannot contact the daemon. It is possible that the daemon is not running or the daemon is running on a port number that is different from what the server expected. Verify that the location service daemon is running and is listening on the correct port.
INTERNAL
Explanation: An internal error condition was detected.
User Response: See the details of the following minor codes. Report the occurrence to technical support.
0x49420034 SOMDERROR_NotImplemented
Details: The invoked operation is not supported in the product or is not valid on the target object. Check that the operation being invoked and the target object run-time type are compatible. Refer to the documentation for the operation for information about restrictions.
0x4942004B SOMDERROR_Internal
Details: Report the problem to technical support.
0x4942004F SOMDERROR_ServerInterrupt
Details: The server has been shut down by an invocation of the interrupt_server() method.
0x4F4D0001
Details: A Portable Interceptor operation cannot find an object key on the target object.
0x4F4D0002
Details: A Portable Interceptor operation cannot find an object key on the target most derived object.
INTF_REPOS
Explanation:An Interface Repository operation has encountered a problem or error.
User Response: See the details of the following minor codes.
0x49420052 SOMDERROR_IRIncoherent
Details: An Interface Repository object references another named Interface Repository object that no longer resides in the IR database. Delete and rebuild the WASORBIR database to correct the problem.
0x49420053 SOMDERROR_IRInternal
Details: An internal programming or database error has occurred. Delete and rebuild the WASORBIR database to correct the problem.
0x49420054 SOMDERROR_IRDuplicateEntry
Details. There was an attempt to create an Interface Repository object when one already exists in the Interface Repository with either the same CORBA::RepositoryId or the same name within that container. Change the ID (CORBA::RepositoryId) parameter that is passed to the 'create_xxxx' operation or change the ID (CORBA::RepositoryId) value of the object already in the IR that is causing the duplicate entry error using the ID write operation. Or, change the name of one of the two conflicting objects within that container.
0x49420055 SOMDERROR_IREntryNotFound
Details: This error might occur when the client is attempting to use Dynamic Invocation Interface (DII) with interfaces that are not accessible in the Interface Repository. Check that the client has access to the Interface Repository and that the interfaces being used are defined in the Interface Repository.
0x49420056 SOMDERROR_IRCannotConnect
Details: Cannot find or access the Interface Repository database. This can occur during a call to resolve_initial_references (with an input string of InterfaceRepository). Verify that the Interface Repository database exists and is properly configured. Also, verify that the directory or file permissions associated with the Interface Repository database allow access by the user receiving the exception. If the database is remote, check that the ID and password are properly configured for that database using configuration properties com.ibm.CORBA.irUserid and com.ibm.CORBA.irPassword.
0x49420057 SOMDERROR_IRNameReUse
Details. Another thread or process is updating the needed portion of the Interface Repository database. Retry the Interface Repository operation that generated the exception at a later time.
INV_OBJREF
Explanation: An invalid object reference was used. For example, if a client uses a reference to an object that no longer exists or cannot be located in the specified server, this error is sent from the server to the client. This error can occur in a client process if an invalid string is passed to CORBA::ORB::string_to_object. It occurs in a server if CORBA::BOA::create is called with input ReferenceData that does not map to any known exportable object residing in that server. The error occurs if CORBA::BOA::get_id is invoked on a nil object reference or on an object reference that has no associated ReferenceData in that server. Also, this error occurs if a server attempts to export an object reference that has no associated ReferenceData in that server or if a client attempts to pass a local object as a parameter on a remote method invocation.
User Response: In a client process, verify that the object that the object reference refers to still exists. Verify that strings passed to CORBA::ORB::string_to_object have not been corrupted or truncated. There is no maximum length for an object reference string. Some lengths, however, are larger than others. Verify that servers do not attempt to export objects that are not handled by the application adaptor of the server.
0x49420040 SOMDERROR_BadObjref
Details: This is the generic invalid object reference minor code.
MARSHAL
Explanation: An error has occurred when trying to marshall or demarshall method parameters or return results as part of a remote invocation. This can occur when demarshalling an inout sequence if the length of the incoming sequence is greater than the original sequence maximum. It alsocan occur if methods are not invoked on the ServerRequest object in the correct order when you use the Dynamic Skeleton Interface (DSI).
User Response: Verify that inout sequences do not exceed the sequence maximum. If using the DSI, verify that operations are invoked in the correct order on the ServerRequest object.
0x4942003C SOMDERROR_MarshalingError
Details: This is the generic marshal error minor code.
0x4F4D0001 SOMDERROR_MarshalingError
Details: Unable to locate or use the appropriate Value Factory.
NO_MEMORY
Explanation: A memory allocation failed
User Response: Verify that the process does not have a memory leak. Increase system resources.
0x4942000A SOMDERROR_NoMemory
Details: This is the generic no memory minor code.
NO_RESOURCES
Explanation: There is a system resources problem. A needed resource is unavailable.
User Response: See the details of the following minor codes.
0x4942000D SOMDERROR_CouldNotStartThread
Details: Cannot start a thread. Check the log for more information. Increase system resources.
0x49420014 SOMDERROR_CouldNotStartProcess
Details. The location service daemon cannot start a server process. Check the log for more information.
0x4F4D0001
Details: A Portable Interceptor operation was invoked that is not supported.
NO_RESPONSE
Explanation: Some process has timed out.
User Response: See the details of the following minor codes.
0x4942003B SOMDERROR_NoMessages
Details: No request messages were pending in a server process when the server invoked CORBA::BOA::execute_next_request or CORBA::BOA::execute_request_loop with the CORBA::BOA::SOMD_NO_WAIT flag. Wait for a request to become available or use the CORBA::BOA::SOMD_WAIT flag to call CORBA::BOA::execute_next_request or CORBA::BOA::execute_request_loop.
0x4942003D SOMDERROR_CommTimeOut
Details. A process has timed out while waiting for a response from another process. Typically, a client receives this error when the server has terminated or is hanging due to an application error. Verify that the other process is still active. To increase the timeout period, change the requestTimeout property in the configuration.

Note: Setting the requestTimeout property to zero results in an infinite timeout.

0x4942005A : SOMDERROR_Server_Registration_Timeout
Details: A server has been started by the location service daemon, but that server has not registered within the timeout period.
OBJECT_NOT_EXIST
Explanation: A locate request failed to find the requested object or the object's server is not running.
User Response: Verify that the correct object reference is being used and the correct server is running.
0x4942005C SOMDERROR_ObjectNotExist
Details: This is the generic object not exist minor code.
PERSIST_STORE
Explanation: There is a Problem with the Implementation Repository.
User Response: See the details of the following minor codes.
0x49420043 SOMDERROR_ImplRepIO
Details: Cannot access the Implementation Repository database. Verify that the Implementation Repository was correctly created and configured. Each host machine must have its own Implementation Repository.
0x49420044 SOMDERROR_EntryNotFound
Details: Cannot find an entry in the Implementation Repository when attempting to delete, update, or locate it. Verify that the specified server alias or UUID matches a server that was previously registered in the Implementation Repository.
0x4942004A SOMDERROR_DuplicateEntry
Details: The application attempted to add a duplicate entry to the Implementation Repository or attempted to update the server alias of an existing entry using a name that is not unique. The server alias does not need to be unique throughout the network, but it must be unique in each Implementation Repository. Verify that the server UUID and server alias of the ImplementationDef to be added or updated in the Implementation Repository are unique.
SQL_INFORMATION
Explanation:A SQL error occurred.
User Response: Report the problem to technical support.
0x49420058 SOMDERROR_IRSQLInformation
Details: An Interface Repository operation has caught a SQL error.
UNKNOWN
Explanation:An unknown error occurred.
User Response: Report the problem to technical support.
0x49420041 SOMDERROR_Unknown
Details: An unexpected error occurred during an operation.
0x4F4D0001
Details: An unknown user exception was detected in the Portable Interceptor.

Related reference
CORBA exceptions



Searchable topic ID:   rcor_sem
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/corba/ref/rcor_sem.html

Library | Support | Terms of Use | Feedback