Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Attaching to remote JVM to profile it from workbench fails
Attaching to remote JVM to profile it from workbench fails [message #111150] Mon, 03 September 2007 11:47 Go to next message
Eclipse UserFriend
Originally posted by: hichamm.orcsoftware.com

Hello,

Server Linux Opteron, using
agntctrl.linux_em64t-TPTP-4.4.1-200708280100.zip
1.TPTP_AC_HOME=/tmp/hichamm/
PATH contains /tmp/hichamm/bin
LD_LIBRARY_PATH contains
/tmp/hichamm/lib/:/tmp/hichamm/plugins/org.eclipse.tptp.java profiler/
JAVA_PROFILER_HOME=/tmp/hichamm/plugins/org.eclipse.tptp.jav aprofiler

2. I start ACStart.sh and run successfully SampleClient

3. I start an inhouse process, that loads the JVM1.6.0 .so for linux
x86-64,
with these jvm optioms:
-verbose
-agentlib:jdwp=transport=dt_socket,address=8456,server=y,sus pend=n
-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execd etails=true


4. from my WinXP32 eclipse europa 3.3.0 (june25 build), I go to Profiling
perspective: set serverhost, the port, test connection ok, in Agents, i
select the execution time analysis.
I click Profile, then eclipse shows Launching processname, connection to
JVMTI agent, and then
the process (with shared-in jvm) exits.
The only error the JVM reports to stdout/err is
[Error: Attach failed]

servicelog.log shows:
<CommonBaseEvent creationTime="2007-09-03T11:43:04.041278Z"
globalInstanceId="A6DBF3480000A1355A5C3D9B7501A70A" msg="Agent is locked"
severity="50" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3659" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:04.791237Z"
globalInstanceId="A6DBF348000C12BE7BB36F3A66FE5ED1" msg="Agent is locked"
severity="50" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3659" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:40.650510Z"
globalInstanceId="A6DBF36C0009ED0661B22C8F449B1D26" msg="Agent is locked"
severity="50" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3659" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:42.791749Z"
globalInstanceId="A6DBF36E000C14BD58084EB33666979F" msg="The requested
connection (119d) could not be found during sendMessage" severity="50"
version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="ConnectionManager.c,
line 534" instanceId="2" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Connection Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:42.792243Z"
globalInstanceId="A6DBF36E000C16AE3598E63B635F790B" msg="A
processExitedEvent was received for which we have no corresponding agent."
severity="30" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3006" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:42.792657Z"
globalInstanceId="A6DBF36E000C184D7E48542A6BBF2DDD" msg="A
processExitedEvent was received for which we have no corresponding agent."
severity="30" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3006" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:42.793092Z"
globalInstanceId="A6DBF36E000C1A011A8EC7BB3697E3ED" msg="A
processExitedEvent was received for which we have no corresponding agent."
severity="30" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3006" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>
<CommonBaseEvent creationTime="2007-09-03T11:43:42.793492Z"
globalInstanceId="A6DBF36E000C1B9132EA578933C23D71" msg="A
processExitedEvent was received for which we have no corresponding agent."
severity="30" version="1.0.1">
<sourceComponentId component="AgentController"
componentIdType="TPTPComponent" executionEnvironment="AgentManager.c, line
3006" instanceId="1" location="k2.orcsoftware.com" locationType="IPV4"
processId="15953" subComponent="Agent Manager" threadId="15953"
componentType="Eclipse_TPTP"/>
<situation categoryName="ReportSituation">
<situationType
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
</CommonBaseEvent>


a few errors appear there,

best regards,
Re: Attaching to remote JVM to profile it from workbench fails [message #112059 is a reply to message #111150] Sun, 09 September 2007 12:43 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf YaffeFriend
Messages: 333
Registered: July 2009
Senior Member
Hicham,

On the Linux machines please define/export the following global
environment variables before launching the Java process:

MARTINI_LOGGER_DIRECTORY=<an existing directory of your choice>
MARTINI_LOGGER_LOG_LEVEL=5

After the Java application crashes, please locate the generated log file
(MLog*.log) and post it here.

I suspect there might be a conflict between the JVMTI Profiler and the
-agentlib:jdwp argument (which loads another JVMTI agent). This is not a
supported configuration at the moment and may cause problems. I'll be
smarter after seeing the log file though.. :)

Thanks,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: Attaching to remote JVM to profile it from workbench fails [message #112223 is a reply to message #112059] Wed, 12 September 2007 07:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hichamm.orcsoftware.com

Your suspicion was correct.
Removing the debugger from the JVM let the eclipse attach correctly to the
JVM.
I managed to monitor the JVM from eclipse, my filter was properly defined,
and i didn't get any info into the workbench alors.
It said in the bottom "Time elapsed" 200seconds

One thing though, on the server box,.../config/servicelog.log, instead of
containing text lines, contained binary data. Is it possible the profiling
output from the agent went to servicelog.log instead of the eclipse
workbench?

I then set the MARTINI env variables. The result is here:
All entries in the M*log file are 'informative'.

servicelog.log is also bin data. (40kb)

in eclipse, Execution Time ANalysis are all empty.

Your help is appreciated,
Re: Attaching to remote JVM to profile it from workbench fails [message #112892 is a reply to message #112223] Thu, 20 September 2007 11:43 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hichamm.orcsoftware.com

Hi,
Any other suspicions here :-?
Re: Attaching to remote JVM to profile it from workbench fails [message #112945 is a reply to message #112223] Thu, 20 September 2007 14:44 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf YaffeFriend
Messages: 333
Registered: July 2009
Senior Member
Hicham wrote:
> Your suspicion was correct.
> Removing the debugger from the JVM let the eclipse attach correctly to
> the JVM.
> I managed to monitor the JVM from eclipse, my filter was properly defined,
> and i didn't get any info into the workbench alors.
> It said in the bottom "Time elapsed" 200seconds
>
> One thing though, on the server box,.../config/servicelog.log, instead
> of containing text lines, contained binary data. Is it possible the
> profiling output from the agent went to servicelog.log instead of the
> eclipse workbench?
>
> I then set the MARTINI env variables. The result is here:
> All entries in the M*log file are 'informative'.
>
> servicelog.log is also bin data. (40kb)
>
> in eclipse, Execution Time ANalysis are all empty.
>
> Your help is appreciated,
>
I am sorry, but I was under the impression that your problem was
resolved. Can you please describe the problem in more details?

Thanks,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: Attaching to remote JVM to profile it from workbench fails [message #113023 is a reply to message #112945] Fri, 21 September 2007 08:33 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hichamm.orcsoftware.com

Hello

I managed to connect eclipse to the remote JVM, my filter was properly
defined,
but i didn't get any info into the workbench. In the bottom, it says "Time
elapsed 200seconds"

One thing though, on the server box,../config/servicelog.log, instead of
containing text lines as usual, contained binary data. Is it possible the
profiling output from the agent went to servicelog.log instead of the
eclipse workbench?

I then set the MARTINI env variables. All entries in the M*log file are
'informative' entries. No errros.

in eclipse, Execution Time Analysis window is all empty.

rds,
Re: Attaching to remote JVM to profile it from workbench fails [message #113156 is a reply to message #113023] Mon, 24 September 2007 08:52 Go to previous message
Eclipse UserFriend
Originally posted by: hichamm.orcsoftware.com

Please let me know what kind of additional details i can provide.
Previous Topic:IWAT0284E error
Next Topic:C/C++ code review
Goto Forum:
  


Current Time: Fri Nov 28 19:45:49 GMT 2014

Powered by FUDForum. Page generated in 0.13374 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software