[mule-user] Posting message back to the queue

3 views
Skip to first unread message

Mohit Anchlia

unread,
Sep 20, 2011, 5:59:16 PM9/20/11
to us...@mule.codehaus.org
I have this flow and on error from http (ReplicationHttpFlow) service
I want to post the message that I retrieved from the queue back on the
queue (replicator.queue). Is there a way it can be done?

<flow name="replicatorManager">
<jms:inbound-endoint queue="replicator.queue">
</jms:inbound-endoint>
<component class="com.i.cg.services.d.ds.replication.ReplicationListener" />
<flow-ref name="ReplicationHttpFlow" />
</flow>

<flow name="ReplicationHttpFlow">
<logger message="In http flow" level="INFO" />
<logger level="INFO" />
<http:outbound-endoint address="http://localhost:8084#[header:http.request]">
</http:outbound-endoint>
<!-- <logger message="Replication #[payload] is an XML message!"
level="INFO" />
--> </flow>

<flow name="bridgeSimulator">
<inbound-endoint address="http://localhost:8084/" />
<logger message="Inside Simulator " level="INFO" />
<logger level="INFO" />
<jersey:resources>
<component
class="com.i.cg.services.d.ds.api.DocumentResourceTestImpl" />
</jersey:resources>
</flow>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email


Magnus Larsson

unread,
Sep 21, 2011, 3:16:12 AM9/21/11
to us...@mule.codehaus.org
Hello!

The default handling of this requirement is, to me, to use jms-transactions that span the http-outbound-endpoint.

Any error during the http-outbound-endpoint processing will cause the jms-transaction to rollback.

Given a proper retry configuration of the JMS provider the messages can typically be retried a couple of times with a proper wait-time between the retries by the JMS provider and finally sent to a deadletter queue if all retries failed.

You would most probably as well set up some kind of alarm on the deadletter queues for detected of messages that ended up there.

If you want to know more details I recommend start reading at http://www.mulesoft.org/documentation/display/MULE3USER/Transaction+Management.

Regards,
Magnus.

Mohit Anchlia

unread,
Sep 21, 2011, 1:22:41 PM9/21/11
to us...@mule.codehaus.org
In this flow if I add <jms:transaction action="ALWAYS_BEGIN" /> I get

Below are errors and snippet of the flow

And this is happening in http:outbound endpoint:

<flow name="Replication">
<async>
<jms:outbound-endoint queue="replicator.queue"
exchange-pattern="one-way">
<jms:transaction action="ALWAYS_BEGIN" />
</jms:outbound-endoint>
</async>
</flow>


<flow name="replicatorManager">
<jms:inbound-endoint queue="replicator.queue">

<jms:transaction action="BEGIN_OR_JOIN" />


</jms:inbound-endoint>
<component
class="com.i.cg.services.d.ds.replication.ReplicationListener" />
<flow-ref name="ReplicationHttpFlow" />

<flow-ref name="VmEndoint" />
</flow>

<flow name="VmEndoint">
<vm:outbound-endoint path="replicator.work"
connector-ref="asynchVm">
</vm:outbound-endoint>
</flow>

<flow name="ReplicationHttpFlow">
<logger message="In http flow" level="INFO" />
<logger level="INFO" />
<http:outbound-endoint address="http://localhost:8084#[header:http.request]">

<response>
<object-to-byte-array-transformer />
<object-to-string-transformer />
<transformer ref="HttpResponseTransformer" />
</response>
</http:outbound-endoint>
</flow>

10:07:03,420 ERROR DefaultServiceExceptionStrategy:263 -
********************************************************************************
Message : A transaction is available for this session,
but transaction action is "Never"
Code : MULE_ERROR-91403
--------------------------------------------------------------------------------
Exception stack is:
1. A transaction is available for this session, but transaction action
is "Never" (org.mule.transaction.IllegalTransactionStateException)
org.mule.transaction.TransactionTemplate:71
(http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/transaction/IllegalTransactionStateException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
org.mule.transaction.IllegalTransactionStateException: A transaction
is available for this session, but transaction action is "Never"
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:71)
at org.mule.processor.TransactionalInterceptingMessageProcessor.process(TransactionalInterceptingMessageProcessor.java:55)
at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:41)
+ 3 more (set debug level logging or
'-Dmule.verbose.exceptions=true' for everything)
********************************************************************************

