PM32552: J2CA0144W AND J2CA0114W GENERATED IN SYSTEMOUT.LOG EVEN THOUGH MAPPINGCONFIGALIAS AND AUTHDATAALIAS ARE CONFIGURED

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The following two warnings may appear in the SystemOut.log
  file...
  
  
  [10-11-2 13:39:53:329 CST] 0000002e PrivExAction  W   J2CA0144W:
  No mappingConfigAlias found for connection factory or datasource
  JMS\testQCF\JMSManagedConnection@0.
  
  [10-11-2 13:39:53:335 CST] 0000002e PrivExAction  W   J2CA0114W:
  No container-managed authentication alias found for connection
  factory or datasource JMS\testQCF\JMSManagedConnection@0.
  
  
  
  However, the resources.xml file confirmed that both are
  configured on the Queue Connection Factory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server version 6.1                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Customers who use the built-in JMS      *
  *                      provider or built-in MQ provider , as   *
  *                      part of XA Recovery will see            *
  *                      J2CA0114W and J2CA0144W messages.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  As a part of XARecovery , we try to get the Started RA .
  But WMQ resource adapters having a key ending with
  "builtin_mqprovider" do not have a started RA instance at
  runtime. The traces would have the following messages :
  
  [10-11-2 13:39:53:329 CST] 0000002e PrivExAction  W   J2CA0144W:
  No mappingConfigAlias found for connection factory or datasource
  JMS\testQCF\JMSManagedConnection@0.
  
  [10-11-2 13:39:53:335 CST] 0000002e PrivExAction  W   J2CA0114W:
  No container-managed authentication alias found for connection
  factory or datasource JMS\testQCF\JMSManagedConnection@0.
  

Problem conclusion

• To support recovering transactions involving WMQ providers the
  code now ignores the requirement that a started RA must exist.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.41  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP