Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

****************************************************************
* USERS AFFECTED: All users of IMS TM Resource Adapter *
* V10.5.2. *
****************************************************************
* PROBLEM DESCRIPTION: Problems/enhancements in APAR PM79883: *
* *
* 1. Excessive messages are logged when *
* the MFS path is chosen during *
* development time in Rational *
* Application Developer. *
* *
* 2. During Callout processing, *
* Message-driven beans (MDBs) running on *
* the WebLogic server do not reconnect *
* properly. *
* *
* 3. Incorrect data store name is used *
* for ACK during resume tpipe operations. *
* *
* 4. SSL sockets cannot reconnect after *
* the host system goes down. *
* *
* 5. The adapter does not expose the *
* clientID to the user. *
* *
* 6. SSL sockets hang during connection. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
Problems/enhancements in APAR PM79883 (IMS TM RA V10.5.3):
1. Excessive messages are logged when the MFS path is chosen
during development time in Rational Application Developer.
2. MDBs running on the WebLogic server do not reconnect after
being disconnected.
3. During resume tpipe operations, if the response comes from a
data store that is different from the original data store,
the ACK incorrectly goes to the original data store.
4. When MDBs are disconnected due to the host system going down,
the SSL sockets are not properly disconnected and therefore
cannot be reconnected for subsequent communications.
5. Currently, the resource adapter does not expose the clientID
to the user.
6. SSL sockets hang during connection time.

Problem conclusion

GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Problems addressed in APAR PM79883 (IMS TM RA V10.5.3):
1. The adapter is fixed to not print out the excessive logging
messages.
2. Modified the code to set the reconnect time value to 5
seconds instead of IMMEDIATE.
3. The adapter is modified to use the datastore name on the
response from the host in the subsequent ACK.
4. The adapter is modified to disconnect the SSL socket
properly before sending in a message over to the host.
5. The adapter is modified to expose the clientID to the user
through the IMSConnectionMetaData class. From the IMSConnection
class the user can call the IMSConnectionMetaData class. Then,
using the IMSConnectionMetaData class, the user can call the
'getClientID' method to retrieve the clientID, which can be
either user provided or generated by the adapter.
.
Example:
.
Connection connection = null;
IMSConnectionMetaData meta =
(IMSConnectionMetaData)connection.getMetaData();
String clientID = meta.getClientID();
6. The adapter is modified to use a timeout value during
connection time to prevent the SSL sockets from hanging. In the
case of IMS callout, a default value of 60 seconds is used. For
non-callout case, the socket timeout value from the
InteractionSpec is used.