When the application comes up (a couple of minutes later) the 'listener' agent's connection goes down and the UI tells me that the agent maybe down or connection is closed. ADMU3000I: Server open for e-business process id is 27966 I can connect with the client (using port 10002, by my choice in extra JVM arguments requested). *** HINT ***: To get profiling results, connect to the application from the profiler UI ADMU0116I: Tool information is being logged in file /opt/WSProfiles/a/logs//startServer.log ADMU0128I: Starting tool with the a profile ADMU3100I: Reading configuration for server: ADMU3200I: Server launched. mixed mode, sharing Solaris 64 bit JVM) Profiler agent is listening on port 10002. Here's what happens: When I launch the server everything seems ok: /opt/WSProfiles/a/yjp-7.0.12/bin/solaris-sparc-64:/opt/WebSphere/AppServer/bin: Using JVMTI (1.5.0_11-b03 Sun Microsystems Inc. Hi all, I'm actually encountering some difficulties in profiling an application running on Websphere 6.1 (JDK 1.5) on a Solaris Sparc machine.
0 Comments
Leave a Reply. |