Magnus Larsson

unread,
Sep 21, 2011, 2:13:13 PM9/21/11
to us...@mule.codehaus.org
Hello again!

May I suggest that you start with simplifying the solution by refactoring it to one flow with one jms-inbound endpoint and one http-outbound endpoint
and set <jms:transaction action="ALWAYS_BEGIN"/> on the inbound-endpoint 
and set <jms:transaction action="ALWAYS_JOIN"/> on the outbound-endpoint.

That should really work, we have used such constructs in many places at several customers!

After you got that working you can step-by-step refactor back to a more complex flow-design (if you really need it) and see where you get problem with "org.mule.transaction.IllegalTransactionStateException: A transaction is available for this session, but transaction action is "Never"" again. 
It is probably caused by an endpoint where you have forgotten to specify transaction-action and where Mule defaults to NEVER wich obviously doesn't work in this case :-)

Ok?

Regards,
Magnus.

Mohit Anchlia

unread,
Sep 21, 2011, 2:20:10 PM9/21/11
to us...@mule.codehaus.org
Yes it is http:outbound where I don't have it specified. But how do I
specify transaction on http:outbound? I tried http:transaction,
jms:transaction but it doesn't work.

On Wed, Sep 21, 2011 at 11:13 AM, Magnus Larsson

Magnus Larsson

unread,
Sep 21, 2011, 2:38:50 PM9/21/11
to us...@mule.codehaus.org
Sorry to here!

Below is a sample usage based on a real customer case where we call a soap-web service based on incoming jms-messages using jms-transactions to ensure that we don't loose any messages if we run into problems when calling the web-service:

Customer specific detailes removed.

<flow name="sample-service">
        <inbound-endpoint 
            address="jms://${IN_QUEUE}" 
            exchange-pattern="request-response">
            <jms:transaction action="ALWAYS_BEGIN" />
        </inbound-endpoint>

    <cxf:jaxws-client 
        wsdlLocation="classpath:/...wsdl"
        port="ServiceSoap" 
        operation="SendMessage"
        clientClass="...Service"
    />
    <outbound-endpoint address="${URL}" exchange-pattern="request-response">
        <jms:transaction action="ALWAYS_JOIN" />
    </outbound-endpoint>
</flow>

Hope it helps!

Regards,
Magnus.

Mohit Anchlia

unread,
Sep 21, 2011, 2:43:16 PM9/21/11
to us...@mule.codehaus.org
Thanks! how do I specify for this flow? jms:transaction fails

<http:outbound-endpoint address="http://localhost:8084#[header:http.request]">


<response>
<object-to-byte-array-transformer />
<object-to-string-transformer />
<transformer ref="HttpResponseTransformer" />
</response>

</http:outbound-endpoint>

On Wed, Sep 21, 2011 at 11:38 AM, Magnus Larsson

Magnus Larsson

unread,
Sep 21, 2011, 2:52:24 PM9/21/11
to us...@mule.codehaus.org
I have no clue, it seems to be very similar to my outbound-endpoint so it should really work...
I'm on Mule 3.1.2 by the way in this case.

I guess that you have tried with specifying <jms:transaction action="ALWAYS_JOIN" /> in the <http:outbound-endpoint> element?

