I committed the fix we know about to amq 4.1 and trunk. However the
code looks rather thread-unsafe -- I'm trying to verify that it needs
to be thread-safe -- so I expect additional fixes will be needed
before we think about a release.
thanks
david jencks
On Mar 13, 2008, at 1:18 PM, Manu George wrote:
Hi Beniamin,
You can also set the InstanceLimit to 0 to disable
the limiting on the MdbContainer side. This may help you too as the
bug in AMQ occurs when the openejb container tries to limit the no of
sessions to the instanceLimit specified.
Regards
Manu
On Thu, Mar 13, 2008 at 3:48 PM, Manu George
<[EMAIL PROTECTED]> wrote:
Hi Beniamin,
The JIRA explains what changes need to be made to
AMQ code. You can try checking out AMQ 4.1.1. from the AMQ site
(http://svn.apache.org/repos/asf/activemq/tags/activemq-4.1.1/) and
making the change as mentioned in the JIRA. The change is in the
method getServerSession of the class
org.apache.activemq.ra.ServerSessionPoolImpl. The line number is
120.
You just need to change the if condition from if
(idleSessions.size()
== 0) to if (activeSessions.size() == 0). I have tried this out and
for me it even solves the problem that we need to give
maxMessagesPerSession == maxSessions. I tested with maxSessions =10
and maxMessagesPerSession = 100 and it was able to process 4000
messages (4 requests of 1000 each) without any being left in the
queue. I know that there are many other combinations I have not
tried
yet and I cannot vouch that they will work but if still you get the
problem after applying this patch we will know that there is some
other problem also.
Regards
Manu
On Thu, Mar 13, 2008 at 4:51 AM, Tomasz Mazan <[EMAIL PROTECTED]> wrote:
David Jencks pisze:
Does fixing the activeMQ bug
https://issues.apache.org/activemq/browse/AMQ-1618 help with any of
these problems? I would find it very difficult to analyze other
failures until this is fixed.
thanks
david jencks
I hope it will do, but now - as I understand - I can only wait
for this
patch included in next Geronimo release. What is expected date
of this
ActiveMQ patch ?
Beniamin
