michal.720 wrote:

> Thanks Jochem for your reply.
>
> The solution you described is the only one I found acceptable.
>
> 1] there is no way to destroy link to database created by ibase_pconnect()
> 2] there is no way to restart apache or firebird (from my position)
>
> I already have a switch which switches between functions connect() or
> pconnect() in my webapplication. And I already know that persistent link
> to database dies in about 20 minutes on one server where the applicaion
> runs.
>
> As you may expect, when somebody needs something, he needs it
> immediately, not after 20 minutes or one hour ;-)

I might suggest that DB schema changes should not be performed on a
production box so casually - you can make the change and show the customer
it works on a dev box and then possibly schedule in an (automated) update
'window' on the production box once a day. e.g. during quite hours the
box switches to 'connect' and a cronjob runs to patch the DB (trying
regularly until it succeeds).

if a customer knows he can rely on a DB schema change always being implemented
within 24 hours, and you explain to then how/why the process works the way it does,
then they might be less annoyed because they have the required insight and knowledge
to plan in accordance...

just a thought.
.

>
> I just wanted to know, if somebody has solved this problem different
> way. Or faster ;-)

you could setup a script that hammers the server with requests in order
to eat thru the number of requests that each child want to handle
before dying. you might want to make it a very simple script. :-)

>
> Thank you
> Michal
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>