PI14101: UNDER HEAVY LOAD JAX-WS WEB SERVICE OUTBOUND POOL MAY LEAK CONNECTIONS.

Fixes are available

APAR status

Closed as program error.

Error description

Under heavy load JAX-WS WebService outbound pool may run out of
connections, leaving connections in use forever. The following
exception indicates the symptom of the issue when connections
are not closed.

[3/12/14 6:05:48:027 MST] 0005334e AbstractAsync 3   Sync
operation timed out
[3/12/14 6:05:48:041 MST] 0005334e HttpServiceCo 3
IOException, closing the reads: java.net.SocketTimeoutException:
Async
operation timed out
[3/12/14 6:05:48:045 MST] 0005334e HttpServiceCo 3   Preparing
connection for closure
[3/12/14 6:05:48:045 MST] 0005334e HttpServiceCo 3   Throwing
exception back to caller.
[3/12/14 6:05:48:685 MST] 0005334e HttpOutRespon 3   Failed to
get next body buffer
[3/12/14 6:05:48:706 MST] 0005334e StAXOMBuilder W
org.apache.axiom.om.impl.builder.StAXOMBuilder parserNext
Attempt to access a parser that has thrown a parse exception
before; rethrowing the original exception.

Local fix

```
restart application server process.
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  JAX-WS web services.                        *
****************************************************************
* PROBLEM DESCRIPTION: When time out exception happens, the    *
*                      current in use connection could not     *
*                      be reset and released.                  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR.    *
****************************************************************
When reading the response body buffer, if a time out exception
happens, the current in use connection could not be reset and
released. It will always stay in "in used" state and can not
be reused. That will cause the connection resources in the
connection pool to run out of connections.

Problem conclusion

Fixed the problem by adding the reset method to reset and
release the connection for reuse if a time out exception
happens.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.33, 8.0.0.9 and 8.5.5.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
PI14101
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-19
Closed date
2014-05-02
Last modified date
2014-05-21

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

R700 PSY
UP
R800 PSY
UP
R850 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI14101: UNDER HEAVY LOAD JAX-WS WEB SERVICE OUTBOUND POOL MAY LEAK CONNECTIONS.

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?