Hi all,

Found the solution for particular issue. Error indicating about failing to
connect deactivate sequence.



* WARN - ForwardingService Failed to send the message through the
deactivate sequence. Sequence name does not Exist.*
According to configuration, after maximum delivery attempts, it will find
the deactivate sequence. But in this scenario, "Deactivate sequence" not
given.

So Configured "Drop message after maximum delivery attempts" as "Enabled".

This redelivery process going on because of back-end service is not alive
or processor can't find endpoint.

In this scenario, it was given direct endpoint (
http://127.0.0.1:9000/services/SimpleStockQuoteService) rather than giving
previously created endpoint. So it also cause for the issue.

Configuring those parameters, solved the issue. Hope this will be helpful
to someone.

Regards,
Dilshani.


On Thu, Mar 10, 2016 at 8:14 AM, Dilshani Subasinghe <[email protected]>
wrote:

> Hi ESB Team,
>
> When I am configuring Store mediator, I created an On Store Sequence.
>
>
>
> *<sequence name="onstoreSeq" xmlns="http://ws.apache.org/ns/synapse
> <http://ws.apache.org/ns/synapse>">    <axis2ns17:store messageStore="reg"
> sequence="conf:/registrySeq"
> xmlns:axis2ns17="http://ws.apache.org/ns/synapse
> <http://ws.apache.org/ns/synapse>"/></sequence>*
>
> Then I created another sequence with a store mediator (Store mediator used
> On Store Sequence)
>
>
>
>
>
> *<sequence name="onstoreSeq">        <store messageStore="reg"
> sequence="conf:/registrySeq"/> </sequence> *
> Created a proxy and invoked it using axis2Client.
>
>
>
>
> *<proxy name="regProxy" startOnLoad="true" trace="disable"
> transports="http https">        <description/>        <target
> inSequence="onstoreSeq"/>    </proxy>*
>
> Then I tried to add a Scheduled Message Forwarding Processor to send
> messages in the message store. As I used Store mediator through On Store
> Sequence, processor will automatically deactivate:
>
>
>
>
>
>
>
>
>
>
>
>
>
> *ForwardingService Deactivating the message processor
> [storeProce]java.lang.NullPointerException    at
> org.apache.synapse.message.processor.impl.forwarder.ForwardingService.dispatch(ForwardingService.java:431)
> at
> org.apache.synapse.message.processor.impl.forwarder.ForwardingService.execute(ForwardingService.java:204)
> at
> org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:90)
> at
> org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)    at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)    at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)[2016-03-09 23:58:51,712]  WARN -
> ForwardingService Failed to send the message through the deactivate
> sequence. Sequence name does not Exist.*
>
>
> *Issue*: Can we implement message processor which have connection to On
> Store Sequence as it not including in synapse ? Why message processor do
> not identify On Store Sequence?
>
> Any clarification on this ? Any help will be highly appreciated.
>
> PS: Attached Synapse Configuration XML.
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware

Mobile: +94773375185
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to