IBM Support

PI70637: RUNTIMEEXCEPTION: INVALID CALL TO WSBYTEBUFFER OCCURS DURING SHUTDOWN

Subscribe

You can track all active APARs for this component.

 

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

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"CD0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2020