APAR status
Closed as program error.
Error description
User created a server side web services client. The application
throws a Nullpointer exception when they try to move the
service and invoke it with a handler. The following is an
example of the stack trace:
.
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
java.lang.NullPointerException
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.component.WSServerImpl.getClientEngineCon
fig(WSSe
rverImpl.java:426)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.axis.ws.configuration.ServerConfiguration
Factory.
getClientEngineConfig(ServerConfigurationFactory.java:108)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.engine.client.ClientEngine.<init>(ClientE
ngine.ja
va:109)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.engine.client.ClientEngineFactory.getEngi
ne(Clien
tEngineFactory.java:92)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.engine.client.Service.<init>(Service.java
:198)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
com.ibm.ws.webservices.engine.client.ServiceFactory.createServic
e(Servic
eFactory.java:273)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
mypack.NewThread.create(NewThread.java:40)
[2/24/04 17:27:03:443 GMT-06:00] 3dd19fb9 SystemErr R
at
mypack.NewThread.run(NewThread.java:47)
Local fix
As a workaround for this problem, the customer can create the
Service in the handler and then pass that to the NewThread
object for it to use. When the Handler gets initialized, it will
pass the newly created Service object to NewThread instance
before calling start(). Once inside NewThread, the service obje
ct can be used expected.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: NullPointerException a thrown from a *
* multi-threaded client *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a customer tries to create a multi-thread client based
on the JSR 101 API, which calls for the use of the
ServiceFactory, this client can fail with a Null Pointer
Exception. If the 101 client is running in an environment that
also has a JSR-109 deployment in it, then this client will fail.
Problem conclusion
Our web services engine did not correctly address this
situation and expected a certain level of deployment info
that does not exist when running in a JSR-101 scenario.
Temporary fix
ZE Fix Error
PQ90362 04/06/23
Although JSR109 doesn't recommend use of ServiceFactory from
within a J2EE environment, a possible way around this was
provided as a test fix.
Comments
APAR information |
APAR number |
PQ85842 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-10 |
Closed date |
2004-06-21 |
Last modified date |
2004-06-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
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 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|