Bug 187218 - SystemMessageException printed to stdout for failures during connect
Summary: SystemMessageException printed to stdout for failures during connect
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 183824
  Show dependency tree
 
Reported: 2007-05-16 05:40 EDT by Sheldon CLA
Modified: 2008-08-13 13:18 EDT (History)
0 users

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 Sheldon CLA 2007-05-16 05:40:22 EDT 
Whenever a system message exception is thrown as a result of incorrect login to e.g telnet or ssh a dialog does not pop up, instead the exception is printed to stdout.

Create a connection to telnet or ssh and enter wrong password when login information is asked, continue entering the wrong password till the login session times out. Instead of a dialog popping up, the exception details are written to stdout check console.
Comment 1 Martin Oberhuber CLA 2007-05-16 11:46:26 EDT 
Fixed in ConnectorService, SubSystem, and the Actions calling connect() in there.
In line with the changes made for bug #183824, API is now specified to throw exception in case of failure, clients are responsible for handling it.

Changeset:
[187218] Fix error reporting for connect()
Comment 2 Martin Oberhuber CLA 2008-08-13 13:18:40 EDT 
[target cleanup] 2.0 M7 was the original target milestone for this bug