I'm getting this Exception quite a lot in our live environment. Customers are starting to shout so I need to fix it as soon as possible.
I have a few questions Do you know when 1.2.3 will be available? Is there a beta release available now which contains the fix? I can catch the exception and retry the put operation but is there any housekeeping calls I can make to ensure that the retry will complete ? I'm currently running Jcache 1.2.2 jBoss 3.2.5 Clustered REP_SYNC Isolation Level = NONE ( until we sort out the teething problems ) Any help or guidance appreciated, Thanks, Neil View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877971#3877971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877971 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
