PK85579: APPLICATION CLASS PATH RESOLUTION FAILS WHEN THE WORKING DIRECTORY NAME IS EMPTY.

Fixes are available

APAR status

Closed as program error.

Error description

When the directory returned by
'newFile(".").getCanonicalPath()' is an empty string, archive
class path resolution generates a value which is missing the
first character of the entry. This causes subsequent class
lookup to fail with an occurance of
java.lang.ClassNotFoundException.

WebSphere Application Server Version :: 6.1.0.19

Local fix

```
No local fix.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: ClassNotFoundException,                 *
*                      NoClassDefFoundError, or other errors   *
*                      while deploying or updating             *
*                      applications.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
While performing application deployment operations, either to
perform a new deployment, or to update an existing deployment,
the processing may produce one of several exceptions, leading
either to a failure to complete the operation, or leading to
an incorrect update of the application files.

The problem symptom is a combination of one or more of the
following:

1) A ClassNotFoundException or NoClassDefFoundError in the
SystemOut or trace log files.  For example:

[4/2/09 8:22:25:474 PDT] 0000000a SystemErr     R Caused by:
java.lang.ClassNotFoundException: com.ibm.websphere.ras.Manager
 at java.net.URLClassLoader.findClass(URLClassLoader.java:496)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:631)
 at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
 at
com.ibm.mq.jms.services.WASManager.<init>(WASManager.java:63)
 at
com.ibm.mq.jms.services.ConfigEnvironment.enableWebSphereTracing
AndLogging(ConfigEnvironment.java:645

[4/2/09 8:22:09:994 PDT] 0000000a CustomService W   WSVR0018W:
Unable to create CustomService, Introscope Custom Service
java.lang.NoClassDefFoundError:
com.wily.introscope.agent.service.IAgentService
 at java.lang.J9VMInternals.verifyImpl(Native Method)
 at java.lang.J9VMInternals.verify(J9VMInternals.java:68)
 at java.lang.J9VMInternals.initialize(J9VMInternals.java:129)
Caused by: java.lang.ClassNotFoundException:
com.wily.introscope.agent.service.IAgentService
 at java.net.URLClassLoader.findClass(URLClassLoader.java:496)
 at
com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.jav
a:132)

2) Other exceptions while processing non-class resources.  For
example:

[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R
java.lang.IllegalArgumentException: Unable to locate WSDL
definition for target namespace
http://v1x0.accountdetails.service.ts.wachovia.net//Binding
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.sca.internal.deployment.sib.SIBSoapJmsTask.installPar
t(SIBSoapJmsTask.java:135)
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.sca.internal.deployment.SCATaskBase.installArtifact(S
CATaskBase.java:192)
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.sca.internal.deployment.SCATaskBase.update(SCATaskBas
e.java:131)
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.sca.internal.deployment.sib.SIBSoapJmsTask.update(SIB
SoapJmsTask.java:278)
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.sca.internal.deployment.SCAUpdateTask.performTask(SCA
UpdateTask.java:242)
[9/26/08 12:11:30:937 CEST] 000000ab SystemErr     R  at
com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImp
l.java:262)

3) Other errors where incorrect application resources are
loaded.  This third case can occur, for example, when the
application contains several versions of particular resources.

Problem conclusion

This particular problem only occurs when the java working
directory is empty.  That is, when the the following java code
returns an empty string:

String workingDirectory = (new File(".")).getCanonicalPath();

Note that an empty working directory is an unusual, low
frequency, circumstance.

Because of the empty working directory, code which resolves
application and module classpath values generates an incorrect
classpath value.  As a result of the incorrect class path value,
resource lookup fails, leading to the problem.  (The classpath
value that is generated has the first character
omitted.)

The code has been corrected to properly generate the classpath.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.7 and 6.1.0.27.  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
PK85579
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-28
Closed date
2009-07-07
Last modified date
2009-07-07

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":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK85579: APPLICATION CLASS PATH RESOLUTION FAILS WHEN THE WORKING DIRECTORY NAME IS EMPTY.

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?