PM22226: FILENOTFOUNDEXCEPTION WHEN COM.IBM.CONFIG.ECLIPSE.WTP=FINER TRACING IS ENABLED DURING EJB 3.0 DEPLOYMENT

Fixes are available

APAR status

Closed as program error.

Error description

Enabling the trace "com.ibm.config.eclipse.wtp=finer"
causes a FileNotFoundException when installing an EJB 3.0
jar file which has no deployment descriptor
(META-INF/ejb-jar.xml), with
exception text
"java.io.FileNotFoundException: IWAE0065E Absolute path
unknown",
and occuring from
org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.
TempZipFileLoadStrategyImpl.getAbsolutePath.
A DeploymentDescriptorLoadException (which wraps the
FileNotFoundException) also occurs, with the text:
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.
DeploymentDescriptorLoadException: META-INF/ejb-jar.xml".

Local fix

Disable trace and the problem should not occur.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server 7.0 (all versions up to but not      *
*                  including 7.0.0.19) and 8.0.0.0.            *
****************************************************************
* PROBLEM DESCRIPTION: FileNotFoundException when enabling     *
*                      com.ibm.config.eclipse.wtp=FINER.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Enabling the trace "com.ibm.config.eclipse.wtp=FINER"
can cause a FileNotFoundException when installing an EJB 3.0
(or higher) jar file which has no deployment descriptor
(META-INF/ejb-jar.xml).  For example:

java.io.FileNotFoundException: IWAE0065E Absolute path
unknown

The FileNotFoundException will be shown as wrapped
by a DeploymentDescriptorLoadException:

org.eclipse.jst.j2ee.commonarchivecore.internal.exception.
DeploymentDescriptorLoadException: META-INF/ejb-jar.xml

For this problem, the exception stack will show the class
"TempZipFileLoadStrategyImpl" and the method "getAbsolutePath":

org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.
TempZipFileLoadStrategyImpl.getAbsolutePath.

The exception only occurs when the specified trace is
enabled.  The exception is shown in server trace log files.

The exception occurs because trace attempts to display an
archive path value which is not always available.  When the
archive path value is not available, a FileNotFoundException
results.  That the archive path value is not available is not
a problem, and no exception should be displayed.

Problem conclusion

Trace code was updated to avoid displaying the
FileNotFoundException when the trace specification
"com.ibm.config.eclipse.wtp=FINER" is enabled.

APAR PM22226 is currently targeted for inclusion in
Service Level (Fix Pack) 7.1.0.19 of WebSphere
Application Server 7.0, and is currently targeted for
inclusion in Service Level (Fix Pack) 8.0.0.1 of WebSphere
Application Server 8.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM22226
Reported component name
WAS EJB3 FEATUR
Reported component ID
5655I3551
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / CST
Submitted date
2010-09-09
Closed date
2011-06-23
Last modified date
2011-10-11

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM24456 PM44908

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R610 PSY
UP

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

Document Information

Modified date:
25 October 2021

Tips

PM22226: FILENOTFOUNDEXCEPTION WHEN COM.IBM.CONFIG.ECLIPSE.WTP=FINER TRACING IS ENABLED DURING EJB 3.0 DEPLOYMENT

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

R610 PSY

Document Information

Share your feedback

Need support?