IJ25574: HTTP REQUESTS ARE REJECTED BY THE HUB IN ERROR

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 9 (6.3.0.7-TIV-ITM-SP0009)

APAR status

• Closed as program error.

Error description

• Symptom:
  
   HTTP requests are rejected by the Hub in error when
  the URI in the POST request includes the correct HTTP port but
  another ITM application running on the same server was started
  before the Hub.
  
  
  
  Description:
  
   The first ITM application to
  start running on a server and that listens for HTTP traffic
  will own the well-known port, (which defaults to 1920).
  
   The
  next ITM application that is started and that also listens for
  HTTP traffic will do so using the next available port.
  
   So if
  the Hub is started second, it will be using a port for HTTP
  that is different to the well-known port.
  
  
  
   When the Hub
  validates a URI in a POST request, it does so using its
  temporary, assigned port rather than the well-known port.
  
  
  Therefore, even though the URI specifies the correct well-known
  port, the request is deemed invalid and rejected.
  
  
  
  
  Solution:
  
   The code validates the port in the URI against
  the well-known port instead of using the temporary port.
  

Local fix

• Workaround:
  
   Ensure that that Hub is started first on any
  server on which other ITM applications run if HTTP POST
  requests are expected that contain URIs that include the host
  and port number in addition to the path.
  

Problem summary

• The first ITM application to start running on a server and that
  listens for HTTP traffic will own the well-known port, (which
  defaults to 1920).  It listens to the port on its chosen
  interface address as well as on the loopback address.
  
  The next ITM application that is started on the same server
  and that is configured to use a different interface also uses
  the well-known port to listen for HTTP traffic on that
  interface.  However, because the first application is already
  listening on the well-known port on the loopback address, the
  second application will listen for HTTP traffic on the next
  available port via the loopback address.
  
   When the Hub receives a request to the well-known port on its
  own interface, because of the contention for the well-known port
  on the loopback address, it incorrectly validates the port in
  the request to the temporary loopback address port that is it
  using.
  
  Therefore, even though the URI specifies the correct well-known
  port, the request is deemed invalid and rejected.
  
  
  HTTP requests are rejected by the Hub in error when the URI in
  the POST request includes the correct HTTP port but another ITM
  application running on the same server was started before the
  Hub.
  

Problem conclusion

• The code validates the port in the URI against the well-known
  port instead of using the temporary port.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0009
  

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:

  OA59987

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels