Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Application Server 7 2004Q2 Update 1 Standard and Enterprise Edition Error Messages Reference 

Chapter 14
Inter ORB Protocol

This chapter lists error messages that originate from the Internet Inter-ORB Protocol.


IOP

Internet Inter-ORB Protocol is a transport-level protocol used by both Remote Method Invocation (RMI) over IIOP and Common Object Request Broker Architecture (CORBA).

This chapter contains error messages that occur in the IOP system.

IOP5001

Severity

SEVERE

Description

An exception occurred while creating the security mechanism list based on the deployer-specified configuration information.

Action

Analyze the System, as described on (more...) .

IOP5002

Severity

SEVERE

Description

An exception occurred while initializing the IIOP SSL socket factory in the server.

Action

Analyze the System, as described on (more...) .

IOP5003

Severity

SEVERE

Description

An exception occurred while initializing the IIOP SSL socket factory in the application client.

Action

Analyze the System, as described on (more...) .

IOP5004

Severity

SEVERE

Description

This error could occur due to one of the following reasons:

  • Unable to set SSL cipher suites after connecting to the server.
  • Unable to set server socket for client authentication.

Action

Check SSL settings for the listener.

IOP5006

Severity

SEVERE

Description

An exception occurred while creating an SSL socket connection.

Action

Check the host and port settings.

IOP5007

Severity

SEVERE

Description

An IO exception occurred while reading the security.properties file. There may be a problem with setup.

Action

Analyze the System, as described on (more...) .

IOP5009

Severity

SEVERE

Description

An exception occurred while initializing the transaction service on the server.

Action

Analyze the System, as described on (more...) .

IOP5010

Severity

SEVERE

Description

An exception occurred while creating a portable object adapter (POA) on the server.

Action

Analyze the System, as described on (more...) .

IOP5011

Severity

SEVERE

Description

A request arrived for an EJB object that does not exist. It may have been removed.

Action

Ensure that the removal-timeout-in-seconds element in the sun-ejb-jar.xml file is a stateful session bean.

See Also

EJB Developers Guide.

IOP5012

Severity

SEVERE

Description

A runtime exception occurred during server execution.

Action

Analyze the System, as described on (more...) .

IOP5013

Severity

SEVERE

Description

An exception occurred while creating a CORBA reference to EJBHome or EJBObject.

Action

Analyze the System, as described on (more...) .

IOP5015

Severity

SEVERE

Description

A runtime exception occurred while setting a system property.

Action

Analyze the System, as described on (more...) .

IOP5016

Severity

SEVERE

Description

The security service is unregistered and therefore exists at interception point.

Action

You may be using Common Secure Interoperability version 2 (CSIv2)1 features via RMI-IIOP client. However, this is not supported. Use the application client container for CSIv2 features.

1It is a protocol used to address the requirements of CORBA security for interoperable authentication, delegation and privileges.

IOP5017

Severity

WARNING

Description

Security service is not registered and therefore the status is not set.

Action

You may be using Common Secure Interoperability version 2 (CSIv2)1 features via RMI-IIOP client. However, this is not supported. Use the application client container for CSIv2 feature.

See Also

Message ID IOP5016.

1It is a protocol used to address the requirements of CORBA security for interoperable authentication, delegation and privileges.

IOP5018

Severity

SEVERE

Description

An exception occurred while importing the user name. Server fails while trying to create Generic Security Service Username Password (GSSUP), API-GSSUPName, from an exported user name sent by the client.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

See Also

Message ID IOP5019.

IOP5019

Severity

SEVERE

Description

An exception occurred while creating an exported user name. The server or client fails while creating an exported user name as an array of one or more UTF-8 characters.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

See Also

Message ID IOP5018.

IOP5020

Severity

SEVERE

Description

An exception occurred while getting the password. This occurs while extracting the user name and password from PasswordCredential and converting the string to UTF-8 format.

Action

Make sure the user name or password specified is not null. If the problem persists, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5021

Severity

SEVERE

Description

An exception occurred while encoding. The token that contains the user name and password is encoded in CDR format.

Action

Make sure the server or client user name and password are correct. If the problem persists, Analyze the System, as described on (more...) with exception stack trace.

IOP5022

Severity

SEVERE

Description

An exception occurred while decoding. This exception occurs when a CDR stream is decoded to create an object that contains the user name and password.

Action

