PJ41307: CUSTOM ASP.NET APPLICATION USING JIGLUE HANGS

APAR status

• Closed as program error.

Error description

• An application running in IIS, using c#, calls into Jiglue which
  then calls into the eProcess java APIs.
  The application could then end up hanging in the VWIDMDebug
  class constructor.
  The symptom seen by the end users is that, because the
  application has locked up, a web page does not load.
  
  If a debug diagnostics dump is taken at the time of the hang,
  and then jextract is used on that dump, you will see
  VWIDMDebug.<clinit> and "VWIDMDebug.<init>" in the java call
  stack:
  
  Java Stack Frames:
  ip=0x1990B2A5/sp=0x1A6F58E8:
  filenet.vw.ntutil.VWNTUTIL_DLL.initLibrary(VWNTUTIL_DLL.java:14)
  ip=0x197AF964/sp=0x1A6F58F4:
  filenet.vw.ntutil.RegKey.<clinit>(RegKey.java:12)
  ip=0x00000003/sp=0x1A6F5920:
  java.lang.J9VMInternals.initializeImpl()
  ip=0x10DC068B/sp=0x1A6F5964:
  java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
  ip=0x19787468/sp=0x1A6F599C:
  filenet.vw.idm.panagon.api.VWIDMDebug.<init>(VWIDMDebug.java:42)
  
  ip=0x197878F4/sp=0x1A6F59AC:
  filenet.vw.idm.panagon.api.VWIDMDebug.<clinit>(VWIDMDebug.java:3
  4)
  ip=0x00000003/sp=0x1A6F59D8:
  java.lang.J9VMInternals.initializeImpl()
  ip=0x10DC068B/sp=0x1A6F5A1C:
  java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
  ip=0x1990C2B6/sp=0x1A6F5A5C:
  filenet.vw.ntutil.trace.println(trace.java:23)
  ip=0x1990BCC5/sp=0x1A6F5A70:
  filenet.vw.ntutil.security.base.NativeSSPIPackage.init(NativeSSP
  IPackage.java:34)
  ip=0x1990A484/sp=0x1A6F5A90:
  filenet.vw.ntutil.security.NTSecurity.getCurrentThreadToken(NTSe
  curity.java:118)
  ip=0x10DC3A97/sp=0x1A6F5AD4:
  sun.reflect.NativeMethodAccessorImpl.invoke0()
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of  jiglue in eProcess-5.2.0-1014/-1016                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Custom application using jiglue hangs. An application        *
  * running in IIS, using c#, calls into Jiglue which            *
  * then calls into the eProcess java APIs.                      *
  * The application could then end up hanging in the VWIDMDebug  *
  * class constructor.                                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The eProcess release described in this APAR, eProcess-5.2.0, *
  * is obsolete and the release is unsupported. Upgrade to any   *
  * current supported release                                    *
  ****************************************************************
  

Problem conclusion

• Resolved by fixing a deadlock in the jiglue code and providing
  test fix eProcess-5.2.0-1015 to the customer.
  

Temporary fix

• eProcess-5.2.0-1015
  

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

  EPROCESS SERVIC

• Fixed component ID

  5724R8700

Applicable component levels

• R520 PSY

     UP