EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/4094f07967ca
                                     

EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/4094f07967ca
                                     

EVALUATION

DTrace probes instered into kernel on JVM intialization. It could cause a problem if multiple JVM's runs on the same machine. Delay probe installation by specific dtrace option.
                                     

SUGGESTED FIX

Luckily, this flag is supported by our build platforms:

diff --git a/make/solaris/makefiles/dtrace.make b/make/solaris/makefiles/dtrace.make
--- a/make/solaris/makefiles/dtrace.make
+++ b/make/solaris/makefiles/dtrace.make
@@ -165,7 +165,7 @@ CONDITIONALLY_UPDATE_JVMOFFS_TARGET = \
 $(DTRACE.o): $(DTRACE).d $(JVMOFFS).h $(JVMOFFS)Index.h $(DTraced_Files)
        @echo Compiling $(DTRACE).d
 
-       $(QUIETLY) $(DTRACE_PROG) $(DTRACE_OPTS) -C -I. -G -o $@ -s $(DTRACE).d \
+       $(QUIETLY) $(DTRACE_PROG) $(DTRACE_OPTS) -C -I. -G -xlazyload -o $@ -s $(DTRACE).d \
      $(DTraced_Files) ||\
   STATUS=$$?;\
        if [ x"$$STATUS" = x"1" -a \
                                     

SUGGESTED FIX

From 6815915: 

"To enable demand loading you should specify '-xlazyload' in the dtrace(1M) invocation
used to create the library (e.g. dtrace -G -xlazyload -s provider.d foo.o)."

It may be as simple as adding this flag in the hotspot build.  But - since building hotspot uses an older backported dtrace package when built on solaris 8 (jdk6's official build platform), that flag may not be available in that situation and we might have to do something more creative.