Community
Participate
Working Groups
Driver: tptp.sdk-TPTP-4.4.0-200705310943 To reproduce: - Launch a Java application in command prompt with -XrunpiAgent on Vista machine - Try to attach to process from Attach launch configuration. There is no agent listed available for attach. Problem does not exist if I shutdown IAC(in task manager) and use RAC instead.
Hi Eugene. I cannot reproduce using the TPTP-4.4.0-200705310943 driver. I am also using IBM JRE 1.5.0 SR4 to run the piAgent since this is the only IBM JRE 1.5 that supports Vista. Can you let me know what JRE are you using?
Eugene, can you try putting the bin directory of IAC in your PATH to see if it makes a difference? The bin directory of IAC should be in: <plugins_folder>\org.eclipse.tptp.platform.ac.win_ia32\agent_controller\bin Also, do you have the IAC started before or after you launch your java application on the command prompt? I sent an email a while back ago to Asaf, I think Joanna was CCed on it. I explained in that email why IAC shouldn't be used in the attach scenario and how it defeats the purpose of IAC if it's used in the attach scenario. Not sure if anyone still has that email in their inbox. If not, I can reiterate the reasons again.
*** Bug 190019 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Hi Eugene. I cannot reproduce using the TPTP-4.4.0-200705310943 driver. I am > also using IBM JRE 1.5.0 SR4 to run the piAgent since this is the only IBM JRE > 1.5 that supports Vista. > > Can you let me know what JRE are you using? > Samson, I am using IBM JRE 1.5.0 SR3. I will go get SR4. java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20061002a (SR3) ) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows 2000 x86-32 j9vmwi3223-20061 001 (JIT enabled) J9VM - 20060915_08260_lHdSMR JIT - 20060908_1811_r8 GC - 20060906_AA) JCL - 20061002
Samson, I retired with IBM SDK 1.5. SR 5 and it doens't help. Navide, I added the PATH with IAC /bin but it doens't help neither. The driver I used is all-in-one. I wonder if there is anything missed in that driver. I will download with SDK build again. FYI, the driver I am using is setup on rnq03, under c:\Eugene\4400-0531\ in case you want to try it also.
I retired with SDK build and same result. Navid, I tried both scenario 1) start IAC before Java process, or 2)Start Java process before IAC, and none of them works.
(In reply to comment #5) > The driver I used is all-in-one. I wonder if there is anything missed in that > driver. I will download with SDK build again. > You probably already know this, but if you use the all-in-one driver from our *internal* build page, it won't include IAC. Can you also look into your error log file to see if it contains anything?
Yes Navid. I aware of that and I download the all-in-one from TPTP download page. Double checked on .metadata and there is nothing in .log (.log is not created) =(
If the ACServer.exe process starts up, then the problem can only be in two different areas: 1) There could be something wrong with the configuration file for IAC. You can check the configuration file in <plugins_folder>\org.eclipse.tptp.platform.ac.win_ia32\agent_controller\config\serviceconfig.xml You can regenerate IAC's configuration through its preference page 2) There could be a general problem with the *Agent Controller* querying and obtaining its agents. You can check the log file in <plugins_folder>\org.eclipse.tptp.platform.ac.win_ia32\agent_controller\config\servicelog.log BTW, I don't really think this is a stop-ship problem, since there is a workaround for it. The workaround is simply to use the standalone AC. I don't really think IAC is suitable for the attach scenario anyways, since it doesn't expose its native files to the user and doesn't allow the user to explicity start it. Attaching to an agent is an advance usecase and the standalone AC should really be used to gain the control needed to do this. Using IAC in this scenario would defeat its purpose, since the user would have to find IAC's native files and include them in their PATH and they would have to somehow start IAC before lauching their agent.
I cannot reproduce the problem on a separate Vista machine. and the machine I used before is hold for build purpose now. As a result, I am going to close this bug as INVALID. Thanks Samson and Navid for your help on analyzing the problem here.
CLOSE BUG
