You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by kbohnenberger <ke...@mantech.com> on 2009/04/17 16:34:47 UTC

jms listeners on snapshot build

I have a "jms listener" like this:
    <proxy name="queueListener1" transports="jms">
        <target>
            <inSequence>
                <property action="set" name="OUT_ONLY" value="true"/>
                <sequence key="receiveKosList"/>
            </inSequence>
        </target>
        <parameter name="transport.jms.ContentType">
            <rules>
                <jmsProperty>contentType</jmsProperty>
                <default>application/xml</default>
            </rules>
        </parameter>
        <parameter
name="transport.jms.ConnectionFactory">incomingQueueFactory</parameter>
        <parameter
name="transport.jms.Destination">cn=keithIncomingQueue</parameter>
    </proxy>


After receiving message, we schema validate the message, run through some
filters and publish a portion of the incoming message to 6 different queues. 
We have a custom spring based publisher to publish to each of the 6 queues.

This all seems to be working ok IF synapse is up all the way and running
before we start publishing messages to the "incoming queue."  However, if
there are already messages on the "incoming queue" and then we bring synapse
up, it takes a really long time for the messages to make it through the
system and only about half of the "incoming messages" make it to the
"outgoing" queues.  We've also noticed that synapse seems to reload the
spring based publishers over and over again.  

The reloading of the spring based publishers does not happen if synapse is
up all the way before we start publishing messages to the "incoming queue."

So there seems to be three problems that occur if there are messages on the
incoming queue before synapse comes up:
1)  Synapse is really really really slow processing the incoming messages. 
Unusably slow.  Like 20 incoming messages will take about 30 minutes.
2)  Not all of the incoming messages make it through the process to the
outgoing queues.
3)  The 6 spring based publishers seem to get reloaded over and over again.

Any ideas?

Thanks

Keith
-- 
View this message in context: http://www.nabble.com/jms-listeners-on-snapshot-build-tp23098856p23098856.html
Sent from the Synapse - User mailing list archive at Nabble.com.