You most likely have a transaction stuck.
Back in those days (of IBO 3.3) there was the potential of a few things.

What I suggest you do is put a general check by getting the session
reference and then looping through all the session's Transaction[]
references. You can look to see if any are being left open at a time when
they shouldn't be.

One remote possibility is the transaction for the SchemaCache may be holding
things up. For a time this was a blind spot and you might be in that. My
memory doesn't server me well enough to recall the exact versions of IBO
this was a problem. In short, doing the general loop through the sessions
global list of transactions will give you the "vision" you need to
investigate your apps transaction hang-up problem.

Keep this topic alive as necessary. This is a very important aspect.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Luciano Sparacino" <lsparacino@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, December 05, 2001 1:07 PM
Subject: [IBO] Server physical transactions and TIB_Transaction Auto-commit


> HI!
>
> I'm having a problem with my client/server application and i don't
know
> where o attack it in order to find a solution. I'm actually working with
> IBO 3.3 and IB 6.0 on Winnt 4.0.
>
> The fact is that the server starts consuming more and more memmory
> during the day up to a point in which it becomes very slow... the only
thing
> we can do then is to restart it and everithing works ok.
>
> I don't know if there's anything i can do with my IBO components to
get
> a better performance and release the load to the IB server (i'm actually
> using TIBOQuery, TIBOTable, TIB_TransactionSingle and TIB_Connection)
>
> I read from a guy from MER systems that physical transactions do keep
> memmory allocated since you prepare a Dataset and then that's only
released
> when commiting or rolling back. What happens if i have my transaction set
> as auto-committ?
>
> thnks