IBM Support

PI06031: JAVA.LANG.RUNTIMEEXCEPTION: INVALID CALL TO WSBYTEBUFFER METHOD. BUFFER HAS ALREADY BEEN RELEASED.

Fixes are available

7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Exception reported with WebSphere z/OS Fixpack 7.0.0.27
    
    
    Exception in thread "ChannelFramework Threadpool : 0"
    java.lang.RuntimeException: Invalid call to WsByteBuffer method.
      Buffer has already been released.
     WsByteBuffer: ID: 1
     Buffer: java.nio.DirectByteBuffer[pos=0 lim=50 cap=8192]
      at
    com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.checkValidity(WsByte
    BufferImpl.java:2109)
      at
    com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.release(WsByteBuffer
    Impl.java:1959)
      at
    com.ibm.wsspi.buffermgmt.WsByteBufferUtils.releaseBufferArray(Ws
    ByteBufferUtils.java:262)
      at
    com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.releaseBuff
    ers(ZIOPInboundMessageHandler.java:675)
      at
    com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.error(ZIOPI
    nboundMessageHandler.java:244)
      at
    com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.readComplet
    e(ZIOPInboundMessageHandler.java:310)
      at
    com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.readFirstMe
    ssage(ZIOPInboundMessageHandler.java:124)
      at
    com.ibm.ws390.channel.ziop.ZIOPInboundConnLink.ready(ZIOPInbound
    ConnLink.java:148)
    at
    com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sen
    dToDiscriminators(NewConnectionInitialReadCallback.java:214)
      at
    com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.com
    plete(NewConnectionInitialReadCallback.java:113)
      at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(Wor
    kQueueManager.java:557)
      at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueue
    Manager.java:607)
      at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueue
    Manager.java:984)
      at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueu
    eManager.java:1069)
      at
    com.ibm.wsspi.runtime.ThreadPoolRepositoryManager$DefaultThreadP
    ool$Worker.run(ThreadPoolRepositoryManager.java:693)
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users of WebSphere Application Server   *
    *                      for z/OS may see a "RuntimeException:   *
    *                      Invalid call to WsByteBuffer method.    *
    *                      Buffer has already been released" in    *
    *                      their joblog.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following exception may be seen in the application server
    joblog,
    Exception in thread "ChannelFramework Threadpool : 0"
    java.lang.RuntimeException: Invalid call to
    WsByteBuffer method. Buffer has already been released
    WsByteBuffer: ID: 1
    Buffer: java.nio.DirectByteBuffer[pos=0 lim=50 cap=8192]
    at com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.checkValidity
    (WsByteBufferImpl.java:2109)
    at com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.release
    (WsByteBufferImpl.java:1959)
    at
    com.ibm.wsspi.buffermgmt.WsByteBufferUtils.releaseBufferArray
    (WsByteBufferUtils.java:262)
    at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.release
    Buffers(ZIOPInboundMessageHandler.java:678)
    at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.error
    (ZIOPInboundMessageHandler.java:245)
    at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.
    readComplete(ZIOPInboundMessageHandler.java:311)
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI06031

  • 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

    2013-11-12

  • Closed date

    2014-04-28

  • Last modified date

    2015-10-06

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI18561

       UP14/06/21 P F406

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

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PI06031

Modified date: 06 October 2015