IJ38850: LONG DELAY IN ATTACH API

APAR status

• Closed as program error.

Error description

• Error Message: When using AttachAPI on multiple JVMs at same
  time there is an observed long delay or pause followed by
  InvocationTargetException even after applying the APAR fix
  IJ34905
  .
  Stack Trace: Caught exception
  java.lang.reflect.InvocationTargetException:
  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java)
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java)
  java.lang.reflect.Method.invoke(Method.java)
  com.ibm.mq.ipt.admin.IPTLocalAdminUtils$VirtualMachineProxy.atta
  ch(IPTLocalAdminUtils.java)
  com.ibm.mq.ipt.admin.IPTLocalAdminUtils.findLocalIPTNames(IPTLoc
  alAdminUtils.java)
  com.ibm.mq.ipt.admin.IPTAdmin.doLocalAdmin(IPTAdmin.java)
  com.ibm.mq.ipt.admin.IPTAdmin.main(IPTAdmin.java)
  .
  

Local fix

Problem summary

• The problem is caused when AttachAPI is used simultaneously on
  multiple JVM's
  

Problem conclusion

• The JVM has been updated to reduce the long delays by improving
  selfAttach and by adjusting timeouts
  .
  This APAR will be fixed in the following Java Releases:
   8 SR7 FP11 (8.0.7.11)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
   https://www.ibm.com/developerworks/java/jdk/
  

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

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels