Dear Adrian, one last post about this topic, you are not expected to answer this. Perhaps it is resolved easier if we meet at a JBoss event (training etc.) some day.
Adrian wrote : | Asking people to look at dead code (3.2.3 is over a year old) | is not only a waste of their time it has an opportunity cost | I did ask you about a special patch made in 3.2.6RC2: anonymous wrote : | Revision 1.20.2.8 - (view) (download) (annotate) - [select for diffs] | Sat Aug 28 11:42:08 2004 UTC (3 months, 3 weeks ago) by ejort | Branch: Branch_3_2 | CVS Tags: JBoss_3_2_6_RC2, JBoss_3_2_7_RC1, JBoss_3_2_6 | Changes since 1.20.2.7: +9 -3 lines | Diff to previous 1.20.2.7 , to branch point 1.20 | | Simulate the single thread per session to avoid concurrent delivery to a message listener, as required by the spec. | This is not one year old. Adrian wrote : | These are the open source forums, you get what you pay for. | Actually you get more than you pay for, since you pay nothing. | Yes, we did not pay you to answer our questions in this forum. But at least we did pay JBoss to get training and documentation. According to Marc Fleurys "Professional Open Source" this is the way it works. And it works so well that now also the (HTML) docs are free. Adrian wrote : | If you want a professional service, you can always buy a support contract. | We have been considering that for some time. But your personal style is indeed not a motivating factor here. Adrian wrote : | Like I've said many times before, I consider it infinitely more rude | when people don't make even the basic effort (like test the latest version) | before posting questions or claiming they've found a bug. | We discovered this problem two weeks ago, but we were able to reproduce it only once since that time. If I were able to reproduce it consistently, i.e. if I run a test for say 2 hours, the problem appears at least once, then I could modify my setup (e.g. using JBoss 3.2.6) until the bug disappears. (Your statement about inserting Thread.sleep() made me curious whether there is some other way to trigger this bug. But I have no idea at the moment.) As the empirical way did not show any success, I tried the analytical one looking at the Changelogs since 3.2.3 and at the source code. The comment "Simulate the single thread per session to avoid concurrent delivery to a message listener, as required by the spec." did not sound like a bug fix in the first place, but most probably is one. Therefore, I just asked for some background (motivation) for this very change in one source file. If you answer would have been "cannot remember why I patched this," it would not have helped me, but it would have been OK. So I continue to go through the source as I did in the forum thread http://www.jboss.org/index.html?module=bb&op=viewtopic&t=45759 In this case I made some basic effort at least. BTW, do you use Doug Leas patched version now? Perhaps we meet some day... Regards, JÃrg View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859165#3859165 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859165 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
