Cyril, Thank you for reporting and providing a well written test case. It really helps.
We've all been involved with a number of other tasks, including the workshops from last week and JBW this week, that prevented me and others from working on tickets. Having said that, because the test case in JBRULES-3528 was well written, it allowed me to see the problem and identify a solution really quickly (literally between meetings). It is committed now to both 5.4.x branch and master branch. To other community members that don't know how to report bugs, take a look at Cyril's test case (https://issues.jboss.org/browse/JBRULES-3528). It is a good example of how to help us help you. You can attach test cases to the tickets or send us a pull request in git hub. There are other community users that also usually provide good test cases (Wolfgang, just to mention one more), but if you don't know how to do it, I really recommend you look at that. Edson On Mon, Jun 25, 2012 at 5:58 AM, Cyril Sochor <cyril.soc...@gmail.com>wrote: > Hi, > > I created two issues in bugtracker, second one with pull request. > JBRULES-3528 Deadlock when using pseudo session clock > JBRULES-3529 JMS messenger for JBOSS AS 7.1 > > Issues are 20 days without any response. What's wrong? > > Thank you, > Cyril Sochor > > > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > > -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users