Hey,
Thanks karthik. Will let you guys know once this is moved into production as
well!!! :)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3867251#3867251
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3867251
Hi,
I examined concurrent.jar from both JBoss 4.0.0 and JBoss 3.2.5. Both of these
have the same version of concurrent.jar (ie: 1.3.3) but with different file
sizes -
JBoss 4.0.0 - 165 KB
JBoss 3.2.5 - 168KB
For the same MDB issue as reported by Karthik in earlier posts, I want to
replace my
you can get 1.3.4 from the source
http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html
and apply it. That is what i did.
regards
Karthik
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3867216#3867216
Reply to the post :
Thanks for the heads up.
We are upgrading to the latest concurrent-1.3.4
which has a QueuedExecutor fix.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3867153#3867153
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3867153
We are experiencing the same problem here with 4.0.1, do we need to upgrade the
concurrent.jar aswell or does 4.0.1 ship with a fixed version?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3866994#3866994
Reply to the post :
Since we upgraded the concurrent.jar, we have not seen this problem re-occur.
I see no harm in trying it out. From the size of the jar distributed with
4.0.1, I suspect it is not the latest version.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3866998#3866998
Thanks for the hint. I will replace our concurrent.jar and see how it goes.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3862539#3862539
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3862539
Reporting bugs against old versions is futile (especially when they this one
was fixed/worked around over a year ago).
It is actually a bug in oswego's concurrent.jar
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3862488#3862488
Reply to the post :
