|
Oh, sorry. I should have included that I was specifying the
-Xbootclasspath/a option. My current conf file includes: <jvm-arg>-Xbootclasspath/a:/home/afritz/jprofiler5/bin/agent.jar</jvm-arg> <jvm-arg>-agentlib:jprofilerti=port=31758</jvm-arg> <!--this is copied from a command launched via jprofiler directly that profiles--> I've also tried (among many variations): <jvm-arg>-Xbootclasspath/a:agent.jar</jvm-arg> <jvm-arg>-agentlib:jprofilerti=port=31758</jvm-arg> <!--this is copied from a command launched via jprofiler directly that profiles--> with agent.jar in the working directory. Regardless, I still get a "Could not find agent library on the library path or in the local directory: jprofilerti". So, sounds like I'm doing what I should with the JVM args. The command that the resin.jar file tries to launch dies quicker than I can see what it actually tried to run (via ps) so I can't tell if maybe some arg is being dropped. Running java -jar lib/resin.jar results in the watchdog starting and then a sub process being spawned to run the actual server. The jvm-arg specified in the conf file get passed through untouched, but if the command later includes a -Xbootclasspath:... then my change will get squashed. At this point I am assuming that is what is happening. Andrew Rob Lockstone wrote: Type java -X from the command line: |
_______________________________________________ resin-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/resin-interest
