0 Replies Latest reply on Mar 19, 2009 3:33 AM by Piotr Hrebieniuk

    exceptions_faults

    Piotr Hrebieniuk Newbie

      Hi there, I can't run exceptions_faults example properly. ant callSync2 works just fine, but if I run 'ant deploy' I get the message, that the faultTo isn't present in message (which shouldn't be a problem, as replyTo is set, as I assume) - stack error msg pasted at the bottom of this msg. Also, on my own ESB, in which action pipeline calls differs from this in callSync2 task only in that the ServiceInvoker is ran from inside of WebService body, i get the exact same msg.
      Here's output from 'ant runtest':

      08:32:34,402 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,422 INFO [STDOUT] MyBasicAction Body: Via Gateway |BASIC_ACTION|
      08:32:34,422 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,422 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,422 INFO [STDOUT] JustAnotherAction Body: Via Gateway |BASIC_ACTION| |JUST_ANOTHER_ACTION|
      08:32:34,422 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,422 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,422 INFO [STDOUT] MyExceptionHandlingAction Body: Via Gateway |BASIC_ACTION| |JUST_ANOTHER_ACTION| |EXCEPTI
      N_HANDLING|
      08:32:34,452 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,462 INFO [STDOUT] About to cause an exception
      08:32:34,462 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header:
      [ To: JMSEpr [ PortReference < <wsa:Address jms://10.7.23.44:1099/queue/quickstart_exceptions_faults_ESB/>, <wsa:Refere
      ceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties
      jbossesb:java.naming.provider.url : 10.7.23.44:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs :
      org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:s
      ecification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:Reference
      roperties jbossesb:message-selector : serviceName='ExceptionCaughtService'/>, <wsa:ReferenceProperties jbossesb:persist
      nt : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb
      transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 66c6cae2-067
      -49ba-b28f-43c2d7a8f9af RelatesTo: jms:correlationID#66c6cae2-0679-49ba-b28f-43c2d7a8f9af ]
      org.jboss.soa.esb.actions.ActionProcessingException: BAD STUFF HAPPENED
       at org.jboss.soa.esb.samples.quickstart.exceptions.MyBasicAction.causesException(MyBasicAction.java:53)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:
      02)
       at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProc
      ssor.java:74)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
       at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:5
      8)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      08:32:34,462 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,462 INFO [STDOUT] MyExceptionHandlingAction catchesException:
       Via Gateway |BASIC_ACTION| |JUST_ANOTHER_ACTION| |EXCEPTION_HANDLING|
      08:32:34,462 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,472 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,502 INFO [STDOUT] JustAnotherAction exceptionHandler:
       Via Gateway |BASIC_ACTION| |JUST_ANOTHER_ACTION| |EXCEPTION_HANDLING|
      08:32:34,502 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
      08:32:34,502 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference <
      wsa:Address jms://10.7.23.44:1099/queue/quickstart_exceptions_faults_ESB/>, <wsa:ReferenceProperties jbossesb:java.nami
      g.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.u
      l : 10.7.23.44:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:Refe
      enceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <w
      a:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-sele
      tor : serviceName='ExceptionCaughtService'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProp
      rties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:Refe
      enceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 66c6cae2-0679-49ba-b28f-43c2d7a8f9af Relates
      o: jms:correlationID#66c6cae2-0679-49ba-b28f-43c2d7a8f9af
      


      Hope you figure something out, as for now i just can't use the ActionProcessingFaultException, and have to force execusion to run through all actions, despite the fact that exception was thrown.
      Thanks!