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

Bug 187133

Summary:

Remote Profiles only allow one to two consecutive attempts without timing out

Product:

z_Archived

Reporter:

Liz Dancy <lizdancy>

Component:

TPTP

Assignee:

Igor Alelekov <igor.alelekov>

Status:

CLOSED WORKSFORME

QA Contact:

Severity:

major

Priority:

CC:

amehrega, analexee, jkubasta, nmehrega

Version:

unspecified

Keywords:

plan

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

closed460

Attachments:

Description	Flags
StartStop	none

Description Liz Dancy

2007-05-15 17:26:13 EDT

I have noticed with the JVMTI profile specifically (all analysis types) that repeated remote profiles from Windows ia32 to Windows ia32 will time out on the second or third attempt consistently. Most of the time the second attempt will just hang at 51% in the local UI.


Occasionally, when you get to the third attempt, it will declare an error message indicating that the launch timed out. There are usually one or more Java processes hanging around on the remote machine.

This seems to be brought on by applications that wait such as StartStop. Please used attached class file to reproduce.

Comment 1 Liz Dancy

2007-05-15 17:26:55 EDT

Created attachment 67324 [details]
StartStop

StartStop class is attached. Try a remote profile from Windows -> Windows with StartStop as the External Java Application.

Comment 2 Navid Mehregani

2007-05-16 17:23:11 EDT

Note that this defect can be duplicate of bug 186003.

Comment 3 Liz Dancy

2007-05-17 13:56:08 EDT

I don't think this is a duplicate of 186003 as this is not related to AGR testing. This defect happens when launching remote profiles manually.

Comment 4 Navid Mehregani

2007-05-17 14:27:30 EDT

Liz, I believe they both get stuck in the same place of the execution framework.

Comment 5 jkubasta

2007-05-28 12:37:06 EDT

defer given workaround

Comment 6 Ruslan Scherbakov

2007-06-13 04:21:43 EDT

Transitioning future work to the right person.

Comment 7 Liz Dancy

2007-06-15 17:00:18 EDT

I am finding the data very inconsistent for numerous remote profiles with JVMTI. I am going to open a readMe for 4.4 and hopefully this can be addressed as a priority in the next release. This prevents the remote JVMTI probekit test suite from completing with AGR. Manual execution is necessary because of the need to restart the agent controller to get data each time when profiling consecutively.

Comment 8 Guru Nagarajan

2007-06-20 19:32:00 EDT

Cannot be contained in 4.4.0.1

Comment 9 Harm Sluiman

2007-06-20 21:52:09 EDT

(In reply to comment #8)
> Cannot be contained in 4.4.0.1

Let su track this as a candidate 4.4.0.1 until we have determined the 4.4.0.1 plan. If not containable, what is the size of the effort and alternatives.

Comment 10 Igor Alelekov

2008-03-07 03:11:53 EST

I can't reproduce this defect.
Anyone is able to do this?

Comment 11 Igor Alelekov

2008-03-07 03:12:28 EST

I used TPTP 4.5 M5 build.

Comment 12 Igor Alelekov

2008-03-13 06:34:03 EDT

Resolving as "works for me"

Comment 13 Paul Slauenwhite

2009-06-30 10:31:02 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since the originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.