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

Bug 144777

Summary:	Provide informational dialog when SWT/Mozilla is not configured correctly on non-Windows OSes.
Product:	z_Archived	Reporter:	Paul Slauenwhite <paulslau>
Component:	TPTP	Assignee:	Paul Slauenwhite <paulslau>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	paulslau
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Paul Slauenwhite

2006-05-31 16:47:25 EDT

Provide informational dialog when SWT/Mozilla is not configured correctly on non-Windows OSes.

Update the Manual Test Runner to return an error message to the launching
client workbench when launching the Manual Test view instructing the user of the follow issues and any possible solutions:

http://www.eclipse.org/tptp/home/downloads/releasenotes/releasenotes4_1_0.html#1_7_5 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=115104)

http://www.eclipse.org/tptp/home/downloads/releasenotes/releasenotes4_1_0.html#1_7_8 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=115648)

Comment 1 Paul Slauenwhite

2006-05-31 16:47:45 EDT

*** Bug 115104 has been marked as a duplicate of this bug. ***

Comment 2 Paul Slauenwhite

2006-09-19 07:39:07 EDT

Informational dialog (or [possibly runner's configuration) should contain the following:

The X Windows System is unable to use file descriptors above 
255. Because the JVM holds file descriptors for open jar files, X can run 
out of file descriptors. As a workaround, you can set the JAVA_HIGH_ZIPFDS environment variable to tell the JVM to use higher file 
descriptors for jar files. 

To use the JAVA_HIGH_ZIPFDS environment variable, set it to a value between 0 and 512. The JVM will 
then open the first jar files using file descriptors up to 1024. For example, 
if your program is likely to load 300 jar files:

export JAVA_HIGH_ZIPFDS=300 

The first 300 jar files will then be loaded using the file descriptors 
724 to 1023. Any jar files opened after that will be opened in the normal 
range.

[Source: https://bugs.eclipse.org/bugs/show_bug.cgi?id=106396 and http://www-128.ibm.com/developerworks/java/jdk/linux/50/sdkandruntimeguide.lnx.en.html]

In the context of the Agent Controller, the problem appears more often, because the Agent Controller (which creates the eclipse process) adds to the process stack its own set of open files. This is recognized as a X window system bug, and if you use an IBM JRE, the work-around is to set JAVA_HIGH_ZIPFDS to a value such as 500 (before launching the Agent Controller!).

Comment 3 Paul Slauenwhite

2006-10-20 16:08:39 EDT

Retargeting to 4.4 as decided in today's AG call (only permitting blocking and critical defects in 4.3 i3).

Comment 4 Paul Slauenwhite

2007-03-21 12:47:18 EDT

The fix for this defect will produce the necessary meaningful error messages.  However, error messages originating from any test runner are not displayed (e.g. dialog) to the launching client workbench.  This will be handled under defect #178595.

The following files checked-in to CVS (HEAD):

org.eclipse.tptp.test.manual.runner.core.internal.ManualTestRunner.java
org.eclipse.hyades.test.tools.core\src-manual-runner\manualRunner.properties

Comment 5 Paul Slauenwhite

2007-06-02 14:51:44 EDT

Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release.  Thanks.

Comment 6 Paul Slauenwhite

2007-06-27 14:51:47 EDT

Verified in TPTP-4.4.0-200706140100C.