To explain further maxSessions and maxMessagesPerSessions activation config properties are 10 by default and so is the MdbContainer instanceLimit. maxMessagePerSessions is actually the prefetch size and maxSessions is the no of parallel sessions. In case you want to use maxMessagesPerSessions as 1 i.e fetch only 1 message from queue at a time for a listener then you need to set maxSession also as 1 and it will process all the messages albeit sequentially. I am not sure why maxSessions and maxMessagesPerSessions should always be the same for the Mdbs to work but i guess it is something AMQ related.
On Jan 27, 2008 12:32 AM, Manu George <[EMAIL PROTECTED]> wrote: > Hi, > I have faced this problem. The work around was to set both > maxMessagesPerSessions and maxSessions to the same value and ensure > that it is less than the instanceLimit of the MdbContainer (By default > it is 10) but configurable via system properties. I have added a > comment to the JIRA explaining the same. > > Regards > Manu > > > On Jan 24, 2008 3:12 AM, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > > On Jan 23, 2008 6:19 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > > > > I probably won't have a chance to look at this until this weekend... > > > > Me too and that's why I'm quiet lately. Had to finish some other > > assignments (cf. openejb). > > > > Jacek > > > > -- > > Jacek Laskowski > > http://www.JacekLaskowski.pl > > >
