PK92424: RUNTIMEEXCEPTION BY INVALID CALL TO WSBYTEBUFFER

Fixes are available

APAR status

Closed as program error.

Error description

The application server will see the Exception below appear.
After that errors related to outbound transactions,  which could
lead to corba rollback minor code may appear repeatedly, even if
the "invalid call to WsByteBuffer"  does not appear again.
.
 java.lang.RuntimeException: Invalid call to WsByteBuffer
method.  Buffer has already been released.  WsByteBuffer: ID: 57
 Buffer: java.nio.DirectByteBuffer&#65517;pos=0 lim=424 cap=1024&#65529;
at com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.checkValidity
at com.ibm.ws.buffermgmt.impl.WsByteBufferImpl.release
at com.ibm.ws.tcp.channel.impl.ZAioTCPReadRequestContextImpl.
                destroy(ZAioTCPReadRequestContextImpl.java:114)
at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.
                       destroyCommon(ZAioTCPConnLink.java:1028)
at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.
                              destroy(ZAioTCPConnLink.java:992)
at com.ibm.wsspi.channel.base.OutboundConnectorLink.close
at com.ibm.wsspi.channel.base.OutboundProtocolLink.close
at com.ibm.ws390.channel.ziop.ZIOPConnectionContext.
                closeConnection(ZIOPConnectionContext.java:204)
at com.ibm.ws390.ziop.ZIOPChannelBridge.sendOutboundRequest
at com.ibm.ws390.orb.ClientDelegate.createRequestCFW
at com.ibm.ws390.orb.ClientDelegate.createRequest
at com.ibm.ws390.orb.ClientDelegate.request
at org.omg.CORBA.portable.ObjectImpl._request
at org.omg.CosTransactions._CoordinatorStub.register_resource
                                    (_CoordinatorStub.java:436)
at com.ibm.ws390.tx.TransactionCoordinatorImpl$1.run
                         (TransactionCoordinatorImpl.java:1067)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs
                                 (ContextManagerImpl.java:4388)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem
                                 (ContextManagerImpl.java:4566)
at com.ibm.ws.security.auth.ContextManagerImpl.
           runAsSystemOrSpecified(ContextManagerImpl.java:4642)
at com.ibm.ws.security.core.SecurityContext.
               runAsSystemOrSpecified(SecurityContext.java:274)
at com.ibm.ws.tx.util.WASTMHelper$2.run(WASTMHelper.java:85)
at com.ibm.ws.security.util.AccessController.
                        doPrivileged(AccessController.java:118)
at com.ibm.ws.tx.util.WASTMHelper.runAsSystemOrSpecified
                                          (WASTMHelper.java:80)
at com.ibm.tx.util.TMHelper.runAsSystemOrSpecified
                                             (TMHelper.java:39)
at com.ibm.ws390.tx.TransactionCoordinatorImpl.
     registerWithSuperior(TransactionCoordinatorImpl.java:1071)
at comm.ibm.ws390.tx.ControllerTransactionManagerImpl.
     receive_request(ControllerTransactionManagerImpl.java:642)
at com.ibm.ws390.tx.ControllerTransactionManagerSet.
      receive_request(ControllerTransactionManagerSet.java:263)
at com.ibm.ws390.ziop.ZIOPMessagePlugin.
         processInboundProxyFilters(ZIOPMessagePlugin.java:416)
at com.ibm.ws390.ziop.ZIOPChannelBridge.
                      filterInbound(ZIOPChannelBridge.java:447)
at com.ibm.ws390.ziop.ZIOPCPPUtilities.process_inbound_request
at com.ibm.ws390.channel.ziop.ZIOPInboundConnLink.
             routeIncomingMessage(ZIOPInboundConnLink.java:218)
at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.
               readComplete(ZIOPInboundMessageHandler.java:290)
at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler.
                   complete(ZIOPInboundMessageHandler.java:226)
at com.ibm.ws.tcp.channel.impl.ZAioTCPReadRequestContextImpl.
          readCompleted(ZAioTCPReadRequestContextImpl.java:680)
at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.readCompleted
at com.ibm.ws.tcp.channel.impl.ZAioTCPChannel.readCompleted

Local fix

A recycle of the Server should set everything back to Good.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: An outbound TCP/IP connection from      *
*                      WebSphere Application Server for z/OS   *
*                      fails repeatedly after improperly       *
*                      cleaning up from an initial exception,  *
*                      potentially resulting in repeated       *
*                      transaction rollbacks.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an outbound TCP/IP connection from WebSphere Application
Server receives an error, it is normally cleaned up and not
reused.  However, in some rare cases an error that occurs
during cleanup of the connection can cause the connection to
be reused, at which point it will receive continual failures.
The nature of the continual failures can vary and may include
transaction rollbacks.  The initial error that occurred during
connection cleanup can generally be spotted in the Controller
joblog and will include the following stack elements:

...
...
at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.destroyCommon
at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.destroy
at com.ibm.wsspi.channel.base.OutboundConnectorLink.close
at com.ibm.wsspi.channel.base.OutboundProtocolLink.close
at com.ibm.ws390.channel.ziop.ZIOPConnectionContext.
  closeConnection
...
...

After spotting an exception with the above stack elements in
the Controller joblog, some outbound connections may continue
to fail until a restart of the server is issued.

In addition, this APAR address another connection error
handling issue.  This error can be spotted by the existence
of the following FFDC log:

java.io.IOException: Error occurred during communications
  processing. EDC5000I No error occurred. (errno2=0xC2450032):
  RV=0, RC=0, RS=
    at com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities.
      giop_exact_read
    at com.ibm.ws.tcp.channel.impl.
      ZAioTCPReadRequestContextImpl.readCommon
    at com.ibm.ws.tcp.channel.impl.
      ZAioTCPReadRequestContextImpl.read

The above error will cause a single request to fail but not
cause additional issues.

Problem conclusion

Connection cleanup code was modified to catch additional
exceptions, at which point the connection will continue to be
cleaned up and not reused.  In addition, additional processing
was added to wrap the IOException from giop_exact_read into a
parent exception that is already being handled properly.

APAR PK92424 is currently targeted for inclusion in
Service Level (Fix Pack) 7.0.0.7 of WebSphere
Application Server version 7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK92424
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
2009-07-27
Closed date
2009-08-11
Last modified date
2009-12-02

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 UK51554
UP09/11/10 P F911

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK92424: RUNTIMEEXCEPTION BY INVALID CALL TO WSBYTEBUFFER

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 UK51554

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

Share your feedback

Need support?