I've got a simple bug I'm having problems ironing out... probably the hot summer weather!
I've bought and activated Profiler, and now I cannot start WAS6 in RAD7. I thought I'd introduced the problem by trying to run Profiler before it was activated. This may still be the case. I was messing around trying to find ways that I may be able to profile a jar running in the server and this involved clicking on things that I didn't know what they did and then promptly forgetting all the things I'd been trying. You know, standard IT guy with unfamiliar software behaviour...
When I try to start WAS in RAD I get this in the console:
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
C:\IBMSDP\7.0\runtimes\base_v6/profiles/default\logs\server1 should
contain failure information.
And in the file native_sterr.log in C:\IBMSDP\7.0\runtimes\base_v6\profiles\default\logs\server1 I get this line:
The JVM option is invalid: -agentpath:C:\IBMSDP\7.0Shared\plugins\eclipse\plugins\com.instantiations.jvmti.agent.win32.x86_2.2.0.200907152126\agent.dll=mode=37,s=was.base.v6,port=2686,telemetryInterval=100,samplingInterval=100,mos=1024,tna=1000,jpp=C:\IBMSDP\7.0Shared\plugins\eclipse\plugins\com.instantiations.jvmti.agent_2.2.0.200907152126\agent.jar
Could not create the Java virtual machine.
I get this error starting WAS6 in a clean workspace too.
Profiler version is 2.2.0.200907152126.
I also have Analytix installed which is working well.
Has anyone got any ideas?