[infinispan-issues] [JBoss JIRA] Issue Comment Edited: (ISPN-1238) Root cause of exceptions thrown by custom JGroupsTransportLookup getting swallowed

Paul Ferraro (JIRA) jira-events at lists.jboss.org
Thu Jul 14 17:45:23 EDT 2011


    [ https://issues.jboss.org/browse/ISPN-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614268#comment-12614268 ] 

Paul Ferraro edited comment on ISPN-1238 at 7/14/11 5:44 PM:
-------------------------------------------------------------

Actually, it would make more sense if buildChannel() threw an exception.  If I'm explicitly trying to supply a channel, using the default one is generally not an appropriate course of action.

      was (Author: pferraro):
    Actually, it would make more sense if buildChannel() threw an exception.  If I'm explicitly trying to supply a channel, using the default one generally not an appropriate course of action.
  
> Root cause of exceptions thrown by custom JGroupsTransportLookup getting swallowed
> ----------------------------------------------------------------------------------
>
>                 Key: ISPN-1238
>                 URL: https://issues.jboss.org/browse/ISPN-1238
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core API
>    Affects Versions: 5.0.0.CR7
>            Reporter: Paul Ferraro
>            Assignee: Dan Berindei
>             Fix For: 5.0.0.FINAL
>
>
> AS7 uses a custom JGroupsTransportLookup so the jgroups channel is created from the jgroups subsystem.  If channel creation throws an exception (i.e. during JGroupsTransportLookup.getJGroupsChannel(...)), the details are lost due to the exception handling in JGroupsTransport.buildChannel().
> The root cause should be logged.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the infinispan-issues mailing list