ICO0005E javax.resource.spi.CommException:
ICO0005E:methodname error.
A communication error occurred during sending or receiving the IMS message.
clientID=[clientid][java_exception]

Explanation

The IMS TM resource adapter was unable to successfully complete a send and receive interaction with the target IMS Connect. The clientid in the message is the client ID of the connection on which the communication exception occurred. java_exception indicates the reason for the failure to complete the interaction.

User response

Use the client ID to help analyze the trace data from the different components that are involved. Examine java_exception to determine the reason for the failure. Some values for java_exception are described in the following table.

Table 1. Java exceptions for ICO0005E
Java exceptions Description
java.io.EOFException
Some possible reasons for the exception are:
  • The timeout value that is specified in the IMS Connect configuration member is exceeded before IMS Connect receives a response from IMS. Exceeding a timeout value typically occurs when a region is not available in IMS to run the IMS transaction that processes the client request. If so, ensure that an appropriate region is started and available to process the request. Exceeding a timeout value can also occur if the IMS application program that is associated with the transaction is stopped. If so, use the IMS command /START PROGRAM to start the IMS application program.
  • A Java™ client tries to use a previously active client (for example, a connection from the pool) for which an IMS Connect STOPCLNT command has been issued.
java.net.SocketException: Connection reset by peer: socket write error
Some possible reasons for the exception are:
  • A Java client attempts to use a connection for which the underlying socket is no longer connected to IMS Connect. The socket connection might be lost if IMS Connect is recycled, but the application server is not. After IMS Connect is restarted, the connections that were formerly successfully connected to IMS Connect are still in the connection pool. As clients attempt to reuse each of these connections, the exception java.net.SocketException is thrown, and the connection object is removed from the connection pool.

    You can change this behavior in WebSphere® Application Server by setting the purge policy of the connection factory that is used by the Java application to the entire pool.

  • TCP/IP on the host is coming down.