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

Bug 199237

Summary: [Java 6] Test execution stalls at 36%.
Product: z_Archived Reporter: Paul Slauenwhite <paulslau>
Component: TPTPAssignee: DuWayne Morris <dmorris>
Status: CLOSED WORKSFORME QA Contact:
Severity: major    
Priority: P1 CC: etiennel, jkubasta
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 200535    
Attachments:
Description Flags
Screen capture. none

Description Paul Slauenwhite CLA 2007-08-08 07:29:05 EDT 
[Java 6] Test execution stalls at 36%.

When using TPTP 4.4.0.1/Java 6, launching a 'Hello World' JUnit test stalls at 36% and eventually throws the following errors:

!ENTRY org.eclipse.hyades.test.core 1 0 2007-08-08 08:27:38.000
!MESSAGE org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
!STACK 0
org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
	at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.hyades.test.core 1 0 2007-08-08 08:27:38.015
!MESSAGE java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
!STACK 0
java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
	at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.handleException(TestExecutionHarnessExecutorStub.java:347)
	at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:434)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830)
	at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
	at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422)
	... 4 more

!ENTRY org.eclipse.hyades.test.core 4 0 2007-08-08 08:27:38.125
!MESSAGE IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException
Comment 1 Paul Slauenwhite CLA 2007-08-08 07:29:22 EDT 
Created attachment 75657 [details]
Screen capture.
Comment 2 Paul Slauenwhite CLA 2007-08-13 08:29:36 EDT 
I would assume we will start supporting Java 6 in 4.5.

Joe, please provide a sizing.
Comment 3 Joe Toomey CLA 2007-08-13 08:39:49 EDT 
I really think this should be part of an enhancement request.  Supporting 1.6 is more than just fixing a defect.  It also has a huge impact in expanding our testing effort.  I hope we will evaluate dropping 1.4 at the same time we begin supporting 1.6.

I agree that 4.5 would be a good release for this, as we are barraged by message board posts from people who fail using 1.6.  The demand is there, but we need to either get more staffing, drop other work, or drop another environment in order to support this.  Paul -- can you raise this with the PMC?

The sizing I'm adding is completely wet-finger-in-the-wind.  It may go up or down once I've had a chance to investigate why we're failing.
Comment 4 Paul Slauenwhite CLA 2007-08-20 08:45:28 EDT 
(In reply to comment #3)
> I really think this should be part of an enhancement request.  Supporting 1.6
> is more than just fixing a defect.  It also has a huge impact in expanding our
> testing effort.  I hope we will evaluate dropping 1.4 at the same time we begin
> supporting 1.6.
> 
> I agree that 4.5 would be a good release for this, as we are barraged by
> message board posts from people who fail using 1.6.  The demand is there, but
> we need to either get more staffing, drop other work, or drop another
> environment in order to support this.  Paul -- can you raise this with the PMC?
> 
> The sizing I'm adding is completely wet-finger-in-the-wind.  It may go up or
> down once I've had a chance to investigate why we're failing.
> 

I have opened enhancement 200535 that we will discuss with the PMC as part of our 4.5 planning/staffing discussion.
Comment 5 Paul Slauenwhite CLA 2007-10-15 13:06:32 EDT 
Duwayne, can you investigate.
Comment 6 DuWayne Morris CLA 2007-10-17 14:24:54 EDT 
I was able to execute JUnit and URL tests with no issues with both the AC and the IAC using the latest pre-release 1.6 IBM JVM that I found on Windows XP with the 4.4.0.3 TPTP driver.

Perhaps there was an issue that has been resolved in the AC since the 4.4.0.1 driver or there were changes in the JVM.  I am using the JVM dated Aug 19, 2007.
Comment 7 Paul Slauenwhite CLA 2007-10-17 15:16:34 EDT 
There have been two others users on the news group seeing the same symptoms.  I will ask them to provide their configuration.
Comment 8 Paul Slauenwhite CLA 2007-10-23 13:32:45 EDT 
(In reply to comment #7)
> There have been two others users on the news group seeing the same symptoms.  I
> will ask them to provide their configuration.
> 

No responses to date.  Closing defect as WORKSFORME.
Comment 9 Paul Slauenwhite CLA 2007-11-07 06:22:30 EST 
Bulk update of the target field to reflect the change in iteration numbers.
Comment 10 Paul Slauenwhite CLA 2007-11-07 06:29:43 EST 
Bulk update of the target field to reflect the change in iteration numbers.
Comment 11 Paul Slauenwhite CLA 2007-11-20 14:15:47 EST 
Closing.