PI28889: TRANSACTION LOG IS CREATED IN THE WRONG LOCATION

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The transaction log is created in the server configuration
  directory rather than the output directory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  Liberty Profile who are using Transactional *
  *                  capabilities and have separate directories  *
  *                  for configuration and output                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Liberty transaction log is created in   *
  *                      the configuration directory and not the *
  *                      output directory                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the transactional capabilities of the Liberty
  profile, the local transactional log is created in the server's
  configuration directory and not in the server output location.
  If the server configuration directory has been set as a read-
  only, this will cause errors attempting to create the
  transaction log.
  

Problem conclusion

• The Liberty profile has been enhanced so that the transactional
  log will be created in the server output directory rather than
  the server configuration directory.  By default, the server
  configuration directory is defined as
  WLP_USER_DIR/servers/serverName, and the server output directory
  is defined as the same location (see http://www-
  01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.webspher
  e.wlp.iseries.doc/ae/twlp_admin_customvars.html?lang=en-us for
  details).  If either the WLP_USER_DIR variable or the
  WLP_OUTPUT_DIR variable are set to values other than their
  defaults such that the server configuration directory and server
  output directory are different, and the default transaction log
  location is used, then the transaction log location will move.
  In this case, if the Liberty server is not quiesced prior to
  applying the fix and restarting so that all global in-flight
  transactions are completed, all in-flight transactions will be
  lost. This may cause other resource managers involved in in-
  flight transactions to continue to lock resources such as
  dtabase records. To resolve this, copy the tranlog folder from
  the old location in the server configuration directory to the
  new location in the server output directory to ensure in-flight
  transactions can be completed.  The fix for this APAR is
  currently targeted for inclusion in fix pack 8.5.5.4.  Please
  refer to the Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980.
  

Temporary fix

• This can be worked around by ensuring the server's configuration
  directory is writable by the application server.
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP