jms sequential disorder

[sic <si...@naver.com>]

I deployed service assembly which is composed of jms bc consumer and bean
service unit, used seda flow.

after client requests our queue, jms consumer gets that message and passes
it to the bean service unit, 
which calls the external web apps(time consuming about a few seconds).
And I'm using 10 threads of the jms consumer and the number of other threads
are default.

my jms configuration is following :
<jms:consumer service=""	endpoint="" 	targetService=""	targetEndpoint="" 
	concurrentConsumers="10"
	maxMessagesPerTask="10" 
	synchronous="true"
	destinationName="FOO" 
	connectionFactory="#jmsConnectionFactory"/>

<bean id="jmsConnectionFactory"
	class="org.apache.activemq.pool.PooledConnectionFactory"
	destroy-method="stop">
	<property name="connectionFactory">
		<bean class="org.apache.activemq.ActivemqMQConnectionFactory">
			<property name="brokerURL">
				<value>vm://localhost</value>
			</property>
		</bean>
	</property>
</bean>

When client requests a lot of messages, it seems that sometimes data cannot
be processed sequentially.
for example in state that previous messages are processed, when client
requests 3 messages, 2nd, 3th messages are sent to the bean service unit,
then after about 3 minutes, 1st message is processed.

How could it be possible? because it's on the multi threads, I understand
some messages are disposed simultaneously but disordered so seriously.

I hope to get some help of this issue.

regards,
sic
-- 
View this message in context: http://servicemix.396122.n5.nabble.com/jms-sequential-disorder-tp2808143p2808143.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.