Make sure the user name and password specified in the client or server are correct. If the problem persists, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5023

Severity

SEVERE

Description

An exception occurred while getting user name and password.

Action

The specified user name or password is either null or not in UTF-8 format. Verify the user name and password.

IOP5024

Severity

SEVERE

Description

An IO exception occurred in IIOP. This exception occurs when the security.properties file is not present in the classpath of the application server or application client container.

Action

Verify and add the security.properties file in the classpath of the application server or application client container.

IOP5026

Severity

SEVERE

Description

More than one credential is specified. You may be using an unsupported feature by using CSIv21 via RMI-IIOP client.

Action

Use application client container.

1It is a protocol used to address the requirements of CORBA security for interoperable authentication, delegation and privileges.

IOP5027

Severity

SEVERE

Description

An invalid security mechanism occurred. The client does not conform to the target bean's configured security policies.

Action

Verify the sun-ejb-jar.xml and sun-acc.xml files and validate the data.

IOP5029

Severity

SEVERE

Description

An exception occurred while creating authentication token – Generic Security Service Username Password (GSSUP) from the specified credential.

Action

Make sure the user name and password specified is not null. If the problem persists, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5030

Severity

SEVERE

Description

An exception occurred while creating and adding the CDR encoded client identity token to the service context field.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

IOP5031

Severity

SEVERE

Description

A service context exception occurred.

Action

Refer to the stack trace in the exception. This indicates the reason that the service context on the client was not extracted from the message. Analyze the System, as described on (more...) with the exception stack trace information.

IOP5032

Severity

SEVERE

Description

Reply message not CompleteEstablishContext or ContextError. An illegal message was sent from the client while establishing a context with the client.

Action

Refer to SecurityException in the log that follows this message for a better description of possible reasons. Analyze the System, as described on (more...) with the exception stack trace information.

IOP5033

Severity

SEVERE

Description

Unknown identity assertion type. An error occurred while creating an identity in the security context for a user on the server.

Action

Refer to the SecurityException in the log that follows this message, and correct the security identity token.

IOP5034

Severity

SEVERE

Description

The message received is not an EstablishContext message. An illegal message was sent from the client while establishing a context with the client.

Action

Check the implementation on the client ORB to find possible issues with the protocol version mismatch, for example, in sequence messages. If you are using the Sun Java System client and server ORBs, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5035

Severity

SEVERE

Description

An error occurred while creating a JAAS subject credential. This error occurs when the message from the client contained an authentication token and JAAS was unable to create an authentication or subject credential.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

IOP5036

Severity

SEVERE

Description

A security exception occurred in IIOP. The system was unable to create an identity credential because the message from the client contained an identity token.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

IOP5037

Severity

SEVERE

Description

A generic exception occurred in IIOP during the creation of identity credential.

Action

Refer to the SecurityException in the log following this exception. Analyze the System, as described on (more...) with the exception stack trace information.

IOP5038

Severity

SEVERE

Description

Could not propagate user name or password required by target when using run as identity. There was no client authentication token found in the security context and an exception, SecurityMechanismException occurred.

Action

A client authentication on the server is required. Send a client authentication to the server.

IOP5039

Severity

SEVERE

Description

The specified mechanism type sent by the client for identification is not supported.

Action

See documentation for server and client security mechanisms.

IOP5040

Severity

SEVERE

Description

Could not lookup the domain name of the specified IP address.

Action

Verify the network and configuration settings. Check the IP address and domain information. The client's domain may not be supported.

IOP5041

Severity

SEVERE

Description

Cannot find principal information in the subject. The security mechanisms are trying to extract the principal from the subject.

Action

Check client authentication token propagated. Also refer to security documentation for supported security mechanisms.

IOP5042

Severity

SEVERE

Description

Cannot find credential information in subject. While authenticating the client and getting its identity, the security mechanism on the server was able to extract the principal from the subject. However, it could not determine any credential from the subject.

Action

Check the client authentication token that is propagated.

See Also

Message ID IOP5041. Also see the Administrator's Guide to Security for supported security mechanisms.

IOP5043

Severity

SEVERE

Description

An exception occurred while creating ASContext. The client authentication does not conform to the security policies set on the server.

Action

Check the application security configuration and make sure the client meets the minimum security required.

IOP5044

Severity

SEVERE

Description

An exception occurred while getting the peer certificate chain. The user and the server are using an SSL connection. However, the server security mechanism is unable to retrieve the certificate from the user to evaluate trust.

