PH52245: ERROR MESSAGE NEEDS TO BE MORE CLEAR

APAR status

• Closed as program error.

Error description

• Customer has a configuration where MQ objects are bound like in
  this sample:
  .
  [12/17/21 16:09:15:777 CET] 00000001 ResourceMgrIm I WSVR0049I:
  Binding A.A.W as a/b/c/d
  ...
  [12/17/21 16:09:15:810 CET] 00000001 ResourceMgrIm I WSVR0049I:
  Binding A_W_MQ_Q as a/b/c/d/mq
  
  In this scenario the following error is hit:
  [12/17/21 16:09:15:837 CET] 00000001 ResourceMgrIm E WSVR0017E:
  Error encountered binding the J2EE resource, A_W_MQ_Q, as
  a/b/c/d/mq from <WAS_Path>/resources.xml
  javax.naming.NotContextException: Name "a/b/c/d", relative to
  context "<Cluster_Name>" is already bound to an object which is
  not a context. [Root exception is
  javax.naming.NameAlreadyBoundException: a/b/c/d [Root exception
  is org.omg.CosNaming.NamingContextPackage.AlreadyBound:
  IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0]]
  
  Object names were changed in the above messages.
  For this kind of scenario we understand that root cause is a
  configuration error, but product could issue a message like "the
  jndi name /aaa/bbb/ccc is already taken", but instead, it says
  "the jndi /aaa/bbb/ccc is already bound to an object which is
  not a context" which is not clear enough to customer knows what
  was the real cause.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  version 8.5.5 or later                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When we try to bind an object to a name *
  *                      which not a naming context then the     *
  *                      error                                   *
  *                      message shown needs to be more clear.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer has a configuration where MQ objects are bound like in
  this sample:
  .
  [12/17/21 16:09:15:777 CET] 00000001 ResourceMgrIm I WSVR0049I:
  Binding A.A.W as a/b/c/d
  ...
  [12/17/21 16:09:15:810 CET] 00000001 ResourceMgrIm I WSVR0049I:
  Binding A_W_MQ_Q as a/b/c/d/mq
  In this scenario the following error is hit which is not clear
  enough to customer knows what was the real cause.
  [12/17/21 16:09:15:837 CET] 00000001 ResourceMgrIm E WSVR0017E:
  Error encountered binding the J2EE resource, A_W_MQ_Q, as
  a/b/c/d/mq from <WAS_Path>/resources.xml
  javax.naming.NotContextException: Name "a/b/c/d", relative to
  context "<Cluster_Name>" is already bound to an object which is
  not a context.
  

Problem conclusion

• The code was fixed to make the error message more clear.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.24 and 9.0.5.16.
  
  For more information, see 'Recommended Updates for WebSphere
  Application Server': https://www.ibm.com/support/pages/node/7155
  

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