...
query or other task that does not write to the database, you still get
the commit but nothing to commit, so to speak.
this non-existing tx should be comitted, according to mr. escher
bax
---
This sf.net email is sponsored by:ThinkGeek
W
Stephane Nicoll wrote:
Hello,
We had exactly the same problem!
Using Jboss 3.2.1 with the pg73jdbc3 driver solves our problem.
Regards,
Stéphane Nicoll
You're dead right.
I had tried out the latest driver but to fix the original problem. I
never noticed it had fixed the "commit" issue.
Just
Tim,
Good to hear the problem has been resolved. I'll have to note the issue
with stored procedures.
With regards to your commit problems, Postgresql does not like receiving a
"commit" when no transactions are queued. From memory, I think the JBoss
transaction manager generates a "commit" when th
Hello,
We had exactly the same problem!
Using Jboss 3.2.1 with the pg73jdbc3 driver solves our problem.
Regards,
Stéphane Nicoll
On Wed, 2003-08-27 at 17:14, Tim McAuley wrote:
Thanks for the reply. I have at last managed to track down the problem.
Just after sending the first email I
Jon Barnett wrote:
Have you logged information on pool sizes, bean lifecycles (particularly
for the stateful session beans) and so on? You'll probably want to monitor
activity on the servlets as well - session expiry probably being an
important event. No session expiry on servlets results in a mem
gestions.
JonB.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Tim McAuley
> Sent: Friday, 22 August 2003 11:46 PM
> To: JBoss User List
> Subject: [JBoss-user] Help with memory leak issue
>
>
> Hi all,
>
> Firstly, I a
Hi all,
Firstly, I apologies if this is a vague request but I feel I need some
pointers.
I am currently testing an application for memory leaks and seem to have
found one but am not sure where it is or how to isolate the leak (if
there is in fact one).
Test:
- Set our entry servlet to have a
