It seems that I am the only one seeing this issue :/
1 of 1 people found this helpful
We're seeing the exact same issue under a nearly identical configuration. Our DBA is gone for the day so I can't ask him what fix he put in place, but I can nearly guarantee that the problem is the configuration of Oracle (or the objects therein, rather), not JBoss Messaging. I suspect it has to do with fragmentation of the lobsegment. Our JBM_MSG sees about 20 million messages come and go per day, so there's lots of volatility in that table, which is a key ingredient for fragmentation.
Thanks for your response. I will be happy if you can get more info from your dba.
I will try to investigate the oracle part.
Our DBA told me that it's a bug in 11g, but it's easily fixed. The solution is to enable an event in the init.ora file and reboot the system. It didn't sound like you had a full-time DBA for your project, so I got a few simple instructions from our DBA to help you out.
- create pfile from spfile
- modify pfile to include the event
- startup using new pfile
- create spfile from the new pfile to put new event into spfile for next reboot
44951 TRACE NAME CONTEXT FOREVER, LEVEL 1024
This fix causes ASSM LOB space to batch up reclaim instead of just reclaiming the requested/required number of LOB chunks. To enable this fix, set event 44951 to the maximum number of chunks that you would like to have reclaimed per attempt. The maximum allowed is 1024. Anything larger becomes 1024. However, if the requested amount of space is larger than the event’s value, the reclaim will be for the requested amount of space.