PM65396: IMPROVED MESSAGE FROM VMM FOR PROTOCOL MISMATCH

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

• Improved message from virtual member manager (VMM) for protocol
  mismatch
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: VMM does not return the exact root      *
  *                      cause of an LDAP Connection exception.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When VMM tries to connect with Ldap and the connection attempt
  fails, VMM throws an exception
  "com.ibm.websphere.wim.exception.WIMConfigurationException:
  CWWIM5020E  Could not connect to the ldap" without any root
  cause. The root cause for this failure is only logged in
  traces. For example if the Ldap Port is not valid, VMM simply
  throws
  com.ibm.websphere.wim.exception.WIMConfigurationException:
  com.ibm.websphere.wim.exception.WIMConfigurationException:
  CWWIM5020E  Could not connect to the
  ldap://<<ldaphost>>:<<port>>
  repository using properties:
  [port=<<port>>],[ldapServerType=IDS],[bindDN=<<bindDN>>],[host=<
  <host>>],[certificateMapMode=exactdn],[sslConfiguration=null],[s
  ecurityDomainName=admin],[certificateFilter=null],[sslEnabled=fa
  lse],[connectTimeout=20],[bindPassword=****],[authentication=sim
  ple],[id=<<LDAP Repository Id>>],
  

Problem conclusion

• The root cause of the exception is now appended to the top
  level error message. For example if the Ldap Port is not
  valid, VMM now throws
  com.ibm.websphere.wim.exception.WIMConfigurationException:
  com.ibm.websphere.wim.exception.WIMConfigurationException:
  CWWIM5020E  Could not connect to the
  ldap://<<ldaphost>>:<<port>>
  repository using properties:
  [port=<<port>>],[ldapServerType=IDS],[bindDN=<<bindDN>>],[host=<
  <host>>],[certificateMapMode=exactdn],[sslConfiguration=null],[s
  ecurityDomainName=admin],[certificateFilter=null],[sslEnabled=fa
  lse],[connectTimeout=20],[bindPassword=****],[authentication=sim
  ple],[id=<<LDAP Repository Id>>], Exception occurred:
  java.net.ConnectException.
  
  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