APAR status
Closed as program error.
Error description
[2/10/05 9:36:53:738 E7c3c84 BeanMetaData E CNTR0035E: EJB
container
caught java.lang.NoSuchFieldException at
java.lang.Class.getField0(Native Method) at
java.lang.Class.getField(Class.java:821) at
com.ibm.ejs.container.BeanMetaData.completeInitialization
This is the same issue as WSAS 4.0x APAR PQ58584 was created
for.
ERROR DESCRIPTION:
On some platforms, a problem has been found where a call to the
reflection api getField(name) results in a NoSuchFieldException
even though the field does exist. This may be an intermittent
problem which will be seen when installing an application with
an Entity Bean with Container Managed Peristence fields.
Local fix
none,
Cannot be recreated at will.
Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server on *
* platforms where Application Server contains *
* a SUN JDK, such as Solaris. *
****************************************************************
* PROBLEM DESCRIPTION: NoSuchFieldException is thrown when *
* starting an application. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This stack trace can be seen at server or application startup:
CNTR0035E: EJB container caught java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getField(Class.java:821)
at com.ibm.ejs.container.BeanMetaData.completeInitialization
(BeanMetaData.java:1134)
This problem was seen on 4.0.X and fixed in APAR PQ58584. We
did not integrate it into the 5.X code stream, because the fix
is a workaround for a SUN JDK bug, and results in a slight
perfomance impact.
Problem conclusion
There is some type of initialization or multi-threaded issue
in the JDK used on Solaris machines, such that the getField()
reflections api does not always work correctly.
To work around this, a change has been made in Application
Server to catch the exception and retry the reflection api
call to getField().
We hope that this bug in the JDK will be fixed in JDK 1.3,
which is included in version 5.1.X, so we are only putting this
workaround in the 5.0.2 code stream for now.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.11.
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 |
PK01520 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-22 |
Closed date |
2005-03-23 |
Last modified date |
2005-03-23 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSN |
UP |
R10A PSN |
UP |
R10H PSN |
UP |
R10I PSN |
UP |
R10P PSN |
UP |
R10S PSN |
UP |
R10W PSN |
UP |
|