112786 – Apply fix for 111106 to 3.1.x stream

Bug 112786 - Apply fix for 111106 to 3.1.x stream

Summary: Apply fix for 111106 to 3.1.x stream

Status:	VERIFIED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Runtime (show other bugs)
Version:	3.1
Hardware:	PC Windows 2000

Importance:	P3 normal (vote)
Target Milestone:	3.1.2
Assignee:	John Arthorne
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-10-17 10:07 EDT by John Arthorne
Modified:	2006-01-10 11:54 EST (History)
CC List:	5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description John Arthorne

2005-10-17 10:07:31 EDT

We have received a request to back-port the fix for 111106 into the 3.1.x
stream.  Once the fix has had some testing in the 3.2 stream, we will consider this.

Comment 1 Yen Lu

2005-10-25 11:43:27 EDT

Automated testing of our headless application appears to be consistently 
hanging due to this problem. Could you post a patch for Eclipse 3.1.1?

Comment 2 Tim deBoer

2005-10-27 14:24:18 EDT

Received another request for this fix.

Comment 3 John Arthorne

2005-10-27 16:05:09 EDT

Fix released to 3.1.x stream.

Comment 4 Yen Lu

2005-10-31 13:24:11 EST

John,

With some recent changes to dependencies in our stack, I now get the following 
message quite regularly. Do you know if this is related to 111106 and whether 
or not your fix will resolve this?

!ENTRY org.eclipse.core.runtime 2 2 2005-10-31 11:06:51.947
!MESSAGE Job found still running after platform shutdown.  Jobs should be 
cancel
ed by the plugin that scheduled them during shutdown: 
org.eclipse.core.internal.
utils.StringPoolJob

Comment 5 John Arthorne

2005-10-31 13:29:28 EST

Yes, the fix should stop that message. That message is mainly logged as a
warning to the plugin author that they should be cleaning up, and it doesn't in
itself represent a significant failure.

Comment 6 Bala Balakumran

2005-11-01 10:56:11 EST

Would not that become a significant falure if a shutdown hook is used
when shutting down the workbench?  The jvm will be prevented from
shutting down?

Comment 7 John Arthorne

2005-11-01 11:31:42 EST

When you say "shutdown hook", are you referring to
java.lang.Runtime#addShutdownHook(Thread)?  I don't see any connection...

Comment 8 John Arthorne

2006-01-10 11:41:46 EST

Yen Lu, the Eclipse 3.1.2 release candidate is now available (M20060109-1200). Would it be possible for you to verify the fix in that build?  I will also be doing independent verification, but want to ensure it solves your particular problem.

Comment 9 John Arthorne

2006-01-10 11:54:00 EST

Verified fixed code is in M20060109-1200