PI70637: RUNTIMEEXCEPTION: INVALID CALL TO WSBYTEBUFFER OCCURS DURING SHUTDOWN

Fixes are available

APAR status

Closed as program error.

Error description

Shutting down Liberty server which is configured with HTTP
and
HTTPS causes "java.lang.RuntimeException: Invalid call to
WsByteBuffer
method.  Buffer has already been released

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty                              *
****************************************************************
* PROBLEM DESCRIPTION: WsByteBufferImpl.release() called twice *
*                      during SSL Channel discrimination       *
*                      failure                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Problem Summary

If there is a failure when the SSL Channel is in the process of
discrimination to send data up to the next channel, one of the
WsByteBuffers might be released twice. If there is a double-
release on a buffer, a java.lang.RuntimeException will occur and
an FFDC will be generated.

The following is an example of the exception:

CHFW0031E:
sonIncomingTcpInputChain_SonIncomingTCPSubsystem_0_51008

com.ibm.wsspi.channel.framework.exception.ChannelException:
java.lang.Runtime

Exception: Invalid call to WsByteBuffer method. Buffer has
already been released.



The following is an example of the FFDC:

[10/3/16 9:39:16:034 GMT] 00000029 id=
com.ibm.ws.bytebuffer.internal.WsByteBufferImpl              3
release
com.ibm.ws.bytebuffer.internal.PooledWsByteBufferImpl@9c465b7f
java.lang.Throwable: stack trace
at
com.ibm.ws.bytebuffer.internal.WsByteBufferImpl.release(WsByteBu
fferImpl.java:1621)
at
com.ibm.wsspi.bytebuffer.WsByteBufferUtils.releaseBufferArray(Ws
ByteBufferUtils.java:332)
at
com.ibm.ws.channel.ssl.internal.SSLConnectionLink.determineNextC
hannel(SSLConnectionLink.java:1042)
...
[10/3/16 9:39:16:035 GMT] 00000029 id=
com.ibm.ws.bytebuffer.internal.WsByteBufferImpl              3
release
com.ibm.ws.bytebuffer.internal.PooledWsByteBufferImpl@9c465b7f
java.lang.Throwable: stack trace
at
com.ibm.ws.bytebuffer.internal.WsByteBufferImpl.release(WsByteBu
fferImpl.java:1621)
at
com.ibm.ws.channel.ssl.internal.SSLReadServiceContext.close(SSLR
eadServiceContext.java:1123)
at
com.ibm.ws.channel.ssl.internal.SSLConnectionLink.cleanup(SSLCon
nectionLink.java:219)
...

Problem conclusion

The SSL Channel was modified to correctly release the
WsByteBuffers.

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.4.  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
PI70637
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-13
Closed date
2016-10-17
Last modified date
2016-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
LIBERTY PROF -
Fixed component ID
5655W6514

Applicable component levels

RCD0 PSY
UP

[{"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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI70637: RUNTIMEEXCEPTION: INVALID CALL TO WSBYTEBUFFER OCCURS DURING SHUTDOWN

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

RCD0 PSY

Document Information

Share your feedback

Need support?