Maybe you can try removing the http-prefix on the endpoint-endpoint to see it that changes anything (I can't see why it should but...)
Also you can try remove the response-element to see if anything changes (again I guess not...)

Otherwise it seems to me like a mystery to me why the construct we have used doesn't work for you...

Regards,
Magnus.

Mohit Anchlia

unread,
Sep 21, 2011, 3:10:56 PM9/21/11
to us...@mule.codehaus.org
Sorry I think I gave incorrect error that is when I didn't have
jms:transaction. With jms:transaction I get:


<flow name="ReplicationHttpFlow">
<logger message="In http flow" level="INFO" />
<logger level="INFO" />

<http:outbound-endpoint address="http://localhost:8084#[header:http.request]">

<jms:transaction action="ALWAYS_JOIN" />

<response>
<object-to-byte-array-transformer />
<object-to-string-transformer />
<transformer ref="HttpResponseTransformer" />
</response>
</http:outbound-endpoint>

</flow>

================================================================================
= Testing: testCreateBridgeApi =
================================================================================
12:06:23,137 INFO AbstractLifecycleManager:55 - Initialising RegistryBroker
12:06:23,215 INFO MuleApplicationContext:456 - Refreshing
org.mule.config.spring.MuleApplicationContext@5f8172: startup date
[Wed Sep 21 12:06:23 PDT 2011]; root of context hierarchy
12:06:23,293 INFO XmlBeanDefinitionReader:315 - Loading XML bean
definitions from URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/mule-spring-config.xml]
12:06:23,403 INFO XmlBeanDefinitionReader:315 - Loading XML bean
definitions from URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]
12:06:23,762 INFO DefaultListableBeanFactory:612 - Overriding bean
definition for bean '_muleConfiguration': replacing [Generic bean:
class [org.mule.config.spring.MuleConfigurationConfigurator]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
with [Generic bean: class
[org.mule.config.spring.MuleConfigurationConfigurator]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
12:06:23,762 INFO DefaultListableBeanFactory:612 - Overriding bean
definition for bean '_muleConfiguration': replacing [Generic bean:
class [org.mule.config.spring.MuleConfigurationConfigurator]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
with [Generic bean: class
[org.mule.config.spring.MuleConfigurationConfigurator]; scope=;
abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
12:06:23,762 INFO DefaultListableBeanFactory:612 - Overriding bean
definition for bean '_muleNotificationManager': replacing [Generic
bean: class [org.mule.config.spring.ServerNotificationManagerConfigurator];
scope=; abstract=false; lazyInit=false; autowireMode=0;
dependencyCheck=0; autowireCandidate=true; primary=false;
factoryBeanName=null; factoryMethodName=null;
initMethodName=initialise; destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
with [Generic bean: class
[org.mule.config.spring.ServerNotificationManagerConfigurator];
scope=; abstract=false; lazyInit=false; autowireMode=0;
dependencyCheck=0; autowireCandidate=true; primary=false;
factoryBeanName=null; factoryMethodName=null;
initMethodName=initialise; destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
12:06:23,762 INFO DefaultListableBeanFactory:612 - Overriding bean
definition for bean '_muleNotificationManager': replacing [Generic
bean: class [org.mule.config.spring.ServerNotificationManagerConfigurator];
scope=; abstract=false; lazyInit=false; autowireMode=0;
dependencyCheck=0; autowireCandidate=true; primary=false;
factoryBeanName=null; factoryMethodName=null;
initMethodName=initialise; destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
with [Generic bean: class
[org.mule.config.spring.ServerNotificationManagerConfigurator];
scope=; abstract=false; lazyInit=false; autowireMode=0;
dependencyCheck=0; autowireCandidate=true; primary=false;
factoryBeanName=null; factoryMethodName=null;
initMethodName=initialise; destroyMethodName=null; defined in URL
[jar:file:/C:/Documents%20and%20Settings/manchlia/.m2/repository/org/mule/modules/mule-module-spring-config/3.1.2/mule-module-spring-config-3.1.2.jar!/default-mule-config.xml]]
12:06:23,778 INFO DefaultListableBeanFactory:612 - Overriding bean
definition for bean '_muleSystemModel': replacing [Root bean: class
[org.mule.model.seda.SedaModel]; scope=singleton; abstract=false;
lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=dispose] with [Root bean: class
[org.mule.model.seda.SedaModel]; scope=singleton; abstract=false;
lazyInit=false; autowireMode=0; dependencyCheck=0;
autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=initialise;
destroyMethodName=dispose]
12:06:23,778 INFO XmlBeanDefinitionReader:315 - Loading XML bean
definitions from URL
[file:/C:/upb/dp/manchlia-dp/depot/services/data-platform/trunk/dp-pipeline/app-bridge/target/test-classes/mule-config-ut.xml]
12:06:23,903 ERROR SpringXmlConfigurationBuilder:53 - Configuration
with "org.mule.config.spring.SpringXmlConfigurationBuilder" failed.
org.mule.api.lifecycle.InitialisationException: Line 171 in XML
document from URL
[file:/C:/upb/dp/manchlia-dp/depot/services/data-platform/trunk/dp-pipeline/app-bridge/target/test-classes/mule-config-ut.xml]
is invalid; nested exception is org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'response'. One of
'{"http://www.mulesoft.org/schema/mule/core":abstract-reconnection-strategy,
"http://www.mulesoft.org/schema/mule/core":abstract-multi-transaction,
"http://www.mulesoft.org/schema/mule/core":property,
"http://www.mulesoft.org/schema/mule/core":properties}' is expected.
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:115)
at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:116)
at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:47)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:80)
at org.mule.tck.AbstractMuleTestCase.createMuleContext(AbstractMuleTestCase.java:512)
at org.mule.tck.AbstractMuleTestCase.setUp(AbstractMuleTestCase.java:451)
at junit.framework.TestCase.runBare(TestCase.java:132)
at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:303)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:282)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
Line 171 in XML document from URL
[file:/C:/upb/dp/manchlia-dp/depot/services/data-platform/trunk/dp-pipeline/app-bridge/target/test-classes/mule-config-ut.xml]
is invalid; nested exception is org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'response'. One of
'{"http://www.mulesoft.org/schema/mule/core":abstract-reconnection-strategy,
"http://www.mulesoft.org/schema/mule/core":abstract-multi-transaction,
"http://www.mulesoft.org/schema/mule/core":property,
"http://www.mulesoft.org/schema/mule/core":properties}' is expected.
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:107)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89)
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:107)
... 23 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a:
Invalid content was found starting with element 'response'. One of
'{"http://www.mulesoft.org/schema/mule/core":abstract-reconnection-strategy,
"http://www.mulesoft.org/schema/mule/core":abstract-multi-transaction,
"http://www.mulesoft.org/schema/mule/core":property,
"http://www.mulesoft.org/schema/mule/core":properties}' is expected.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:417)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3182)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1806)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)
... 32 more


