|TPTP 4.1 install problems [java.exe - Ordinal Not Found]? [message #64718]
||Thu, 06 April 2006 09:58
Registered: July 2009
I've installed TPTP188.8.131.52 on Windows XP SP2, Eclipse 3.1.1 (with EMF) with
"new technology" tptpAgentCtlr.exe.
Sample client for agent testing works nicely. TPTP environment in Eclipse
works and similar to documentation.
Note: Eclipse JRE - j2re1.4.2_09.
During invocation select test suite -> Run as... -> Test causing error:
java.exe - Ordinal Not Found
The ordinal 43 could not be located in dynamic link library hcclco.dll
Please explain what can be wrong with my env.?
|Re: TPTP 4.1 install problems [java.exe - Ordinal Not Found]? [message #65392 is a reply to message #64718]
||Mon, 10 April 2006 17:38
| Randy D. Smith
Registered: July 2009
> I've installed TPTP184.108.40.206 on Windows XP SP2, Eclipse 3.1.1 (with EMF) with
> "new technology" tptpAgentCtlr.exe.
> Sample client for agent testing works nicely. TPTP environment in Eclipse
> works and similar to documentation.
> Note: Eclipse JRE - j2re1.4.2_09.
> During invocation select test suite -> Run as... -> Test causing error:
> java.exe - Ordinal Not Found
> The ordinal 43 could not be located in dynamic link library hcclco.dll
> Please explain what can be wrong with my env.?
I think part of our team (mostly the IBMers) are shying away from your
question because of the reference to the new tech AC, while another part
of our team (particularly us Intelers) are shying away because you're
asking about the behavior of the Eclipse workbench... and most of our
focus has been "under the hood" in AC-land.
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. I'm sort of curious how you managed to make the workbench
aware of the AC.... did you change the serviceconfig's port to the 10002
port the workbench talks to? We intentionally used a different port as
we talked a different protocol. So for 220.127.116.11, 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".
What you're seeing (the "ordinal 43...") is what we see when we get
mismatched libraries in our BC efforts... but for the most part when we
get it packaged right, it works quite well... 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.
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
Powered by FUDForum
. Page generated in 0.07722 seconds