Home » Archived » Test and Performance Tools Platform (TPTP) » Getting the new technology agent controller working
| Getting the new technology agent controller working [message #63969] |
Tue, 04 April 2006 15:29  |
Eclipse User |
|
|
|
I've downloaded and installed the new technology agent controller. I have
followed the instructions in the readme.txt file, however, when I try to
run SampleClient, it just stops after printing the Agent ID.
Here is the output from the SampleClient shell:
[bin]$ SampleClient
Connected to the Agent Controller on "localhost" at port number 10006
The Time Collector Agent ID: 102
Also, when trying to run a test suite in tptp, this is the exception trace
I see from the tptpAgentController shell:
[bin]$ tptpAgentCtlr
Exception in thread "Reader Thread: IBMRAC:ramaster"
java.lang.NullPointerException
at java.util.Hashtable.getEntry(Hashtable.java:492)
at java.util.Hashtable.containsKey(Hashtable.java:368)
at
org.eclipse.tptp.platform.agentcontroller.internal.impl.Traf ficControllerImpl.getTransport(TrafficControllerImpl.java:21 8)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.waitUntilFlushCompleted(Hyades MessageProcessorImpl.java:1339)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.processExited(HyadesMessagePro cessorImpl.java:1258)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.processExited(HyadesMessagePro cessorImpl.java:1233)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.pr oxy.ProcessProxy.processExited(ProcessProxy.java:181)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.agentInactive(HyadesMessagePro cessorImpl.java:1307)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.pr oxy.AgentProxy.setActive(AgentProxy.java:90)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.handleAgentInactive(HyadesMess ageProcessorImpl.java:261)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.incommingCommand(HyadesMessage ProcessorImpl.java:212)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesMessageProcessorImpl.incommingMessage(HyadesMessage ProcessorImpl.java:114)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesByteProcessorImpl.processByteStream(HyadesByteProce ssorImpl.java:197)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesByteProcessorImpl.incommingBytes(HyadesByteProcesso rImpl.java:84)
at
org.eclipse.tptp.platform.agentcontroller.internal.hyades.im pl.HyadesProcessingModuleImpl.incommingBytes(HyadesProcessin gModuleImpl.java:68)
at
org.eclipse.tptp.platform.agentcontroller.internal.transport .impl.DataReaderThreadImpl.run(DataReaderThreadImpl.java:46)
|
|
| | | |
| Re: Getting the new technology agent controller working [message #64764 is a reply to message #64318] |
Thu, 06 April 2006 10:49  |
| Eclipse User |
|
|
|
Jeremy McJunkin wrote:
> The version I downloaded was 4.1.0.1, this was from the downloads page
> in the new technology agent controller section.
>
I've asked the rest of our team to look at this... I'm a little confused
about what I'm seeing here.
You did edit the <Install-Dir>/agents/*/agent.xml files, right? They
have Windows-isms in them by default that have to be edited to get it
working.
Can you elaborate on what you're doing by way of the "test suite" you
refer to? Again, that sounds a lot like using the Eclipse workbench's
TPTP Profiling and Logging view... and in the "new technology AC" of
4.1.0.1, there's not a lot to connect to at that point in time. Yes,
you're right, at least SampleClient *should* work!
Meanwhile, I'll download and try following the instructions myself to
see if I've missed something... I haven't used 4.1 in a while since
we've been working on 4.2
What version of the JDK are you using? Whose is it? (IBM, Sun, ?) What
version of Linux are you on??
Thanks,
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Getting the new technology agent controller working [message #64810 is a reply to message #64764] |
Thu, 06 April 2006 11:38 |
| Eclipse User |
|
|
|
Randy D. Smith wrote:
> Jeremy McJunkin wrote:
>> The version I downloaded was 4.1.0.1, this was from the downloads page
>> in the new technology agent controller section.
>>
> I've asked the rest of our team to look at this... I'm a little confused
> about what I'm seeing here.
> You did edit the <Install-Dir>/agents/*/agent.xml files, right? They
> have Windows-isms in them by default that have to be edited to get it
> working.
> Can you elaborate on what you're doing by way of the "test suite" you
> refer to? Again, that sounds a lot like using the Eclipse workbench's
> TPTP Profiling and Logging view... and in the "new technology AC" of
> 4.1.0.1, there's not a lot to connect to at that point in time. Yes,
> you're right, at least SampleClient *should* work!
> Meanwhile, I'll download and try following the instructions myself to
> see if I've missed something... I haven't used 4.1 in a while since
> we've been working on 4.2
> What version of the JDK are you using? Whose is it? (IBM, Sun, ?) What
> version of Linux are you on??
h
> Thanks,
Well, SampleClient just started to work after I restarted my machine, I
noticed in the log file that it could not access the shared memory but I
am not sure if this was from the previous running of SampleClient or from
tptp in eclipse. I have not had a chance to test tptp in eclipse yet
becuase I just used the callipso update site and now the test perspective
no longer exists, so I am using the tptp update site hoping that will fix
it. By the way, I was using ibm's 1.5 jdk for eclipse, but
tptpAgentController was using ibm's 1.42 jdk. Could this be a problem?
Also, I am running on an internal linux offering based on rhel 4
|
|
|
| Re: Getting the new technology agent controller working [message #65455 is a reply to message #64810] |
Mon, 10 April 2006 18:41 |
| Eclipse User |
|
|
|
Jeremy McJunkin wrote:
> Well, SampleClient just started to work after I restarted my machine, I
> noticed in the log file that it could not access the shared memory but I
> am not sure if this was from the previous running of SampleClient or
> from tptp in eclipse.
Almost certainly the previous run of SampleClient... we had a problem
where TimeCollector (SampleClient's agent) was sticking around holding
onto shared memory... I think the fix to that is coming in the 4.2i2
build that's about to be done. Moral of the story... if you run into
similar problems in the future, look at your ps results to see if the
tptpProcessController or any other agent (e.g., TimeCollector) is
hanging around once the tptpAgentCtlr goes away... if so, it needs to be
killed. Like I said, fixed in 4.2i2.
> I have not had a chance to test tptp in eclipse
> yet becuase I just used the callipso update site and now the test
> perspective no longer exists, so I am using the tptp update site hoping
> that will fix it. By the way, I was using ibm's 1.5 jdk for eclipse,
> but tptpAgentController was using ibm's 1.42 jdk. Could this be a
> problem? Also, I am running on an internal linux offering based on rhel 4
I've used 1.5 and 1.4.2, but I'm not sure I've mixed and matched them as
you have. I'm really not sure whether that can cause problems. Frankly,
I'm as concerned about the RHEL 4 as I am about the JVMs... I'm not sure
if anyone here is testing on RHEL 4 yet... I'll check around.
But your references to TPTP in Eclipse and the new tech AC together
concern me a bit, particularly as you refer to 4.1.0.1. Let me repeat
something I said on another thread, edited somewhat:
"Bottom line, the new tech AC was meant for "new agent and *client*
work" in TPTP 4.1 ... it was never intended (then) to be a replacement
for the RAC (original AC) in an environment with an *unchanged* Eclipse
workbench. The Eclipse workbench really doesn't "know about" the AC in
that release. .... We intentionally used a different port as we talked
a different protocol. So for 4.1.0.1, if you want to use Eclipse
workbench functionality, you'll need to talk to the RAC (or IAC), not
the new tech AC.
That all being said, let me mention that *the* emphasis for the new tech
AC for 4.2 is precisely what you're doing, which is provide this new
tech agent controller listening on the same port (10002) for the same
protocol, that is, we're providing backward compatibility (BC) to the
RAC via the AC... I call it AC/BC... but some here say that's "too cute".
.... but you'll have to track the 4.2 development at least through the
pending release of the 4.2i2 stable build RSN (real soon now) if you
want to work with the new tech AC in such an environment."
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Getting the new technology agent controller working [message #66035 is a reply to message #65455] |
Tue, 11 April 2006 17:54 |
| Eclipse User |
|
|
|
Randy D. Smith wrote:
> Jeremy McJunkin wrote:
>> I have not had a chance to test tptp in eclipse yet becuase I just
>> used the callipso update site and now the test perspective no longer
>> exists, so I am using the tptp update site hoping that will fix it.
>> By the way, I was using ibm's 1.5 jdk for eclipse, but
>> tptpAgentController was using ibm's 1.42 jdk. Could this be a
>> problem? Also, I am running on an internal linux offering based on
>> rhel 4
As a result of helping Lisa in a separate thread, she directed me to
some earlier release notes that had an interesting item I thought I'd
mention here, as they might become relevant later on; be ye forewarned:
"Symptom 3: Profiling data is not collected and the process console is
unavailable
A launched process from the Profiling Perspective appears in the
Profiling Monitor but no profiling data is collected. The process
console standard in, standard out, and standard error are also
unavailable. These problems can be due to any of the following causes:
....
Cause 4: The JRE used to build a test case needs to be the JRE used to
start Eclipse
Edit the Eclipse workbench preference:
1. Click Window > Preference...
2. Select Java > Installed JREs
3. Select the JRE used to start Eclipse. If this JRE is not in the
list, create it."
I'd never noticed that one before! Interesting!!
Not sure if it will continue to be relevant or not... this was from the
latest release notes (for 4.1), but it's worth noting that there is an
explicit situation where mixing and matching JREs can be dangerous.
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
Goto Forum:
Current Time: Fri Oct 31 10:11:21 EDT 2025
Powered by FUDForum. Page generated in 0.04004 seconds |
Home