PK99294: Applications that follow EJB 3.0 spec and use WebSphere Startup Beans, fail to start in a multiple Servant Region environment.

Fixes are available

APAR status

Closed as program error.

Error description

An application that follow the EJB 3.0 spec and contains
WebSphere Startup Beans will fail to start in a multiple
Servant Region configuration (where wlm_maximumSRCount > 1).

Here's an example of the error that can be seen in the second
Servant Region:

STUP0003E: NamingException looking up home for startup bean with
JNDI
name &lt;null&gt;, exception was java.lang.NullPointerException:
name
must not be null
STUP0004E: Cannot create startup bean named &lt;null&gt;,
exception was
java.lang.NullPointerException
STUP0006E: Exception calling startup bean named &lt;null&gt;,
exception
was java.lang.NullPointerException
WSVR0501E: Error creating component
com.ibm.ws.runtime.component.CompositionUnitMgrImpl@7c357c35
com.ibm.ws.exception.RuntimeWarning: Application Startup Bean
failed to
start.
.
Stack trace shows:
 001F 0X1E5FC22C  c=./bbgrjtr.cpp  at line:+886 ... BBOO0220E:
STUP0003E: NamingException looking up home for startup bean with
JNDI
 name &lt;null&gt;, exception was
java.lang.NullPointerException: name
must not be null
  at
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContex
t.java:4
21)
  at javax.naming.InitialContext.lookup(InitialContext.java:450)
  at
com.ibm.ws.startupservice.StartBeanInfo.getAppStartUpHome(StartB
eanInfo.
java:171)
...

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All z/OS users of IBM WebSphere Application *
*                  Server V7.0 using WebSphere Startup Beans   *
*                  in a multiple Servant Region(SR)            *
*                  environment                                 *
****************************************************************
* PROBLEM DESCRIPTION: Applications using WebSphere Startup    *
*                      Beans in a z/OS multiple SR             *
*                      environment will fail to start.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The EJBContainer did not place the name of the Remote Home of
Startup Beans in the internal metadata.   Therefore the
attempt to look up this home fails with an exception similar
to what is shown in the error description of this APAR.

Problem conclusion

The code that places the name of the WebSphere Startup Bean
Home in the internal metadata was changed to execute for every
SR, not just the SR designated to bind entries into the common
namespace.

APAR PK99294 is currently targeted for inclusion in
Service Level (Fix Pack) 7.0.0.9 of WebSphere Application
Server V7.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
PK99294
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-22
Closed date
2010-01-19
Last modified date
2010-04-12

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

PM12093

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK55133
UP10/03/26 P F003

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK99294: Applications that follow EJB 3.0 spec and use WebSphere Startup Beans, fail to start in a multiple Servant Region environment.

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

R700 PSY UK55133

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?