Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » object interactions view not available
object interactions view not available [message #50083] Thu, 12 January 2006 17:18 Go to next message
Holger Machens is currently offline Holger Machens
Messages: 57
Registered: July 2009
Member
This is a multi-part message in MIME format.
--------------050000070305080900090005
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi folks,


i ported our tracing plugin to tptp 4.1. All works fine but it's no
longer possible to open the object interactions view: i.e. it's
disabled in the "context menu -> open with .." sub group.

I compared our trace file (see attachment) to a trace file
generated by your java profiler but i can't see any significant
difference which might explain the other behavior.

Any idea?


Thanks in advance
Holger


P.S. The attached file is the trace agent file copied from the
workspace directory.

--------------050000070305080900090005
Content-Type: application/octet-stream;
name="trace_agent.trcaxmi"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="trace_agent.trcaxmi"

UEsDBBQACAAIAAGQLDQAAAAAAAAAAAAAAAAQAAQAUmVzb3VyY2VDb250ZW50 c/7KAADdWNtu
4zYQfd+vENSHtmgtcXSljPVusomDuEiyQdcB9s1gJMZWI4uCRNnx33eoixPF l3pzKdDqQZY4
Q87MOTNDyh8/P8wTbcHzIhbpQAeD6BpPQxHF6XSg34zPelT//OmD9vE85jnL w9mqP/7z5HjK
U6k9zOP+eqalZuJaadHH8YE+kzLrm+ZyuTTEfGqIfGp+vxytVYquytKuNCxC ANUuvoUzPme9
OC0kS0Pezlr70JnLwyTOCl4tMFuxiBfmXEQ8KcxZq2+gS+0i45yF/MAFpNKt J6dsjrMifKsv
o9Y0srhSyo3rXNzFCc9B1+QqQ912QNfyMpXxnI8iRPRmdNoDsH1CwfecnufY 4Nk9Cxx88mzP
64FNiBvYFrV0DcPP5ThWlsFoJlHieO4wUEKRdWXUB9+3h4AzQ5EkPJRIzSWG MtDPh8fXk+Or
08nw+/DkZjz6ejU5u7m40BW1WS5CXhQaktKvXa8wUkRf1yJdy2J0Hizw3QOg kLyQxjeeL1Tw
auL1by+OuweuQakb4AV+QB1COqF7xCCuS/DyPN/1cW7CCjlcYH7uUojTWJ7h rZjxaI+NW1bw
WkwMsGyUUdshHi5DAwQhLOdlwmS82KvEkqQY6LYyOuN5LHn0Zf+ya72Tg9av WebRqKkUNGZV
nMpZzllUNFyNqzcNK3SaizK7qgZfB7NCMWbJKF2IkKk8Q9OmedTkknkUPwqw M5hPfVIZ0bOI
5wRo0A/0rpMdyS53XcuglqX8sTyfWJS+nbOg7ZJYdRgZC+/ZlLfYtllvYgsp I4HVL6QytSYE
tvMEFU8hpmuBaxWizEM+Su9E17PHcQVjBZ3tubblBha0wF2yOD1R6/yAba0y /PX2LxQ9A0PU
g2hOOTjnciZa0jxCqRe4sDY9R9MIfTxNmSxzHPjl13XWQw2X2YRYPbfYbcFR NY23qbr3qbV3
oxVqWgFcH2wXbLsF95wnifhfQKIlAneI6Muqi0LTEIyD0hE20xF3EIqQEd9p IZtyOSlkjoeX
jazswAhUdTqXEpvauO/QrTBuUepkdtcXi1iuC4673iBZPi26XiC8iEQ6rW6T BUtK/juOiVJq
kShvE978tCIlqKNpfmrBs2AIcRQxvkcsy7axQP1t0WzV2h0ORkMCJ1DNs46G P4Q8U31wgqyJ
5XN4twDiUY/4geWTdoliVspILDcaxv428aRUELe6Fw/00elF/1nnNdd9sA/t lrN7smo3ZlVh
j9pNqm07CJ1zltXpqTcAgWO7rgee2l6K427Otv4bxDxq4jrAxlmZJNXLaw1p dWFtLzYUh/gk
+e6N/0fBAGoHgGWo6nC3i/BqLF5gZy8U0IViy6HiDXpvFemTY8SuaC+r4nk8 ouhaXU4HEG4e
NZV3APdYf9hIalR37fv4BSjz1Z6DoYzDey4VIdTBJgmB815hwkvChEPChE6Y W7jnD/HjaTNw
iIKAOr4D6uTVItCzCRDAxk/1FoB7tdFp6MrdQD/ld6xM5KXAA6jIJ4uCwASU Hbz/wdKS5St8
8QBNuoH4OcQedX8yHE/aLyU/cCxncshXpyHzkOGX6k//cAg3n4z9m5TBm1NW HfMVYxAQ33ao
95SyzW+ADcb8/yhjZqOsnpn6IwZXfNjvPn62T8azEv1XzwQPM+iyCkP5kDU+ rNeKHzu0ufm3
z6cPfwNQSwcIYpvlWeMEAAA0EgAAUEsBAhQAFAAIAAgAAZAsNGKb5VnjBAAA NBIAABAABAAA
AAAAAAAAAAAAAAAAAFJlc291cmNlQ29udGVudHP+ygAAUEsFBgAAAAABAAEA QgAAACUFAAAA
AA==
--------------050000070305080900090005--
Re: object interactions view not available [message #50142 is a reply to message #50083] Thu, 12 January 2006 17:25 Go to previous messageGo to next message
Eclipse User
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 005FBB8E852570F4_=
Content-Type: text/plain; charset="US-ASCII"

This was a change made in the 4.1 driver. In your profiling set ->
select Execution time analysis -> Advanced -> Select Collect instance
level information -> try profiling now. You should now see the object
interaction view.

Navid Mehregani
--=_alternative 005FBB8E852570F4_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">This was &nbsp;a change made in the
4.1 driver. &nbsp;In your profiling set -&gt; select Execution time analysis
-&gt; Advanced -&gt; Select Collect instance level information -&gt; try
profiling now. &nbsp;You should now see the object interaction view.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 005FBB8E852570F4_=--
Re: object interactions view not available [message #50233 is a reply to message #50142] Thu, 12 January 2006 18:22 Go to previous messageGo to next message
Holger Machens is currently offline Holger Machens
Messages: 57
Registered: July 2009
Member
Navid_Mehregani_nmehrega@ca.ibm.com wrote:

>This was a change made in the 4.1 driver. In your profiling set ->
>select Execution time analysis -> Advanced -> Select Collect instance
>level information -> try profiling now. You should now see the object
>interaction view.
>
>Navid Mehregani
>
>

Hi Navid,

thanks for your help, but i already did it.

More information:
The context menu entry "object interactions" is visible but grayed
(disabled).

Any other ideas?


Thanks
Holger
Re: object interactions view not available [message #50464 is a reply to message #50233] Fri, 13 January 2006 18:43 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 404
Registered: July 2009
Senior Member
I tried to tinker around with the trace files generated by the Java
profiler. It seems that if the model detects an invalid object reference,
it will make the UI disable the object interaction view.

Can you make sure that your trace file generated by your plugin includes:
- <objAlloc events
- Reports objIdRef on threadStart, classDef, methodEntry, and methodExit
events. This attribute determines whether the references are correct or
not.

Can you also attach a trace file that your plugin generates before the
events are loaded to the loaders (i.e. a trace file similar to one that you
get when you set the "Send profiling data to a file" option under the
destination tab when profiling a Java application)

As an example, consider the following trace. This trace file doesn't
include the <objAlloc events but it does include objIdRef attributres:

<?xml version="1.0"?>
<TRACE>
<node nodeId="35c9d850-cb8f-4608-a943-c40c9767e04d" hostname="amehregani"
ipaddress="9.26.150.231,127.0.0.1" timezone="300"
time="1137109936.625000000"/>
<processCreate processId="d280c69b-0aea-4650-aba7-ce71ae5cbac2" pid="3640"
nodeIdRef="35c9d850-cb8f-4608-a943-c40c9767e04d"
time="1137109936.625000000"/>
<agentCreate agentId="b67d1048-9d21-44d7-bdce-257bc6ce22ea" version="1.000"
processIdRef="d280c69b-0aea-4650-aba7-ce71ae5cbac2" agentName="Java
Profiling Agent" agentType="Profiler" agentParameters="server=controlled"
time="1137109936.764999866"/>
<traceStart traceId="17abeaa0-5fb4-4e38-939e-2db6674746f2"
agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
time="1137109936.930803298"/>
<threadStart threadId="2" time="1137109936.938701152" threadName="main"
groupName="main" parentName="system" objIdRef="0"/>
<classDef threadIdRef="2" name="int" sourceName="" classId="5"
time="1137109936.946427106"/>
<runtimeInitDone threadIdRef="2" time="1137109936.968850612"/>
<classDef threadIdRef="4" name="java.lang.Class" sourceName="Class.java"
classId="89" time="1137109936.945830821"/>
<classDef threadIdRef="4" name="java.lang.Thread" sourceName="Thread.java"
classId="324" time="1137109936.947596311"/>
<threadStart threadId="4" time="1137109936.998217821" threadName="Signal
Dispatcher" groupName="system" parentName="" objIdRef="3850"/>
<classDef threadIdRef="2" name="MainClass" sourceName="MainClass.java"
classId="5576" time="1137109937.099534034"/>
<methodDef name="main" signature="([Ljava/lang/String;)V"
startLineNumber="20" endLineNumber="21" methodId="5574" classIdRef="5576"/>
<methodEntry threadIdRef="2" time="1137109937.099518775" methodIdRef="5574"
classIdRef="5576" ticket="5795" stackDepth="1"/>
<classDef threadIdRef="2" name="java.lang.ClassLoader"
sourceName="ClassLoader.java" classId="3975" time="1137109937.000886678"/>
<methodDef name="checkPackageAccess"
signature="(Ljava/lang/Class;Ljava/security/ProtectionDomain;)V "
startLineNumber="306" endLineNumber="320" methodId="3965"
classIdRef="3975"/>
<classDef threadIdRef="2" name="sun.misc.Launcher$AppClassLoader"
sourceName="Launcher.java" classId="2441" objIdRef="2443"
time="1137109936.958760738"/>
<methodEntry threadIdRef="2" time="1137109937.099586486" methodIdRef="3965"
objIdRef="2443" classIdRef="3975" ticket="5796" stackDepth="2"/>
<methodExit threadIdRef="2" methodIdRef="3965" objIdRef="2443"
classIdRef="3975" ticket="0" time="1137109937.099647998"
overhead="0.000036774"/>
<methodExit threadIdRef="2" methodIdRef="5574" classIdRef="5576"
ticket="5795" time="1137109937.101277828" overhead="0.000083538"/>
<threadEnd threadIdRef="2" time="1137109937.101340532"/>
<threadStart threadId="5" time="1137109937.102098941"
threadName="DestroyJavaVM" groupName="main" parentName="system"
objIdRef="5668"/>
<threadEnd threadIdRef="5" time="1137109937.115652561"/>
<runtimeShutdown threadIdRef="1" time="1137109937.115679502"/>
<traceEnd time="1137109937.115683794"/>
<agentDestroy agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
time="1137109937.115689754"/>
</TRACE>


If you take out the objIdRef attribute of <methodEntry threadIdRef="2"
time="1137109937.099586486" methodIdRef="3965" objIdRef="2443"
classIdRef="3975" ticket="5796" stackDepth="2"/>, then the object references
will be broken and the menu item will be disabled.

Hope this helps.


"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
news:dq66ob$otn$1@utils.eclipse.org...
>
> Navid_Mehregani_nmehrega@ca.ibm.com wrote:
>
> >This was a change made in the 4.1 driver. In your profiling set ->
> >select Execution time analysis -> Advanced -> Select Collect instance
> >level information -> try profiling now. You should now see the object
> >interaction view.
> >
> >Navid Mehregani
> >
> >
>
> Hi Navid,
>
> thanks for your help, but i already did it.
>
> More information:
> The context menu entry "object interactions" is visible but grayed
> (disabled).
>
> Any other ideas?
>
>
> Thanks
> Holger
>
Re: object interactions view not available [message #50688 is a reply to message #50464] Mon, 16 January 2006 15:38 Go to previous messageGo to next message
Holger Machens is currently offline Holger Machens
Messages: 57
Registered: July 2009
Member
Hi Ali,


thanks for your reply and for the time you spent in searching
the right answer, but you get me slightly wrong.

The file i gave you in my first post is not the data send by
the agent - it's the data stored in workspace
(ok, indirectly it's send by the agent ;) ).

You can look at it's contents by using the command:
> jar xf <filename>

I already looked for dangling references but i didn't find
one.


Maybe one can tell me, which integrity checks are done
when the viewer plugin starts up or which decisions lead
to the grayed context menu entry "object interactions".


Thanks
Holger


Ali Mehregani wrote:

>I tried to tinker around with the trace files generated by the Java
>profiler. It seems that if the model detects an invalid object reference,
>it will make the UI disable the object interaction view.
>
>Can you make sure that your trace file generated by your plugin includes:
>- <objAlloc events
>- Reports objIdRef on threadStart, classDef, methodEntry, and methodExit
>events. This attribute determines whether the references are correct or
>not.
>
>Can you also attach a trace file that your plugin generates before the
>events are loaded to the loaders (i.e. a trace file similar to one that you
>get when you set the "Send profiling data to a file" option under the
>destination tab when profiling a Java application)
>
>As an example, consider the following trace. This trace file doesn't
>include the <objAlloc events but it does include objIdRef attributres:
>
><?xml version="1.0"?>
><TRACE>
><node nodeId="35c9d850-cb8f-4608-a943-c40c9767e04d" hostname="amehregani"
>ipaddress="9.26.150.231,127.0.0.1" timezone="300"
>time="1137109936.625000000"/>
><processCreate processId="d280c69b-0aea-4650-aba7-ce71ae5cbac2" pid="3640"
>nodeIdRef="35c9d850-cb8f-4608-a943-c40c9767e04d"
>time="1137109936.625000000"/>
><agentCreate agentId="b67d1048-9d21-44d7-bdce-257bc6ce22ea" version="1.000"
>processIdRef="d280c69b-0aea-4650-aba7-ce71ae5cbac2" agentName="Java
>Profiling Agent" agentType="Profiler" agentParameters="server=controlled"
>time="1137109936.764999866"/>
><traceStart traceId="17abeaa0-5fb4-4e38-939e-2db6674746f2"
>agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
>time="1137109936.930803298"/>
><threadStart threadId="2" time="1137109936.938701152" threadName="main"
>groupName="main" parentName="system" objIdRef="0"/>
><classDef threadIdRef="2" name="int" sourceName="" classId="5"
>time="1137109936.946427106"/>
><runtimeInitDone threadIdRef="2" time="1137109936.968850612"/>
><classDef threadIdRef="4" name="java.lang.Class" sourceName="Class.java"
>classId="89" time="1137109936.945830821"/>
><classDef threadIdRef="4" name="java.lang.Thread" sourceName="Thread.java"
>classId="324" time="1137109936.947596311"/>
><threadStart threadId="4" time="1137109936.998217821" threadName="Signal
>Dispatcher" groupName="system" parentName="" objIdRef="3850"/>
><classDef threadIdRef="2" name="MainClass" sourceName="MainClass.java"
>classId="5576" time="1137109937.099534034"/>
><methodDef name="main" signature="([Ljava/lang/String;)V"
>startLineNumber="20" endLineNumber="21" methodId="5574" classIdRef="5576"/>
><methodEntry threadIdRef="2" time="1137109937.099518775" methodIdRef="5574"
>classIdRef="5576" ticket="5795" stackDepth="1"/>
><classDef threadIdRef="2" name="java.lang.ClassLoader"
>sourceName="ClassLoader.java" classId="3975" time="1137109937.000886678"/>
><methodDef name="checkPackageAccess"
>signature="(Ljava/lang/Class;Ljava/security/ProtectionDomain;)V "
>startLineNumber="306" endLineNumber="320" methodId="3965"
>classIdRef="3975"/>
><classDef threadIdRef="2" name="sun.misc.Launcher$AppClassLoader"
>sourceName="Launcher.java" classId="2441" objIdRef="2443"
>time="1137109936.958760738"/>
><methodEntry threadIdRef="2" time="1137109937.099586486" methodIdRef="3965"
>objIdRef="2443" classIdRef="3975" ticket="5796" stackDepth="2"/>
><methodExit threadIdRef="2" methodIdRef="3965" objIdRef="2443"
>classIdRef="3975" ticket="0" time="1137109937.099647998"
>overhead="0.000036774"/>
><methodExit threadIdRef="2" methodIdRef="5574" classIdRef="5576"
>ticket="5795" time="1137109937.101277828" overhead="0.000083538"/>
><threadEnd threadIdRef="2" time="1137109937.101340532"/>
><threadStart threadId="5" time="1137109937.102098941"
>threadName="DestroyJavaVM" groupName="main" parentName="system"
>objIdRef="5668"/>
><threadEnd threadIdRef="5" time="1137109937.115652561"/>
><runtimeShutdown threadIdRef="1" time="1137109937.115679502"/>
><traceEnd time="1137109937.115683794"/>
><agentDestroy agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
>time="1137109937.115689754"/>
></TRACE>
>
>
>If you take out the objIdRef attribute of <methodEntry threadIdRef="2"
>time="1137109937.099586486" methodIdRef="3965" objIdRef="2443"
>classIdRef="3975" ticket="5796" stackDepth="2"/>, then the object references
>will be broken and the menu item will be disabled.
>
>Hope this helps.
>
>
>"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
>news:dq66ob$otn$1@utils.eclipse.org...
>
>
>>Navid_Mehregani_nmehrega@ca.ibm.com wrote:
>>
>>
>>
>>>This was a change made in the 4.1 driver. In your profiling set ->
>>>select Execution time analysis -> Advanced -> Select Collect instance
>>>level information -> try profiling now. You should now see the object
>>>interaction view.
>>>
>>>Navid Mehregani
>>>
>>>
>>>
>>>
>>Hi Navid,
>>
>>thanks for your help, but i already did it.
>>
>>More information:
>>The context menu entry "object interactions" is visible but grayed
>>(disabled).
>>
>>Any other ideas?
>>
>>
>>Thanks
>> Holger
>>
>>
>>
>
>
>
>
Re: object interactions view not available [message #55834 is a reply to message #50688] Wed, 01 March 2006 09:52 Go to previous messageGo to next message
Holger Machens is currently offline Holger Machens
Messages: 57
Registered: July 2009
Member
?

Holger Machens wrote:
> Hi Ali,
>
>
> thanks for your reply and for the time you spent in searching
> the right answer, but you get me slightly wrong.
>
> The file i gave you in my first post is not the data send by
> the agent - it's the data stored in workspace
> (ok, indirectly it's send by the agent ;) ).
>
> You can look at it's contents by using the command:
>
>>jar xf <filename>
>
>
> I already looked for dangling references but i didn't find
> one.
>
>
> Maybe one can tell me, which integrity checks are done
> when the viewer plugin starts up or which decisions lead
> to the grayed context menu entry "object interactions".
>
>
> Thanks
> Holger
>
>
> Ali Mehregani wrote:
>
>
>>I tried to tinker around with the trace files generated by the Java
>>profiler. It seems that if the model detects an invalid object reference,
>>it will make the UI disable the object interaction view.
>>
>>Can you make sure that your trace file generated by your plugin includes:
>>- <objAlloc events
>>- Reports objIdRef on threadStart, classDef, methodEntry, and methodExit
>>events. This attribute determines whether the references are correct or
>>not.
>>
>>Can you also attach a trace file that your plugin generates before the
>>events are loaded to the loaders (i.e. a trace file similar to one that you
>>get when you set the "Send profiling data to a file" option under the
>>destination tab when profiling a Java application)
>>
>>As an example, consider the following trace. This trace file doesn't
>>include the <objAlloc events but it does include objIdRef attributres:
>>
>><?xml version="1.0"?>
>><TRACE>
>><node nodeId="35c9d850-cb8f-4608-a943-c40c9767e04d" hostname="amehregani"
>>ipaddress="9.26.150.231,127.0.0.1" timezone="300"
>>time="1137109936.625000000"/>
>><processCreate processId="d280c69b-0aea-4650-aba7-ce71ae5cbac2" pid="3640"
>>nodeIdRef="35c9d850-cb8f-4608-a943-c40c9767e04d"
>>time="1137109936.625000000"/>
>><agentCreate agentId="b67d1048-9d21-44d7-bdce-257bc6ce22ea" version="1.000"
>>processIdRef="d280c69b-0aea-4650-aba7-ce71ae5cbac2" agentName="Java
>>Profiling Agent" agentType="Profiler" agentParameters="server=controlled"
>>time="1137109936.764999866"/>
>><traceStart traceId="17abeaa0-5fb4-4e38-939e-2db6674746f2"
>>agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
>>time="1137109936.930803298"/>
>><threadStart threadId="2" time="1137109936.938701152" threadName="main"
>>groupName="main" parentName="system" objIdRef="0"/>
>><classDef threadIdRef="2" name="int" sourceName="" classId="5"
>>time="1137109936.946427106"/>
>><runtimeInitDone threadIdRef="2" time="1137109936.968850612"/>
>><classDef threadIdRef="4" name="java.lang.Class" sourceName="Class.java"
>>classId="89" time="1137109936.945830821"/>
>><classDef threadIdRef="4" name="java.lang.Thread" sourceName="Thread.java"
>>classId="324" time="1137109936.947596311"/>
>><threadStart threadId="4" time="1137109936.998217821" threadName="Signal
>>Dispatcher" groupName="system" parentName="" objIdRef="3850"/>
>><classDef threadIdRef="2" name="MainClass" sourceName="MainClass.java"
>>classId="5576" time="1137109937.099534034"/>
>><methodDef name="main" signature="([Ljava/lang/String;)V"
>>startLineNumber="20" endLineNumber="21" methodId="5574" classIdRef="5576"/>
>><methodEntry threadIdRef="2" time="1137109937.099518775" methodIdRef="5574"
>>classIdRef="5576" ticket="5795" stackDepth="1"/>
>><classDef threadIdRef="2" name="java.lang.ClassLoader"
>>sourceName="ClassLoader.java" classId="3975" time="1137109937.000886678"/>
>><methodDef name="checkPackageAccess"
>>signature="(Ljava/lang/Class;Ljava/security/ProtectionDomain;)V "
>>startLineNumber="306" endLineNumber="320" methodId="3965"
>>classIdRef="3975"/>
>><classDef threadIdRef="2" name="sun.misc.Launcher$AppClassLoader"
>>sourceName="Launcher.java" classId="2441" objIdRef="2443"
>>time="1137109936.958760738"/>
>><methodEntry threadIdRef="2" time="1137109937.099586486" methodIdRef="3965"
>>objIdRef="2443" classIdRef="3975" ticket="5796" stackDepth="2"/>
>><methodExit threadIdRef="2" methodIdRef="3965" objIdRef="2443"
>>classIdRef="3975" ticket="0" time="1137109937.099647998"
>>overhead="0.000036774"/>
>><methodExit threadIdRef="2" methodIdRef="5574" classIdRef="5576"
>>ticket="5795" time="1137109937.101277828" overhead="0.000083538"/>
>><threadEnd threadIdRef="2" time="1137109937.101340532"/>
>><threadStart threadId="5" time="1137109937.102098941"
>>threadName="DestroyJavaVM" groupName="main" parentName="system"
>>objIdRef="5668"/>
>><threadEnd threadIdRef="5" time="1137109937.115652561"/>
>><runtimeShutdown threadIdRef="1" time="1137109937.115679502"/>
>><traceEnd time="1137109937.115683794"/>
>><agentDestroy agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
>>time="1137109937.115689754"/>
>></TRACE>
>>
>>
>>If you take out the objIdRef attribute of <methodEntry threadIdRef="2"
>>time="1137109937.099586486" methodIdRef="3965" objIdRef="2443"
>>classIdRef="3975" ticket="5796" stackDepth="2"/>, then the object references
>>will be broken and the menu item will be disabled.
>>
>>Hope this helps.
>>
>>
>>"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
>>news:dq66ob$otn$1@utils.eclipse.org...
>>
>>
>>
>>>Navid_Mehregani_nmehrega@ca.ibm.com wrote:
>>>
>>>
>>>
>>>
>>>>This was a change made in the 4.1 driver. In your profiling set ->
>>>>select Execution time analysis -> Advanced -> Select Collect instance
>>>>level information -> try profiling now. You should now see the object
>>>>interaction view.
>>>>
>>>>Navid Mehregani
>>>>
>>>>
>>>>
>>>>
>>>
>>>Hi Navid,
>>>
>>>thanks for your help, but i already did it.
>>>
>>>More information:
>>>The context menu entry "object interactions" is visible but grayed
>>>(disabled).
>>>
>>>Any other ideas?
>>>
>>>
>>>Thanks
>>>Holger
>>>
>>>
>>>
>>
>>
>>
>>
Re: object interactions view not available [message #56206 is a reply to message #55834] Thu, 02 March 2006 16:48 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 404
Registered: July 2009
Senior Member
Marius, do you know the answer to this?
Do the models expect something to be true for the object interactions to be
enabled?

"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
news:du3qsg$qsh$1@utils.eclipse.org...
> ?
>
> Holger Machens wrote:
> > Hi Ali,
> >
> >
> > thanks for your reply and for the time you spent in searching
> > the right answer, but you get me slightly wrong.
> >
> > The file i gave you in my first post is not the data send by
> > the agent - it's the data stored in workspace
> > (ok, indirectly it's send by the agent ;) ).
> >
> > You can look at it's contents by using the command:
> >
> >>jar xf <filename>
> >
> >
> > I already looked for dangling references but i didn't find
> > one.
> >
> >
> > Maybe one can tell me, which integrity checks are done
> > when the viewer plugin starts up or which decisions lead
> > to the grayed context menu entry "object interactions".
> >
> >
> > Thanks
> > Holger
> >
> >
> > Ali Mehregani wrote:
> >
> >
> >>I tried to tinker around with the trace files generated by the Java
> >>profiler. It seems that if the model detects an invalid object
reference,
> >>it will make the UI disable the object interaction view.
> >>
> >>Can you make sure that your trace file generated by your plugin
includes:
> >>- <objAlloc events
> >>- Reports objIdRef on threadStart, classDef, methodEntry, and methodExit
> >>events. This attribute determines whether the references are correct or
> >>not.
> >>
> >>Can you also attach a trace file that your plugin generates before the
> >>events are loaded to the loaders (i.e. a trace file similar to one that
you
> >>get when you set the "Send profiling data to a file" option under the
> >>destination tab when profiling a Java application)
> >>
> >>As an example, consider the following trace. This trace file doesn't
> >>include the <objAlloc events but it does include objIdRef attributres:
> >>
> >><?xml version="1.0"?>
> >><TRACE>
> >><node nodeId="35c9d850-cb8f-4608-a943-c40c9767e04d"
hostname="amehregani"
> >>ipaddress="9.26.150.231,127.0.0.1" timezone="300"
> >>time="1137109936.625000000"/>
> >><processCreate processId="d280c69b-0aea-4650-aba7-ce71ae5cbac2"
pid="3640"
> >>nodeIdRef="35c9d850-cb8f-4608-a943-c40c9767e04d"
> >>time="1137109936.625000000"/>
> >><agentCreate agentId="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
version="1.000"
> >>processIdRef="d280c69b-0aea-4650-aba7-ce71ae5cbac2" agentName="Java
> >>Profiling Agent" agentType="Profiler"
agentParameters="server=controlled"
> >>time="1137109936.764999866"/>
> >><traceStart traceId="17abeaa0-5fb4-4e38-939e-2db6674746f2"
> >>agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
> >>time="1137109936.930803298"/>
> >><threadStart threadId="2" time="1137109936.938701152" threadName="main"
> >>groupName="main" parentName="system" objIdRef="0"/>
> >><classDef threadIdRef="2" name="int" sourceName="" classId="5"
> >>time="1137109936.946427106"/>
> >><runtimeInitDone threadIdRef="2" time="1137109936.968850612"/>
> >><classDef threadIdRef="4" name="java.lang.Class" sourceName="Class.java"
> >>classId="89" time="1137109936.945830821"/>
> >><classDef threadIdRef="4" name="java.lang.Thread"
sourceName="Thread.java"
> >>classId="324" time="1137109936.947596311"/>
> >><threadStart threadId="4" time="1137109936.998217821" threadName="Signal
> >>Dispatcher" groupName="system" parentName="" objIdRef="3850"/>
> >><classDef threadIdRef="2" name="MainClass" sourceName="MainClass.java"
> >>classId="5576" time="1137109937.099534034"/>
> >><methodDef name="main" signature="([Ljava/lang/String;)V"
> >>startLineNumber="20" endLineNumber="21" methodId="5574"
classIdRef="5576"/>
> >><methodEntry threadIdRef="2" time="1137109937.099518775"
methodIdRef="5574"
> >>classIdRef="5576" ticket="5795" stackDepth="1"/>
> >><classDef threadIdRef="2" name="java.lang.ClassLoader"
> >>sourceName="ClassLoader.java" classId="3975"
time="1137109937.000886678"/>
> >><methodDef name="checkPackageAccess"
> >>signature="(Ljava/lang/Class;Ljava/security/ProtectionDomain;)V "
> >>startLineNumber="306" endLineNumber="320" methodId="3965"
> >>classIdRef="3975"/>
> >><classDef threadIdRef="2" name="sun.misc.Launcher$AppClassLoader"
> >>sourceName="Launcher.java" classId="2441" objIdRef="2443"
> >>time="1137109936.958760738"/>
> >><methodEntry threadIdRef="2" time="1137109937.099586486"
methodIdRef="3965"
> >>objIdRef="2443" classIdRef="3975" ticket="5796" stackDepth="2"/>
> >><methodExit threadIdRef="2" methodIdRef="3965" objIdRef="2443"
> >>classIdRef="3975" ticket="0" time="1137109937.099647998"
> >>overhead="0.000036774"/>
> >><methodExit threadIdRef="2" methodIdRef="5574" classIdRef="5576"
> >>ticket="5795" time="1137109937.101277828" overhead="0.000083538"/>
> >><threadEnd threadIdRef="2" time="1137109937.101340532"/>
> >><threadStart threadId="5" time="1137109937.102098941"
> >>threadName="DestroyJavaVM" groupName="main" parentName="system"
> >>objIdRef="5668"/>
> >><threadEnd threadIdRef="5" time="1137109937.115652561"/>
> >><runtimeShutdown threadIdRef="1" time="1137109937.115679502"/>
> >><traceEnd time="1137109937.115683794"/>
> >><agentDestroy agentIdRef="b67d1048-9d21-44d7-bdce-257bc6ce22ea"
> >>time="1137109937.115689754"/>
> >></TRACE>
> >>
> >>
> >>If you take out the objIdRef attribute of <methodEntry threadIdRef="2"
> >>time="1137109937.099586486" methodIdRef="3965" objIdRef="2443"
> >>classIdRef="3975" ticket="5796" stackDepth="2"/>, then the object
references
> >>will be broken and the menu item will be disabled.
> >>
> >>Hope this helps.
> >>
> >>
> >>"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
> >>news:dq66ob$otn$1@utils.eclipse.org...
> >>
> >>
> >>
> >>>Navid_Mehregani_nmehrega@ca.ibm.com wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>This was a change made in the 4.1 driver. In your profiling set ->
> >>>>select Execution time analysis -> Advanced -> Select Collect instance
> >>>>level information -> try profiling now. You should now see the object
> >>>>interaction view.
> >>>>
> >>>>Navid Mehregani
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>Hi Navid,
> >>>
> >>>thanks for your help, but i already did it.
> >>>
> >>>More information:
> >>>The context menu entry "object interactions" is visible but grayed
> >>>(disabled).
> >>>
> >>>Any other ideas?
> >>>
> >>>
> >>>Thanks
> >>>Holger
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
Re: object interactions view not available [message #69081 is a reply to message #56206] Sat, 29 April 2006 15:50 Go to previous message
Holger Machens is currently offline Holger Machens
Messages: 57
Registered: July 2009
Member
Hi all,


this is the code snippet i searched for:

public class OpenObjectInteraction{
....
public boolean isEnabledForObject(Object obj)
{
TraceProcesses currentProcesses = getCurrentProcesses(obj);

if (currentProcesses != null && currentProcesses.size() > 0)
{
TRCProcess process;
Iterator iter = currentProcesses.iterator();
while (iter.hasNext())
{
process = ((TraceProcess)iter.next()).getProcess();

if (process != null && process.getClassClass() != null && process.getObjects() != null
&& process.getClassClass().getObjects() != null)
{
if (process.getClassClass().getObjects().size() != process.getObjects().size())
return true;
}
}
}

return false;
}
....

Maybe this information is helpful for others too.

Cheers
Holger
Previous Topic:What's a Test Artifact?
Next Topic:TPTP & Python
Goto Forum:
  


Current Time: Mon Sep 22 10:17:31 GMT 2014

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

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