Re: SQL Error: This statement has been closed
Re: SQL Error: This statement has been closed
- Subject: Re: SQL Error: This statement has been closed
- From: Miguel Arroz <email@hidden>
- Date: Sun, 11 May 2008 01:01:38 +0100
Hi!
It seems multiple EOF stacks and synchronizers are out of the
equation. Digging further and thinking on Alentejo...
Yours
Miguel Arroz
On 2008/05/11, at 00:42, Miguel Arroz wrote:
Hi!
I just found a new reason to avoid sleeping well. I'm running an
app in development mode, with Wonder's multiple EOF stack feature
enabled, and synchronizer tuned to not allow insertions to be
broadcasted. The DB is Postgresql.
When I stress-test a little my app, running the same direct action
a lot of times in a row, sometimes the pages don't load and I get
exceptions with this:
Next exception:SQL State:55000 -- error code: 0 -- msg: This
statement has been closed.
What the heck is this?! My built-in automatic panic inducer is
screaming "there's a freackin' serious concurrency-related bug in
some nasty part of WO where you DON'T want to touch".
I still didn't test this on my deployment environment, but first it
would be nice to know what may be causing this. Any ideas?
Yours
Miguel Arroz
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden