| WebLogic 8.1 startup hangs with TPTP 4.0 runpiAgent [message #28887] |
Mon, 29 August 2005 12:50  |
Eclipse User |
|
|
|
Originally posted by: rgavlin.xxxxx.com
After I modify the WebLogic 8.1 SP3 startup script to include the
-XrunpiAgent:server=standalone argument, the WebLogic startup process
hangs early-on in its lifecycle. I'm using TPTP 4.0 and am able to
successfully profile JUnit tests using TPTP 4.0. Any thoughts or
suggestions?
Ron Gavlin
|
|
|
| Re: WebLogic 8.1 startup hangs with TPTP 4.0 runpiAgent [message #30505 is a reply to message #28887] |
Thu, 08 September 2005 05:51  |
 Guru Nagarajan
Messages: 45
Registered: July 2009 |
Member |
|
|
Ron,
You can choose to launch the Java app with the JVM arg -XrunpiAgent in
three different modes, standalone, enabled or controlled:
-XrunpiAgent:server=[standalone | enabled | controlled]
standalone A stand-alone trace to a specified file based on the options and
filters given on the command line is generated, and trace file generated can
be imported in TPTP for analysis.
enabled: The application will start and run normally, but produces no trace
data until TPTP workbench attaches(via Profile>Attach - Java Process) to the
agent and start monitoring.
controlled: The application is blocked from running until workbench attach
and gives it instructions to continue. With this mode chosen, all the
startup data will be covered in the trace session.
Pls. try the profiling with "server=enabled" mode and let us know what you
see.
Thanks,,
Guru
"Ron Gavlin" <rgavlin@xxxxx.com> wrote in message
news:94b344848847ff490a37341818e42d6c$1@www.eclipse.org...
> After I modify the WebLogic 8.1 SP3 startup script to include
> the -XrunpiAgent:server=standalone argument, the WebLogic startup process
> hangs early-on in its lifecycle. I'm using TPTP 4.0 and am able to
> successfully profile JUnit tests using TPTP 4.0. Any thoughts or
> suggestions?
>
> Ron Gavlin
>
|
|
|
Powered by
FUDForum. Page generated in 0.03382 seconds
] 
Search
Help
Register
Login
Home
