Bug 98193 - Show appropriate message dialog when the RAC is not started appropriately when importing a log file with filter
Summary: Show appropriate message dialog when the RAC is not started appropriately whe...
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP.monitoring (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Terry Fountoulakis CLA
QA Contact:
URL:
Whiteboard: closed460
Keywords: PII, ui
Depends on:
Blocks:
 
Reported: 2005-06-02 17:40 EDT by Terry Fountoulakis CLA
Modified: 2010-06-03 15:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Terry Fountoulakis CLA 2005-06-02 17:40:25 EDT
Importing a log file with a filter results in an error if the RAC is not 
started properly.  We are logging the exception to the log file.  The exception 
is shown below.  This is related to defect 95615.

The RAC not started properly, refers to a RAC started without the 
LD_LIBRARY_PATH variable appropriately set on linux.

We may consider showing an error message such as "Server not available 
exception occured, the RAC may not have been started properly."  It may not be 
necessary to do this, as it may not happen regularly.  It's something to 
consider.

Below is the stack trace for the exception to point to where this is happening.

!ENTRY org.eclipse.hyades.ui 1 0 2005-06-02 17:03:39.47
!MESSAGE 
org.eclipse.hyades.internal.execution.core.file.ServerNotAvailableException: 
java.net.ConnectException: Connection refused: connect
!STACK 0
org.eclipse.hyades.internal.execution.core.file.ServerNotAvailableException: 
java.net.ConnectException: Connection refused: connect
	at 
org.eclipse.hyades.internal.execution.core.file.FileServerCommandFactory.connect
SocketChannel(FileServerCommandFactory.java:147)
	at 
org.eclipse.hyades.internal.execution.core.file.FileServerCommandFactory.createP
utFileCommand(FileServerCommandFactory.java:288)
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:325)
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:378)
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:351)
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:338)
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:388)
	at 
org.eclipse.tptp.monitoring.logui.internal.util.GLAFilterHelper.sendAdapter
(GLAFilterHelper.java:469)
	at 
org.eclipse.tptp.monitoring.logui.internal.util.GLAFilterHelper.addFilterToAdapt
er(GLAFilterHelper.java:226)
	at 
org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.importFromRem
oteHost(ImportLogWizard.java:1844)
	at 
org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.importLog
(ImportLogWizard.java:1771)
	at 
org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.run
(ImportLogWizard.java:261)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
	at 
org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.performFinish
(ImportLogWizard.java:187)
	at org.eclipse.jface.wizard.WizardDialog.finishPressed
(WizardDialog.java:676)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed
(WizardDialog.java:349)
Comment 1 Terry Fountoulakis CLA 2005-07-05 14:32:10 EDT
This problem occured, when I launched the RAC with the RAServer command instead 
of the RAStart.sh command.  This should not be called in this way on unix.  
Since this is unlikely to occur and only occurs when a filter is used, we won't 
fix it and be content that the log file prints a usefull stack trace which is 
indicative of the problem.

This defect is related to defect 95615, we printed the stack trace or exception 
in this case is more informative.  We see a connection exception which should 
signal that the RAC may not have been started correctly.

java.io.IOException: java.net.ConnectException: Connection refused: connect
	at 
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.putFile
(FileManagerExtendedImpl.java:413)
	at 
org.eclipse.tptp.monitoring.logui.internal.util.GLAFilterHelper.sendAdapter
(GLAFilterHelper.java:469)
Comment 2 Terry Fountoulakis CLA 2005-07-14 17:09:23 EDT
verified
Comment 3 Paul Slauenwhite CLA 2009-06-30 12:17:30 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 this enhancement/defect has been resolved and unverified for more than 1 year 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.