PM24579: CREATING A NEW SHARED LIBRARY RESULTING IN SOME GARBAGE CHARACTERS IN THE CLASSPATH VALUE OF LIBRARY.XML FILE.

Fixes are available

APAR status

Closed as program error.

Error description

Problem : Creating a shared library using wsadmin scriping is
appending some garbage characters at the end of classpath value
in library.xml file when the specified classpath ends with
'\n' after upgrading to V6.1.0.31 from V6.1.0.27.

Sample commands:

from java.lang import String
from os.path import *

serv = AdminConfig.getid('/Cell:cell_name/Node:node_name/')
print serv
classpathValues = '${SHARED-LIBS}' + os.sep + 'TEST_FOLDER' +
os.sep + 'TEST_SUB_FOLDER' + os.sep + '\n'
classpath = [String(classpathValues)]
AdminConfig.create('Library', serv, [['name', 'MAL_TEST_LIB'],
['classPath', classpath ]])
AdminConfig.save()

Results:
========
At V6.1.0.31/33:
<libraries:Library xmi:id="Library_1286188199111"
name="MAL_TEST_LIB">
<classPath>${SHARED-LIBS}/TEST_FOLDER/TEST_SUB_FOLDER/&#xA;
</classPath>
</libraries:Library>


Tested same script on 6.1.0.27 and did not get the encoding in
libraries.xml
<libraries:Library xmi:id="Library_1286187974483"
name="MAL_TEST_LIB">

<classPath>${SHARED-LIBS}/TEST_FOLDER/TEST_SUB_FOLDER/</classPat
h>
</libraries:Library>

Local fix

```
No work-around.
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7 users of wsadmin scripting in jython     *
****************************************************************
* PROBLEM DESCRIPTION: Garbage characters appear at the end    *
*                      of the classpath in Library.xml for a   *
*                      shared library creation using           *
*                      wsadmin scripting.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The wsadmin jython parser does not trim the ending '\n'
character. This leads to the garbage characters showing at the
end of the classpath value in the library.xml file for a
shared library created with a specified classpath that ends
with '\n'.

Problem conclusion

We now trim the ending '\n' of the classpath value in the
wsadmin jython parser implementation to eliminate the ending
garbage characters generation.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.15.  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
PM24579
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-14
Closed date
2010-10-29
Last modified date
2010-10-29

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM24579: CREATING A NEW SHARED LIBRARY RESULTING IN SOME GARBAGE CHARACTERS IN THE CLASSPATH VALUE OF LIBRARY.XML FILE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?