PM62866: MISLEADING ATTRIBUTE NAME WHILE CREATING MAIL SESSION USING PROPERTIES FILE BASED CONFIGURATION.

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Creating a mail session using the Admininstrative Console :
  
  Resources -> mail -> Mail Sessions > New
  
  and the required attributes are
  *name
  *JNDIname.
  
  
  But to create the same mail sesssion using the Properties file
  based configuration template, we have to the use the following
  attribute.
  
  description=!{mailSessionJNDI2} #required
  
  Where mailSessionJNDI2 is the JNDI name.
  
  The attribute JNDIname doesnt exist in the properties file based
  configuration template, passing the JNDI name in the
  description attribute is misleading .
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Misleading attributes name in the       *
  *                      mail session template while using the   *
  *                      properties file based configuration     *
  *                      to create a new mail session.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When creating a new mail session using Admininstartive Console,
  the required attributes are
  *name
  *jndiName.
  But to create the same mail session using the Properties file
  based configuration template, the required attributes
  "jndiName" and "name" are missing.  User needs to specify
  the jndiName in the "description" attribute and mail session
  name in the "String" attribute (there is no String attribute)
  to workaround the problem such as:
  description=mailSessionJNDI2 #required
  String=mailSession2
  Where mailSessionJNDI2 is the JNDI name and mailSession2 is
  the mail session name.
  The attributes jndiName and name do not exist in the
  properties file based configuration template and passing the
  JNDI name in the description attribute is misleading .
  

Problem conclusion

• There are some typo errors in the existing mail session
  template which cause the jndiName and name attributes to be
  misleading when using the properties file based configuration
  template to create a new mail session. You need to specify
  a new system property to use the updated properties
  file based configuration template to create a new mail session.
  
  The system property name is:
  com.ibm.websphere.management.useUpdatedPropertyFiles
  
  The system property can be set via wsadmin or administrative
  console.
  
  When running the wsadmin local mode, the system property
  can be set through the wsadmin -javaoption <system property>
  command such as:
  
  wsadmin -conntype none -lang jython -javaoption
  "-Dcom.ibm.websphere.management.useUpdatedPropertyFiles=true"
  
  When running the wsadmin in the server process (connecting to
  server process), the system property can be set in wsadmin
  AdminTask.setJVMSystemProperties command.  It can be set
  through the administrative console as per the following link
  too.
  
  
  http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?t
  opic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/xrun_jvm
  .html
  
  After the system property is set,  please save the changes and
  do sync node if this is a federated cell, and restart each
  server for it to take effect.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.4 and 8.5.0.1.  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

• R800 PSY

     UP

• R850 PSY

     UP