On Wed, Sep 21, 2011 at 11:52 AM, Magnus Larsson

rvo...@gmail.com

unread,
Sep 21, 2011, 3:16:37 PM9/21/11
to us...@mule.codehaus.org
Put the jms:transaction element below the response element.

<[hidden email]> wrote:
> On Wed, Sep 21, 2011 at 8:43 PM, Mohit Anchlia <[hidden email]>
>> > On Wed, Sep 21, 2011 at 8:20 PM, Mohit Anchlia <[hidden email]>
>> >> > <[hidden email]>
>> >> >> > <[hidden email]>
---------------------------------------------------------------------
If you reply to this email, your message will be added to the discussion below:
http://mule.1045714.n5.nabble.com/Posting-message-back-to-the-queue-tp4824252p4827517.html
To start a new topic under Mule - User, email [hidden email]
To unsubscribe from Mule - User, click here.


View this message in context: Re: Posting message back to the queue
Sent from the Mule - User mailing list archive at Nabble.com.

Mohit Anchlia

unread,
Sep 21, 2011, 3:40:09 PM9/21/11
to us...@mule.codehaus.org
that works. Thanks!!

Magnus Larsson

unread,
Sep 21, 2011, 3:53:35 PM9/21/11
to us...@mule.codehaus.org
Great!

Hunting down the right error helps :-)

Regards,
Magnus.
Reply all
Reply to author
Forward
0 new messages