Connection errors on inbound requests go unreported.
----------------------------------------------------
Key: YOKO-231
URL: http://issues.apache.org/jira/browse/YOKO-231
Project: Yoko - CORBA Server
Issue Type: Bug
Components: orb core
Affects Versions: 1.0-incubating-M2
Reporter: Rick McGuire
Assigned To: Rick McGuire
Fix For: 1.0-incubating-M2
On inbound requests, errors with the connection are getting turned into CORBA
system exceptions and queued for processing by sending them back with the
request reply. Unfortunately, the connection error causes the connection to be
severed and the exception is never passed back to the client. The client
receives a generic "COMM FAILURE" error, and the server doesn't reflect the
underlying cause of the error.
This is a major usability concern. In trying to get the Geronimo TCK to run, I
was receiving these COMM FAILURES on the client, and it took two days of
intensive debugging of the yoko code to discover that the underlying problem
was an SSL handshaking problem caused by a truststore setup problem. If the
initial IOException and stack trace had been displayed or logged on the server,
two days worth of time could have been saved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
