[jboss-jira] [JBoss JIRA] Closed: (JBREM-1088) MicroSocketClientInvoker(InvokerLocator locator, Map configuration) ctor - not propagating exceptions (only message is wrapped)
[
https://jira.jboss.org/jira/browse/JBREM-1088?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1088.
----------------------------
Resolution: Done
Changed
throw new RuntimeException(ex.getMessage());
to
throw new RuntimeException(ex.getMessage(), ex);
on 2.2 and 2.x branches.
MicroSocketClientInvoker(InvokerLocator locator, Map configuration)
ctor - not propagating exceptions (only message is wrapped)
-------------------------------------------------------------------------------------------------------------------------------
Key: JBREM-1088
URL: https://jira.jboss.org/jira/browse/JBREM-1088
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
Environment: Windows
Reporter: Developer JBoss
Assignee: Ron Sigal
Priority: Minor
Fix For: 2.5.1 (Flounder), 2.2.2.SP12
During org.jboss.remoting.Client.connect() call, if server "hostname" DNS
mapping is not available at client,
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.setup() getAddressByName
throws :
java.net.UnknownHostException: <hostname>
However, calling method:
org.jboss.remoting.transport.socket.MicroSocketClientInvoker(InvokerLocator locator, Map
configuration) catches this exception and wraps it as new
RuntimeException(ex.getMessage()). This looses rootcause exception stack. It is difficult
for caller client code to understand the cause of the exception (UnknownHostException).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira