PK73716: APPLICATIONS MAY PROCESS INBOUND JCA WORK BEFORE SERVER STARTUP IS COMPLETE

Fixes are available

APAR status

Closed as program error.

Error description

When individual applications start, any inbound J2EE Connector
Architecture (JCA) work can be immediately processed by the
server even if dependent servers or applications have not yet
started. A common symptom of this behavior is that a
NameNotFoundException occurs due to the fact that a dependent
application has not yet started.

Local fix

```
NA
```

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Process Server users.             *
****************************************************************
* PROBLEM DESCRIPTION: Service Connector Architecture (SCA)    *
*                      applications begin executing inbound    *
*                      work before the server is started.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When individual Service Connector Architecture applications
start, inbound work may start executing on the server before
dependent applications and servers are started and ready
to process work.  A common symptom of this behavior is a
NameNotFoundException that occurs whenever a dependent
application has not yet started.

Problem conclusion

APAR PK73716 delays the server from executing inbound work
until sufficient resources are available.  In particular, the
server does not activate message endpoints until all
applications are started.

The fix for this APAR is currently targeted for inclusion in
WebSphere Process Server fixpacks 6.0.2.6 and 6.1.2.2; and
WebSphere Application Server fixpacks 6.0.2.33, 6.1.0.23 and
7.0.0.3. 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
PK73716
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-13
Closed date
2008-11-11
Last modified date
2008-11-18

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

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

Document Information

Modified date:
28 December 2021

Tips

PK73716: APPLICATIONS MAY PROCESS INBOUND JCA WORK BEFORE SERVER STARTUP IS COMPLETE

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?