Alle 13:38, mercoledì 9 ottobre 2002, [EMAIL PROTECTED]
ha scritto:
> We had/have big problems with 3.2, some of which should be present in
> 3.0.x also.
> See (still unfixed) bug report 614313 (TxManager memory leak), which
> costs us 1.6kb per transaction.
THAT'S very interesing has our batch job will cause hundred of transaction per
execution !
I'll check the bug report to see if I can find a patch. Otherwise I'll
consider to create only one big transaction for all the work (very bad
solution, but still better than having to reboot the server every night).
> Beside that 1.4.0 itself has compilation leak which kicks in when
> (re-)deploying. I heard 1.4.1 fixes this
> issue; so far I can only say that we have considerably less memory usage
> under 1.4.1 when running the
> testsuite, which does heavy (re-)deploy...
>
Should be not my problem as we don't redeploy often (once a week or less).
> We also had big problems with our application code leaking memory when
> not closing
> connections to jbossmq (topics). Since we close everything more cleanly
> now these issues went
> away. But of course you should consider this as a bug on our side, not
> on jboss's side.
Not using message beans , but thanks
Most of all thank you for your answer as I was wondering I was alone with this
problem !!!
Bye,
V
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
