incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Closed: (YOKO-231) Connection errors on inbound requests go unreported.
Date Thu, 12 Jul 2007 18:43:05 GMT

     [ https://issues.apache.org/jira/browse/YOKO-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick McGuire closed YOKO-231.
-----------------------------

    Resolution: Cannot Reproduce

This was really resolved by changes for YOKO-401.

> Connection errors on inbound requests go unreported.
> ----------------------------------------------------
>
>                 Key: YOKO-231
>                 URL: https://issues.apache.org/jira/browse/YOKO-231
>             Project: Yoko - CORBA Server
>          Issue Type: Bug
>          Components: orb core
>    Affects Versions: v1.0-incubating-M2
>            Reporter: Rick McGuire
>            Assignee: Rick McGuire
>             Fix For: v1.0.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message