PQ43361: GETACTIVEJAVAVMS DOES NOT RETURN AN ACCURATE NUMBER

APAR status

• Closed as duplicate of another APAR.

Error description

• JNI_GetCreatedJavaVMs can return an invalid number.
  This is the fix for 1.3.0. See OW47041 for 1.1.8.
  In particular, if JVMs are loaded in the same
  process from different dlls this can cause problems.
  The fix was to
  JNI_GetCreatedJavaVMs to check for the existence of a JVM
  loaded previously from another dll.
  --
  CMVC defect SOV, 26611.
  Track integrated after 130-20010522
  --
  Note : The responder for PQ44234 indicates this is
  fixed in cumulative PTF3 (UQ49441), but this isn't
  the case. Please install cumulative PTF SR9 for
  relief.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• If two different JVM dll's are loaded, the second one has no
  way of knowing that the first is present. This caused problems
  with Component Broker because threads from one JVM ended up
  talking to the other. The solution to this is to change
  JNI_GetCreatedJavaVMs to check for the existence of a JVM
  loaded previously from another dll.
  This APAR is a duplicate of PQ50780
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels