[esb-issues] [JBoss JIRA] Closed: (JBESB-2097) ServiceInvoker Exception details

Kevin Conner (JIRA) jira-events at lists.jboss.org
Wed Jul 1 10:10:51 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBESB-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner closed JBESB-2097.
-------------------------------

    Resolution: Done


The exceptions have now been clarified with MissingServiceException being thrown when EPRs cannot be found and ResponseTimeoutException thrown when the execution times out.  Both are subclasses of the MessageDeliverException exception so the signature remains unchanged.

Updated in revision 27386.

> ServiceInvoker Exception details
> --------------------------------
>
>                 Key: JBESB-2097
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2097
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.4
>            Reporter: Burr Sutter
>            Assignee: Kevin Conner
>             Fix For: 4.6
>
>
> Current the ServiceInvoker.deliverSync() method might throw the following exceptions:
> MessageDeliverException
> RegistryException
> FaultMessageException
> requestMessage = MessageFactory.getInstance().getMessage();    
> requestMessage.getProperties().setProperty(Environment.EXCEPTION_ON_DELIVERY_FAILURE,"true");        
> ServiceInvoker invoker = new ServiceInvoker("MyCategory", "Service99");
> replyMessage = invoker.deliverSync(requestMessage,2000);
> A service name which does not exist results in a MessageDeliverException, with the following information exposed via a
> System.err.println(mde);
> 11:25:16,179 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx
> ception: Failed to deliver message [header: [  ]] to Service [MyCategory:Servic
> e99].  Check for errors.
> It would have made more sense for it to be a RegistryException and the actual message doesn't indicate that there is a lookup problem.
> Futhermore, a timeout results in the following MessageDeliverException:
> 11:45:06,278 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx
> ception: Failed to deliver message [header: [ To: InVMEpr [ PortReference < <wsa
> :Address invm://52455354456173794553425365727669636531/false?false#10000/>, <wsa
> :ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jb
> ossesb:type : urn:jboss/esb/epr/type/invm/> > ] ReplyTo: InVMEpr [ PortReference
>  < <wsa:Address invm://thread-559/>, <wsa:ReferenceProperties jbossesb:passByVal
> ue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/in
> vm/> > ] ]] to Service [MyCategory:Service1].  Told not to retry.
> No indication that the problem is timeout and the "Told not to retry" is a bit terse.

-- 
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

        



More information about the esb-issues mailing list