Harry P. [http://community.jboss.org/people/harishpandya] created the discussion
"Re: Configure MDB PoolSize" To view the discussion, visit: http://community.jboss.org/message/625437#625437 -------------------------------------------------------------- Hi jaikiran, i want to use concurrency using JMS so i used topic implementation of JMS. My standardjboss.xml is <proxy-factory-config> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> <CreateJBossMQDestination>true</CreateJBossMQDestination> <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed --> <MinimumSize>2</MinimumSize> <MaximumSize>2</MaximumSize><!--how many parellel need for FPM --> <KeepAliveMillis>150000</KeepAliveMillis> <MaxMessages>15</MaxMessages> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> <DLQConfig> <DestinationQueue>queue/DLQ</DestinationQueue> <MaxTimesRedelivered>10</MaxTimesRedelivered> <TimeToLive>0</TimeToLive> </DLQConfig> </MDBConfig> </proxy-factory-config> Concurrency is achieved. But the problem is that concurrency is applied to a fixed no of messages after that remaining messages are taken sequentially. Ex. No. of messages on topic(range) Connecurrency performed for message Sequential 11-15 4 (2 parellel) 7-11 21-24 10(5 parellel) 11-15 25-29 18(9 parellel) 7-11 35-40 34(17 perellel- best perf.) 1-6 do you know why such pattern is followed & can we restrict it. Thanks in Advance. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/625437#625437] Start a new discussion in JBoss Messaging at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2042]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
