Re: "Another thread runs exclusively already." exception

• To: ozone-users@ozone-db.org
• Subject: Re: "Another thread runs exclusively already." exception
• From: Timothy Reaves <treaves@silverfields.com>
• Date: Thu, 01 Jun 2000 15:32:36 -0400
• Organization: Silverfields
• References: <39342768.E2419052@silverfields.com> <00060116551401.01438@sheepy> <39367E50.2EEB2B20@silverfields.com> <00060120313100.02488@sheepy>
• Sender: treaves@umbar.pair.com

Falko Braeutigam wrote:

>
> >
> > I see the code commented out dealing with stopping the other thread.  What was
> > wrong there?
> The comment say: race conditions - but right now I don't see the problem.
> Please try the commented code.

O.K., I tried it with the code uncommented and recompiled, and same thing.

It always has to do with how FAST the query is sent, not how many.  Perhaps some object
with the server threads or transactions are not being gc'ed fast enough?  Are you using
thread / transaction pools?

• References:
  • Re: "Another thread runs exclusively already." exception
    • From: Falko Braeutigam <falko@softwarebuero.de>
  • Re: "Another thread runs exclusively already." exception
    • From: Timothy Reaves <treaves@silverfields.com>
  • Re: "Another thread runs exclusively already." exception
    • From: Falko Braeutigam <falko@softwarebuero.de>

• Prev by Date: Re: "Another thread runs exclusively already." exception
• Next by Date: Objects inside objects don't persist??!?
• Prev by thread: Re: "Another thread runs exclusively already." exception
• Next by thread: Re: prowler0.2 org/.../prowler/castor is missing
• Index(es):
  • Date
  • Thread