IV81120: 500 ERROR AFTER ENABLING SYSTEM PROPERTY MXE.SYSTEM. USINGLOADBALANCER

APAR status

• Closed as program error.

Error description

• We recently moved to a clustered IIS server farm and saw that
  in the
  MAXSESSION and LOGINTRACKING tables the client IP address was
  always
  storing the internal IP address of our IIS server. After
  reading about
  the APAR (
  http://www-01.ibm.com/support/docview.wss?uid=swg1IV48747),
  
  we tried to turn on the system property that was added
  (mxe.system.
  usingLoadBalancer) which checks to see if there is an
  X-Forwarded-For
  header and if so, use that IP address in the header, but it
  prevents
  any login with a java.lang.StringIndexOutOfBoundsException
  error.
  
  Reviewing the RequestManager class, it looks like it was
  assumed that
  the X-Forwarded-For header would always have multiple IP
  addresses
  separated by a comma (which would happen if the request is
  routed
  through multiple proxies), but in our situation it's just the
  client's
  IP address (without any additional IP addresses separated by a
  comma).
  When it tries to get a substring from position 0 to the comma
  it gets
  the out of bounds exception.
  
  Some examples of both (going through no additional proxies and
  going
  through multiple proxies) can be found on Amazon's AWS website
  here:
  
  http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Developer
  Guide/x-forwarded-headers.html
  
  
  System Information:
  
  App Server IBM WebSphere Application Server 8.5.5.7
  Version
  Tivoli's process automation engine 7.6.0.1 Build 20150611-1135
  DB Build
  V7601-65
  IBM TPAE Integration Framework 7.6.0.1 Build 20150610-1800 DB
  Build
  V7601-07
  IBM Maximo Asset Management 7.6.0.1 Build 20150611-1135 DB
  Build V7601-
  01
  Server OS Windows Server 2012 R2 6.3
  Server DB Microsoft SQL Server 11.0 (11.00.5058)
  (c) Copyright IBM Corp. 2015
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Maximo Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 500 error after enabling system property                     *
  * mxe.system.usingLoadBalancer.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to latest release                                    *
  ****************************************************************
  We recently moved to a clustered IIS server farm and saw that in
  the MAXSESSION and LOGINTRACKING tables the client IP address
  was always storing the internal IP address of our IIS server.
  After reading about the APAR
  (http://www-01.ibm.com/support/docview.wss?uid=swg1IV48747), we
  tried to turn on the system property that was added
  (mxe.system.usingLoadBalancer) which checks to see if there is
  an X-Forwarded-For header and if so, use that IP address in the
  header, but it prevents any login with a
  java.lang.StringIndexOutOfBoundsException error. Reviewing the
  RequestManager class, it looks like it was assumed that the
  X-Forwarded-For header would always have multiple IP addresses
  separated by a comma (which would happen if the request is
  routed through multiple proxies), but in our situation it's just
  the client's IP address (without any additional IP addresses
  separated by a comma). When it tries to get a substring from
  position 0 to the comma it gets the out of bounds exception.
  Some examples of both (going through no additional proxies and
  going through multiple proxies) can be found on Amazon's AWS
  website here:
  http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Developer
  Guide/x-forwarded-headers.html
  

Problem conclusion

• No error after enabling system property
  mxe.system.usingLoadBalancer.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Fix Pack Release 7.6.0.5 TPAE
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels

• R760 PSY

     UP