You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2009/05/07 16:18:30 UTC
[jira] Updated: (WSCOMMONS-465) Error Handling Logic in
JMSConnectionConnectionFactoryManager is Wrong and Causes NPE
[ https://issues.apache.org/jira/browse/WSCOMMONS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated WSCOMMONS-465:
------------------------------------------
Attachment: WSCOMMONS-465.patch
Attaching fix for the reported issue. This males sure that no NPE is thrown and the original exception is properly logged.
> Error Handling Logic in JMSConnectionConnectionFactoryManager is Wrong and Causes NPE
> -------------------------------------------------------------------------------------
>
> Key: WSCOMMONS-465
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-465
> Project: WS-Commons
> Issue Type: Bug
> Components: Transport
> Affects Versions: Transports 1.0
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Attachments: WSCOMMONS-465.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> Exception handling logic in the JMSConnectionFactoryManager#loadConnectionFactoryDefinitions is wrong. It causes an NPE to be thrown whenever the initialization of the JMSConnectionFactory thus suppressing the original exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.