Bug 235753 - [dstore] Improve error message for connection timeout to REXEC server
Summary: [dstore] Improve error message for connection timeout to REXEC server
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 153246
  Show dependency tree
 
Reported: 2008-06-05 00:49 EDT by Masao Nishimoto CLA
Modified: 2011-09-27 03:23 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Masao Nishimoto CLA 2008-06-05 00:49:30 EDT
When connecting to the dstore server using a REXEC connection, if a connection timeout occurs, the following error message is shown:

Message: Unable to connect to REXEC host service on port 3512 of host xx
Detail: Message from host: yy

The actual message from host may be nothing or a part of output from the server, and is useless for a user.  Since the cause of the failure is a SocketTimeoutException, the message should indicate the timeout and ask a user to retry with the increased timeout value.
Comment 1 Martin Oberhuber CLA 2008-06-05 05:37:34 EDT
This is a concrete incarnation of a more generic problem already known as per bug 153246. I agree that the error reporting for dstore REXEC should be improved because it's currently very hard to diagnose problems.

Bug 194584 is also slightly related but refers to the message when a daemon is not running.
Comment 2 Martin Oberhuber CLA 2008-06-05 05:38:28 EDT
I think it's important to note that this does likely *not* require PII change but just a better way of forwarding the remote exception or error message into the Details page of the SystemMessage.
Comment 3 David McKnight CLA 2008-07-09 16:09:14 EDT
Setting milestone to 3.0.1 in case it's possible to deal with this without any PII.