PM80400: WSADMIN MAY DISPLAY WRONG EXCEPTION WHEN TERMINATED BY AN UNCAUGHT NON-WSAS FAILURE

7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Exception handling not behaving as expected.
  
  Did test with customer provided script:
  Executing script like
  =====================
  try:
      AdminConfig.list('NonExistentType')
  except:
      print 'Handled wsadmin exception'
  print 'Raising another exception'
  x = 1/0
  
  resulting in:
  =============
  Handled wsadmin exception
  Raising another exception
  WASX7017E: Exception received while running file "ex.py";
  exception information:
  com.ibm.websphere.management.exception.
  InvalidConfigDataTypeException
  com.ibm.websphere.management.exception.
  InvalidConfigDataTypeException:
  ADMG0007E: The configuration data type NonExistentType is not
  valid.
   -----
  Expected behaviour would have been to get the real exception
  ZeroDivisionError: integer division or modulo
  triggered by
    x = 1/0
  instead of the InvalidConfigDataTypeException which should have
  been caught before.
  

Local fix

• None
   -
  Keywords:jython jacl  Misleading  wsadmin  script
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server wsadmin scripting                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: In some cases an exception surfaced     *
  *                      from a wsadmin script may not be        *
  *                      the actual exception raised.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a WebSphere Application Server built-in scripting object
  throws an exception which is caught and handled in the script,
  and later a non Application server exception is thrown and not
  caught, on exit wsadmin will erroneously report the first
  exception as the cause for exiting.
  

Problem conclusion

• The code was changed to report the actual thrown exception.
  The new behavior is only enabled when the following system
  property is set in the wsadmin JVM:
  
  com.ibm.ws.scripting.exceptionPropagation=thrown
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack s6.1.0.47, 7.0.0.29, 8.0.0.7 and the fix pack
  following 8.5.0.2. Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP