APAR status
Closed as program error.
Error description
The WebSphere Extension MBean Provider classpath does not work.
Leigh Williamson of the WebSphere team helped us figure this out
and
told us to write a
WebSphere APAR.
Scenario:
The WCI Team has an Enterprise Application, which has a custom
MBean.
Our custom MBean has methods that return or recieve as
parameters
objects that are
defined by our Enterprise Application. In order for the MBean to
properly use our objects, we need
to add the jars which contain those objects to the server's
classpath.
So, we used the WAS Admin Console to configure an Extension
MBean
Provider and added the fully qualified
names of our two .jar files to the ClassPath property there.
(using a
colon as a seperator). Leigh Williamson is in Loop on this.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.x users who *
* use the WebSphere Extension MBean Provider *
* classpath. *
****************************************************************
* PROBLEM DESCRIPTION: The jar files defined in the WebSphere *
* Extension MBean Provider classpath are *
* not picked up by the runtime *
* classloader. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The MBeanExtension initializer did not add the extension mbean
provider classpath to the runtime classpath.
Problem conclusion
Changed the MBeanExtension initializer to add the extension
provider classpath to the runtime classloader so jar files
set in the extension provider classpath are available at
runtime.
Temporary fix
Test fixes now available on
PQ99999.
PQ82376_502_test.jar is for 5.0.2.x releases.
PQ82376_51_test.jar is for 5.1.0.x releases.
Comments
APAR information |
APAR number |
PQ82376 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-12-17 |
Closed date |
2004-02-19 |
Last modified date |
2004-02-19 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|