Action

Ensure that the client certificate is available on the client and meets the security requirements as per the server requirements.

IOP5045

Severity

SEVERE

Description

An invalid security mechanism exception occurred.

Action

See the exceptions reported along with this message for solution. If the problem persists, Analyze the System, as described on (more...) .

IOP5046

Severity

SEVERE

Description

An invalid ID token is sent.

Action

Analyze the System, as described on (more...) .

IOP5047

Severity

SEVERE

Description

A security exception occurred. The client does not conform to the target bean's configured security policies.

Action

Verify the sun-ejb-jar.xml and sun-acc.xml files. Validate the security information and roles assigned in the XML files.

IOP5048

Severity

SEVERE

Description

An authentication exception occurred. The client authentication does not conform to the security policies set on the server.

Action

Check the application’s security configuration and make sure the client meets the minimum security required.

IOP5049

Severity

SEVERE

Description

A login exception occurred. An attempt to login to the server by authenticating the client with the specified subject and credential failed.

Action

Analyze the System, as described on (more...) with the exception stack trace information.

IOP5050

Severity

SEVERE

Description

An unknown message type exception occurred.

Action

Analyze the System, as described on (more...) .

IOP5051

Severity

SEVERE

Description

More than one TAG_CSI_SEC_MECH_LIST tagged component was found. The client has sent more than one security mechanism. However, only one mechanism can be specified.

Action

Specify only one security mechanism.

IOP5052

Severity

SEVERE

Description

An error occurred while starting bootserver.

Action

Analyze the System, as described on (more...) .

IOP5054

Severity

WARNING

Description

A request arrived on a disabled connection. The IIOP listener port is disabled in server.xml. A regular CORBA request message sent by the client is rejected.

Action

If the IIOP listener port was disabled on purpose, then no action is required. However, if it was not disabled on purpose, enable the IIOP listener port in server.xml.

IOP5055

Severity

SEVERE

Description

Could not create listener on the specified port and host.

Action

Validate host and port settings in server.xml. Also verify if there is a process listening on that port. If yes, then change the iiop-listener element in server.xml to a different port and restart the server. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

IOP5056

Severity

SEVERE

Description

An exception occurred while creating the listener.

Action

Check host and port settings. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

See Also

Message ID IOP5055.

IOP5057

Severity

SEVERE

Description

An unknown host present and hence could not create a listener.

Action

Make sure the host used in server.xml has a valid hostname/IP address. If the problem persists, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5058

Severity

SEVERE

Description

An unknown host present.

Action

Check host settings. The host name may be incorrect.

See Also

Message ID IOP5057.

IOP5071

Severity

WARNING

Description

This exception can occur during the findPOA() call in the ORB.

Action

Restart the server. If restart option is not available, Analyze the System, as described on (more...) with the exception stack trace information.

IOP5073

Severity

WARNING

Description

The port specified in the iiop-listener element in server.xml is not a number between 1 and 65535.

Action

Make sure the iiop-listener element in server.xml is a number in the range specified. Modify the server.xml and restart the server.

IOP5074

Severity

WARNING

Description

The port specified in the iiop-listener element in server.xml is not a number between 1 and 65535, even though the listener is disabled.

Action

Make sure that all the disabled iiop-listener elements in server.xml is a number in the range specified above. Modify the server.xml and restart the server.

IOP5075

Severity

WARNING

Description

The steady-thread-pool-size specified in the ORB element in server.xml is not a positive number (greater than or equal to1).

Action

Make sure that steady-thread-pool-size specified in the ORB element in server.xml is not a positive number. Modify the value in server.xml and restart the server.

IOP5076

Severity

WARNING

Description

The max-thread-pool-size specified in the ORB element in server.xml is not a positive number (greater than or equal to1).

Action

Make sure that max-thread-pool-size specified in the ORB element in server.xml is not a positive number. Modify the value in server.xml and restart the server.

IOP5077

Severity

WARNING

Description

This exception can occur if the idle-thread-timeout-in-seconds specified in the ORB element in server.xml is not a positive number.

Action

Make sure that idle-thread-timeout-in-seconds specified in the ORB element in server.xml is not a positive number. Modify the value in server.xml and restart the server.



Previous      Contents      Index      Next     


Copyright 2004 Sun Microsystems, Inc. All rights reserved.