[seam-dev] JMS deadlock issue in JBoss AS7 7.1 Final

[Ove Ranheim]

Yes, it turns out that HornetQ page-size is not set in AS7.1.Final by default, which it should have. If page-size is not set for BLOCK policy, it will cause dead-lock after approx 30 persisted messages.

If you add this to jboss messaging sub-system configuration, it'll work fine.

<max-size-bytes>10485760</max-size-bytes>
<page-size-bytes>1048576</page-size-bytes>  <== lack of page-size is root cause

Issues updated:

https://issues.jboss.org/browse/AS7-3919
https://issues.jboss.org/browse/HORNETQ-870

/ove


On Feb 28, 2012, at 11:07 PM, Jason Porter wrote:

> Did you get this sorted out on JIRA?
> 
> On Tue, Feb 28, 2012 at 07:45, Ove Ranheim <oranheim at gmail.com> wrote:
> Hi,
> 
> I have identified a deadlock situation with JBoss 7.1.0 Final and HornetQ.
> 
> Please check out: https://issues.jboss.org/browse/AS7-3919
> 
> Could this be related to Seam JMS?
> 
> Ove
> 
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
> 
> 
> 
> -- 
> Jason Porter
> http://lightguard-jp.blogspot.com
> http://twitter.com/lightguardjp
> 
> Software Engineer
> Open Source Advocate
> Author of Seam Catch - Next Generation Java Exception Handling
> 
> PGP key id: 926CCFF5
> PGP key available at: keyserver.net, pgp.mit.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20120228/188df958/attachment.html