Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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
A string might contain backslash character(s). Like bindDN="cn=John\,Doe,ou=IBM". Here, a backslash character in front of a comma character is an escape character of the comma. On WebSphere Application Server full profile, the string is passed to the code as it is. Therefore, the code gets the value of bindDN as "cn=John\,Doe,ou=IBM". For Liberty profile, the backslash is dropped and the code gets "cn=John,Doe,ou=IBM" which is not valid. And if it is escaped again like "cn=John\\,Doe,ou=IBM", It gets an error as: probeid = processBundleConfig. bundle/version/pid=com.ibm.ws.security.registry.ldap/1.0.1.cl012 0131010- 2115/com.ibm.ws.security.registry.ldap.config-ldap. Message=Cardinality violation: "cn=Dohn\,Doe,ou=IBM" has 3 value(s) but must have between 1 and 1 value(s). Stack Dump = java.lang.IllegalArgumentException: Cardinality violation: "cn=Dohn\,Doe,ou=IBM" has 3 value(s) but must have between 1 and 1 value(s). at com.ibm.ws.config.internal.xml.ConfigEvaluator.processString(Con figEvalu ator.java:663) at com.ibm.ws.config.internal.xml.ConfigEvaluator.convertToSingleVa lue(Conf igEvaluator.java:373) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluateMetaType( ConfigEv aluator.java:292) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluateMetaTypeA ttribute (ConfigEvaluator.java:207) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluate(ConfigEv aluator. java:133) at com.ibm.ws.config.internal.xml.XMLBundleProcessor.updateConfigur ation(XM LBundleProcessor.java:1461) at com.ibm.ws.config.internal.xml.XMLBundleProcessor.processBundleC onfig(XM LBundleProcessor.java:409) at com.ibm.ws.config.internal.WSConfigActivator.bundleChanged(WSCon figActiv ator.java:317) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispa tchEvent (BundleContextImpl.java:847) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(E ventMana ger.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventS ynchrono us(ListenerQueue.java:148)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: The server fails when validating * * configuration elements containing * * escaped commas. * **************************************************************** * RECOMMENDATION: * **************************************************************** A string in the server configuration may contain backslash character(s), for example: "bindDN="cn=John\,Doe,ou=IBM". The server should interpret the backslash character in front of the comma character as an escape character of comma. Instead, the server unexpectedly removes the backslash and interprets the string as "cn=John,Doe,ou=IBM". Further, if the string is escaped again, like "cn=John\\,Doe,ou=IBM", the server misinterprets the string and fails with an exception like the following. probeid = processBundleConfig. bundle/version/pid=com.ibm.ws.security.registry.ldap/1.0.1.cl012 0131010- 2115/com.ibm.ws.security.registry.ldap.config-ldap. Message=Cardinality violation: "cn=Dohn\,Doe,ou=IBM" has 3 value(s) but must have between 1 and 1 value(s). Stack Dump = java.lang.IllegalArgumentException: Cardinality violation: "cn=Dohn\,Doe,ou=IBM" has 3 value(s) but must have between 1 and 1 value(s). at com.ibm.ws.config.internal.xml.ConfigEvaluator.processString(Con figEvalu ator.java:663) at com.ibm.ws.config.internal.xml.ConfigEvaluator.convertToSingleVa lue(Conf igEvaluator.java:373) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluateMetaType( ConfigEv aluator.java:292) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluateMetaTypeA ttribute (ConfigEvaluator.java:207) at com.ibm.ws.config.internal.xml.ConfigEvaluator.evaluate(ConfigEv aluator. java:133) at com.ibm.ws.config.internal.xml.XMLBundleProcessor.updateConfigur ation(XM LBundleProcessor.java:1461) at com.ibm.ws.config.internal.xml.XMLBundleProcessor.processBundleC onfig(XM LBundleProcessor.java:409) at com.ibm.ws.config.internal.WSConfigActivator.bundleChanged(WSCon figActiv ator.java:317) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispa tchEvent (BundleContextImpl.java:847) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(E ventMana ger.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventS ynchrono us(ListenerQueue.java:148)
Problem conclusion
Apply APAR PI15289 to update the application server to correctly interpret escaped commas within the server configuration. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3. 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 number
PI15289
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-04
Closed date
2014-05-23
Last modified date
2014-05-23
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
Document Information
Modified date:
28 April 2022