« Return to Thread: JMS exceptions in Mule 2.2.1

Re: JMS exceptions in Mule 2.2.1

by ron.fulkerson :: Rate this Message:

Reply to Author | View in Thread

Hi,

Thanks again for the reply.  I tried to update my configuration to match
the example, but still had no success.  I then adapted the echo example
in 2.2.1 to work similar to your example, but still no luck.  I have
pasted the adapted echo config below.

Thanks for the help,
Ron

<?xml version="1.0" encoding="utf-8"?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:spring="http://www.springframework.org/schema/beans"
        xmlns:stdio="http://www.mulesource.org/schema/mule/stdio/2.2"
        xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2"
        xmlns:jms="http://www.mulesource.org/schema/mule/jms/2.2"
        xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
                           
http://www.mulesource.org/schema/mule/core/2.2 
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
                           
http://www.mulesource.org/schema/mule/stdio/2.2 
http://www.mulesource.org/schema/mule/stdio/2.2/mule-stdio.xsd
                           
http://www.mulesource.org/schema/mule/jms/2.2 
http://www.mulesource.org/schema/mule/jms/2.2/mule-jms.xsd
                            http://www.mulesource.org/schema/mule/vm/2.2 
http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd">
    <description>This is a simple component example that demostrates how
to expose a component over multiple transports.</description>

    <jms:activemq-connector name="jmsConnector"
brokerURL="tcp://localhost:4101" specification="1.1"
disableTemporaryReplyToDestinations="true" />
    <stdio:connector name="SystemStreamConnector" promptMessage="Please
enter something:" messageDelayTime="1000" />

    <model name="echoSample">
        <service name="EchoUMO">
            <inbound>
                <stdio:inbound-endpoint system="IN"/>
            </inbound>
            <outbound>
                <chaining-router>
                    <vm:outbound-endpoint path="echo" synchronous="true" />
                    <stdio:outbound-endpoint system="OUT"
synchronous="false" />
                </chaining-router>
            </outbound>
        </service>
        <service name="Requester">
            <inbound>
                <vm:inbound-endpoint path="echo" synchronous="true" />
            </inbound>
            <outbound>
                <chaining-router>
                    <jms:outbound-endpoint queue="RequestQueue"
synchronous="true" />
                    <reply-to address="jms://ReplyQueue" />
                </chaining-router>
            </outbound>
            <async-reply timeout="10000" failOnTimeout="true">
                <jms:inbound-endpoint queue="ReplyQueue" />
                <single-async-reply-router />
            </async-reply>
        </service>
        <service name="Replier">
            <inbound>
                <jms:inbound-endpoint queue="RequestQueue"
synchronous="true" />
            </inbound>
            <echo-component />
        </service>
    </model>
</mule>


Puneet Gupta wrote:

> Here is a working example:
>
>    <model name="jms-test-suite">
>        <service name="Requester">
>            <inbound>
>                <vm:inbound-endpoint path="IN" synchronous="true"/>
>            </inbound>
>            <outbound>
>                <chaining-router>
>                    <jms:outbound-endpoint queue="RequestQueue"
> synchronous="true"/>
>                    <reply-to address="jms://ReplyQueue"/>
>                </chaining-router>
>            </outbound>
>            <async-reply timeout="10000" failOnTimeout="true">
>                <jms:inbound-endpoint queue="ReplyQueue"/>
>                <single-async-reply-router/>
>            </async-reply>
>        </service>
>
>        <service name="Replier">
>            <inbound>
>                <jms:inbound-endpoint queue="RequestQueue" synchronous="true"/>
>            </inbound>
>            <echo-component/>
>        </service>
> </model>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>  

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

    http://xircles.codehaus.org/manage_email


 « Return to Thread: JMS exceptions in Mule 2.2.1