Just to let everyone knows that this bug has been fixed.
Thanks,
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831508#3831508
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831508
Chris,
I have a fix here for you to test it out. Can you send me your email address? Mine is
[EMAIL PROTECTED] I will mail you the new jar.
Thanks,
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3829802#3829802
Reply to the post :
Chris,
I've taken a look at the source code. I can see a chance for the null pointer
exception.
Is there a test case that you can send me to reproduce this problem so I can validate
it? I'd like to add it to the JUnit test suite as well.
Otherwise, I will fix it and have you tested out for
Unfortunately I couldn't send you the code to test since it is hitting up on the DB
(which is constantly changing itself). All I am doing is a mass bulk from a DB table
(about 2 at a time), and they are all just simple strings. ie
cache.put(/DBConstant/State, California, 5);
Ben,
When you get a chance please let me know what is coming up null. Is it something I can
check before each put?
Thanks again,
Chris
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3828988#3828988
Reply to the post :
It is while doing a bulk insert of a few thousand elements and it seems to happen
about once every 4 or 5 runs. And it isn't ever really on the same element. Sometimes
it will only get through 50 or 60 and sometimes it does 1 before it crashes.
Thanks again,
Chris
View the original post :
Chris,
Thanks for reporting the problem. Can you give me more detailed info on how can I
reproduce the problem? BTW, I am currently out of town and won't be able to look into
this problem untill next week.
Thanks,
-Ben
View the original post :
