Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 196461

Summary:	'Attach to Agent' Profile to Linux machine w/ security enabled does not return available agents
Product:	z_Archived	Reporter:	Kendric Wang <kendricw>
Component:	TPTP	Assignee:	Jonathan West <jgwest>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	jkubasta, xubing
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Kendric Wang

2007-07-13 10:23:52 EDT

Build ID: I20070625-1500

Steps To Reproduce:
1. Setup RAC on Linux machine using Java142 (for piagent).
2. Start ACServer with security enabled.
3. Start java process (InOut class) in controlled mode on the Linux machine:
java -classpath . -XrunpiAgent:server=controlled InOut
4. Create an 'Attach to Agent' profile from workbench on Windows.
5. Specify host and test connection.
6. Click on 'Agents' tab. Refresh. I see the following error message:
"Error retrieving running agents - see log for more details"
7. When I check off the error message and click on 'Refresh', it does return all Java Profiling agents, but the error seen above as well.
8. I try to profile with the 'Basic Memory Analysis' and 'Execution Time Analysis' agents. The progress bar remains at 27% for half a minute, then a security window pops up and prompts for the linux machine's user/password. After entering this information and clicking 'OK', the 'Attach to Agents' profile configuration window pops up again showing the error message from before.

*Note: remote Attach to Agent profiling DOES WORK with security disabled

More information:
TPTP Build - 4.4.0.1-200707090100
Workbench on WindowsXP
Remote machine - blackhawk-sles9
JVM on Linux machine - J2RE 1.4.2 IBM build cxia32142-20070321 (SR8) (JIT enabled: jitc)

Comment 1 Jonathan West

2007-11-05 14:42:46 EST

Unable to reproduce the bug with Java 1.4.2, TPTP 4.4.0.3, and Eclipse 3.3.1. I suspect it was fixed indirectly by the security patches that went into 4.4.0.1 and 4.4.0.2.

But I'm still glad we submitted it Kendric, because this is an annoying one not to catch (and note) from the users perspective ;).

Comment 2 Paul Slauenwhite

2007-12-19 07:58:59 EST

Please change the target to the 4.5 iteration when this Bugzilla was resolved.

Comment 3 Joel Cayne

2008-07-31 16:40:49 EDT

Closing.