3 Replies Latest reply: Jan 7, 2009 1:57 PM by Jeff DeLong RSS

Problems with overlord-cdl-1.0-M1 Purchasing example

Jeff DeLong Master

I had two problems;

1) Conformance checking in IDE

I followed the instructions in the SamplesGuide 3.1 1 - 4, but did not result in an error being generated, complaining about a type mismatch.

2) Running the example

I saw the following exception in the console:

org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:137)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.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:530)
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)
Caused by: java.lang.Exception: Error in process message: java.lang.Exception: Haven't found the decision method in the configuration.
at org.jboss.soa.overlord.jbossesb.actions.ConversationAction.process(ConversationAction.java:215)
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:102)
... 6 more
Caused by: java.lang.Exception: Haven't found the decision method in the configuration.
at org.jboss.soa.overlord.jbossesb.actions.IfAction.handle(IfAction.java:82)
at org.jboss.soa.overlord.jbossesb.actions.ConversationAction.process(ConversationAction.java:197)
... 11 more
22:08:38,311 INFO [SendMessageAction] Sent message to 'PurchaseGoods.CreditAgency/CreditAgency.main'
22:08:38,311 INFO [SendMessageAction] MESSAGE TYPE 'CreditCheckRequest' SENT.
22:08:38,318 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/esb-creditAgency/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: EPR: PortReference < <wsa:Address logical:PurchaseGoods.Store#CreditResponse/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > MessageID: 8673fd5b-c916-4c46-8d9a-1addee82ebd7 RelatesTo: jms:correlationID#8673fd5b-c916-4c46-8d9a-1addee82ebd7
22:08:38,406 WARN [ActionProcessingPipeline] Failed to send response failure to DLQ service

Thanks,

Jeff

  • 1. Re: Problems with overlord-cdl-1.0-M1 Purchasing example
    Jeff Yu Master

    Hi Jeff,

    For the 2nd issue, see through the error stack, it means that in the jboss-esb.xml,

    <if expression="isCreditValid()" immediate="true" service-category="PurchaseGoods.CreditAgency" service-name="CreditAgency.decision1"/>
    


    I guess the expression's value is not correct in your case, so that the method cant be found in its business pojo class, which is CreditAgencyPurchase.java in this case.

    And I think the 1st error you see it means the expression wasn't written correctly.

    Thanks
    Jeff Yu

  • 2. Re: Problems with overlord-cdl-1.0-M1 Purchasing example
    Gary Brown Master

    Hi Jeff

    In terms of the first problem - could you send me the Configuration Details from the Help->About Eclipse SDK. Just want to check that all the appropriate plugins are installed and active.

    Regards
    Gary

  • 3. Re: Problems with overlord-cdl-1.0-M1 Purchasing example
    Jeff DeLong Master

    Gary pointed out that I did he org.jboss.tools.overlord.cdl.* plugins in my
    environment. This explains the fact that the jboss-esb.xml
    files are not being validated.

    Once I setup a local update site, pointing to the overlord distribution's tools folder - and then import the overlord.cdl features, the conformance checking worked as described in the SamplesGuide.