IC64877: HATS IOS INVOKED FROM SERVLET RETURN JAVA.LANG.ILLEGALARGUMENTEX CEPTION IF HTTP SESSION ISN'T ESTABLISHED FIRST.

Rational Host Access Transformation Services, Version 7.1.0.5
Rational Host Access Transformation Services, Version 7.1.0.6
Rational Host Access Transformation Services, Version 7.5.1.1
Rational Host Access Transformation Services, Version 7.5.1.2
Rational Host Access Transformation Services, version 7.5.1.3
Rational Host Access Transformation Services Fix Pack 4 (7.5.1.4) for 7.5.1
Rational Host Access Transformation Services Fix Pack 5 (7.5.1.5) for 7.5.1
Rational Host Access Transformation Services Fix Pack 6 (7.5.1.6) for 7.5.1

APAR status

• Closed as program error.

Error description

• Environment: HATS V7.5.
  Problem: If a customer uses a servlet to invoke a HATS
  Integration Object (IO), and they have not previously
  established an http session and thereby created an http session
  object, the invocation will fail, returning a
  java.lang.illegalArgumentException error message.  This type
  of invocation, without first establishing an http session,
  worked fine in HATS V6.0.  Also, in either case, invoking the
  IO from a .jsp page instead of a servelet works fine.
  

Local fix

• establish an http session just before invoking the IO.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  *                 HATS users running applications that call    *
  *                 Integration Objects from a servlet context.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: If an Integration Object was called     *
  *                      from a servlet context without          *
  *                      creating a HTTP session object first,   *
  *                      then                                    *
  *                      a java.lang.illegalArgumentException    *
  *                      error is generated.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  HATS code was ignoring an indicator that specified not to
  create an internal WebSession object if no HTTP session object
  exists.
  

Problem conclusion

• HATS code was modified to only create the internal WebSession
  object under the proper conditions.
  

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

• HATSCOMM
  

Fix information

• Fixed component name

  RATL HATS MULTI

• Fixed component ID

  5724U6700

Applicable component levels

• R710 PSY

     UP

• R750 PSY

     UP