IT29122: NUMBER OF ACTIVE GROWS IN THE PERIMETER SERVER LOG WHEN THE HTTPSERVER REQUESTS HANG

APAR status

• Closed as program error.

Error description

• Error Description
  
  IBM Serling B2B Integrator versions 5020604, 5020604_1, 6000000,
  6000001 and 6000100
  can become unstable and the active connection count continues to
  grow in the perimeter.log.
  
  
  Netstats shows majority of connections from the HTTP server
  adapter are in the CLOSE_WAIT state indefinitely exhausting the
  perimeter connections. The CLOSE_WAIT indicates that the HTTP
  server adapter does not close the connections properly.
  
  The Perimeter.log logs show the below error message when the
  server can no longer accept new connections (inbound/outbound).
  
  [2019-05-09 08:36:22.319] ERROR Relay[local]: Max concurrent
  circuits reached: size is:4096
  [2019-05-09 08:36:22.319] ERROR Exception in
  AcceptServer.connected
  [2019-05-09 08:36:22.319] ERROR [1557401782319] System is out of
  resources
  [2019-05-09 08:36:22.319] ERRORDTL
  [1557401782319]com.sterlingcommerce.perimeter.muxrat.CircuitReso
  urcesException: System is out of resources
  at
  com.sterlingcommerce.perimeter.muxrat.relay.Relay.newCircuit(Rel
  ay.java:182)
  
  Symptoms:
  
  Experiencing timeouts.
  Netstat output shows a growing number of CLOSE_WAIT port state
  on the HTTP Server  adapter port.
  
  Eventually, IBM Serling B2B Integrator runs out of active
  connections and displays "System is out of resources" error.
  

Local fix

• Local Fix
  RTC 583432
  SB /SB
  Circumvention:
  Add the following to customer_overrides.properties and restart
  the IBM Sterling B2B Integrator to apply the changes.
   1. perimeter.physicalConnMgr.killStale_CLOSE_WAIT=true
   2. perimeter.physicalConnMgr.maxTimeToKillStaleConnections=120
   3. perimeter.physicalConnMgr.dumpConnectionList =yes
  
  Note: For the cleaner task to run and kill stale
  connections, either the perimeter logs should be set to ?ALL? or
  the set
  perimeter.physicalConnMgr.dumpConnectionList to yes.
  
  Since the perimeter logging can get extensive if set to "ALL",
  setting the property to yes in step 3 is advised.
  
  This cleans up the CLOSE_WAIT ports.
  You will experience timeouts in the front end.
  

Problem summary

• Users Affected:
  All
  
  Problem Description:
  If the http server requests hangs, the number of active
  connections
  grows in the perimeter server log.
  
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code fix is provided.
  
  Delivered In:
  5020604_2
  6000101
  6000002
  

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

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels