Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Product Version: WebSphere Application Server V7.0 Operating System: Windows Problem title wsadmin.bat is unable to handle multiple spaces in Path character when defining the shared library path. . Problem description We have to define a shared library for our j2ee application. When the shared library is installed in a directory with a single space, it works fine.. Example : c:\Program Files\IBM\tivoli\lib it works fine When we try to define the library with 2 spaces the configuration fails. Example c:\Program Files\JDBC Drivers We have tried "c:/Program Files/JDBC Drivers" "C:/Program Files/JDBC Drivers/" The libraries.xml does not have proper information. Our python scripts contains the following def setSharedLibrary(nodeName, serverName, sharedLibDir, appName, cellName): global AdminConfig print 'setSharedLibrary:nodeName ' + nodeName n1 = AdminConfig.getid("/Cell:" + cellName + "/Node:"+nodeName+"/"); print 'setSharedLibrary:sharedLibDir ' + sharedLibDir library = AdminConfig.create('Library', n1, [['name', 'impactSharedLibrary'], 'classPath',sharedLibDir]]); print 'setSharedLibrary:appName ' + appName deployment = AdminConfig.getid("/Deployment:" + appName); appDeploy = AdminConfig.showAttribute(deployment, 'deployedObject'); classLoad1 = AdminConfig.showAttribute(appDeploy, 'classloader'); AdminConfig.create('LibraryRef',classLoad1, [['libraryName','impactSharedLibrary']]); AdminConfig.save(); print 'setSharedLibrary successful' return sharedLibDir = sys.argv[2] sharedLibDirEsc = '\"' + sharedLibDir + '\"' setSharedLibrary(nodeName, serverName, sharedLibDirEsc, appName, cellName)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server versions 7 and 8 * **************************************************************** * PROBLEM DESCRIPTION: Unable to use wsadmin to create shared * * libary when library classpath * * contains multiple spaces * **************************************************************** * RECOMMENDATION: * **************************************************************** The wsadmin tool is unable to handle multiple spaces in the classpath when creating the shared libary such as "C:/Program Files/JDBC Driver/test.jar"
Problem conclusion
It is a bug in wsadmin code when creating a shared library and the libary classpath contains multiple spaces in the path string such as "C:/Program Files/JDBC Driver/test.jar". The path would be broken into separate paths by the spaces. The correct syntaxes to define a shared libary classpath containing multiple spaces are: Using Jacl: Enclose with additional {} or quotes: $AdminConfig create Library $node {{name test1} {classPath {"C:/Program Files/JDBC Driver/test.jar"}}} or $AdminConfig create Library $node {{name test2} {classPath "'C:/Program Files/JDBC Driver/test.jar'"}} Using Jython: Enclose with additional [] or quotes: AdminConfig.create('Library', node, [['name','test2'],['classPath',['C:/Program Files/JDBC Driver/test.jar']]]) or AdminConfig.create('Library', node, [['name','test2'],['classPath',"'C:/Program Files/JDBC Driver/test.jar'"]]) The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.21 and 8.0.0.2. 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
PM38888
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-11
Closed date
2011-08-12
Last modified date
2011-11-02
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021