IC86574: OUTSTANDINGREQUESTS PROPERTY CAN BECOME NEGATIVE

APAR status

• Closed as program error.

Error description

• If HTTP nodes have the timeout terminal wired then it is
  possible for timeouts to cause the outstandingRequests property
  on the associated URL registration on the HTTP or HTTPSConnector
  to become negative.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker who make use of the
  timeout terminal of the SOAPInput or HTTPInput nodes.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM SUMMARY:
  If HTTP nodes have the timeout terminal wired then it is
  possible for timeouts to cause the outstandingRequests
  property on the associated URL registration on the HTTP or
  HTTPSConnector
  to become negative.
  The output of mqsireportproperties on the HTTP(S)Connector
  will look something like:
  
  mqsireportproperties TESTV7BRK -e default -o HTTPConnector -r
  
  HTTPConnector
  uuid='HTTPConnector'
  userTraceLevel='none'
  traceLevel='none'
  userTraceFilter='none'
  traceFilter='none'
  port='7802'
  address=''
  allowTrace=''
  maxPostSize=''
  acceptCount=''
  bufferSize=''
  compressableMimeTypes=''
  compression=''
  connectionLinger=''
  connectionTimeout=''
  maxHttpHeaderSize=''
  maxKeepAliveRequests=''
  maxSpareThreads=''
  maxThreads=''
  minSpareThreads=''
  noCompressionUserAgents=''
  restrictedUserAgents=''
  socketBuffer=''
  tcpNoDelay=''
  explicitlySetPortNumber=''
  enableLookups=''
  enableMQListener=''
  shutdownDelay=''
  DefaultConnector
  port='7802'
  URLRegistration='/timeMeOut'
  nodeLabel='HTTP Input'
  outstandingRequests='-2'
  

Problem conclusion

• WebSphere Message Broker has been modified so that the
  outstandingRequests count behaves correctly when the timeout
  terminal of the SOAPInput or HTTPInput nodes is wired.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v7.0
  --------           --------------------
  Multiplatforms     7.0.0.6
  
  Platform           v8.0
  --------           --------------------
  Multiplatforms     8.0.0.3
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• 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

  WEB MESSAGE BRO

• Fixed component ID

  5724J0510

Applicable component levels

• R700 PSY

     UP