Hi,
I have seen a similar message a few months ago on the user list. Someone
said that in scarab, the issue ids get unusually large. Looks the same to
me.
I would guess that this might be a synchronisation issue, this smells like
copying a long value which is not an atomic operation in java. But I did
not look into the code yet, I am not very familiar with the idbroker code.
This is certainly fixable in a nightly build, if the error is found
(which can turn out to be quite difficult, as it is not very
reproducable...)
I'll add a bug entry in scarab for it, but if you want a quick solution
you will have to look yourself, I am afraid.
Thomas
On Mon, 11 Jul 2005, Dave Newton wrote:
Hi,
Using a fairly recent Torque (3.1, maybe 3.1.1) for some reason I started
getting HUGE values for one of my NEXT_ID columns and the QUANTITY column.
While saving new objects to that table I got OutOfMemory exceptions. When I
made the NEXT_ID and QUANTITY values saner the OOM exception went away.
I have since turned off cleverquantity and may switch to another persistence
mechanism fo unrelated reasons, but I'm wondering:
a) Have people ever seen this before? (I haven't, and I've been using Torque
for several years without incident)
b) Are the OOM exceptions related to the huge values, and if so, why/how?
c) Is this patch/nightly/latest-version-fixable? I know I'm not running the
latest and greatest.
Thanks much,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
