I'm using 1 write and one 1 read connection per user, read is in autocommit mode, with the write connection i commit manually.
Connections are open up to 7 days. They is a maximum of 60 connection (30 users) that can connect to my app.
There was a big problem with creating new connections in Interclient (can't create new cause of Unaivalable Database exception after some time, this was a confirmed bug, that never was solved).
But as i look at my code again i see that connections are closed when the client disconnects. This i have programmed specially for this costumer, where i test Jaybird.
So normaly all connections has to be closed afer 1 day.
As i stated my appserver never has crashed the JVM before, and now after installing the newest driver it crashes every 1-2 days.
When i don't find a solution, i must choose another database.

The other problem with wrong result sets i have posted months before.
I normaly used the standard isolation level the driver gives me. There was no problem with Interclient. With Jaybird i sometimes get wrong resultsets.(not all rows are fetched).
I got the response to set the isolation level to Connection.TRANSACTION_READ_COMMITTED,
and i have done this for my read connections, without getting better results.
But this only happens sometimes, it is not reproducable.

gruß
Carsten

----- Original Message -----
From: "Roman Rokytskyy" <rrokytskyy@...>
To: <Firebird-Java@yahoogroups.com>
Sent: Wednesday, October 23, 2002 6:40 PM
Subject: [Firebird-Java] Re: Periodical Server-Crashes


> Hi,
>
> > I'm not using PoolMon or another Connection-Manager, just the
> > standard DriverManager.getConnection().
> > I'm just not closing connections, after a user disconnects from my
> > app and i give him his 2 connections(1read/1write) back, when he
> > connects again to my app.
>
> How long your connection lives? Note, it is very sensitive part of
> the JDBC. According to the specification, open connection always have
> a transaction associated with it. Long transactions are usually a bad
> idea, because the eat server resources. Also it is very bad idea to
> have long transaction in case of Firebird, because this has an impact
> on record version handling.
>
> What is the requirement to give the same connection over and over
> again to the client and keep it open?
>
> And one more question. Can it be that you run out of socket
> connections that your JVM can handle? How many open connections do
> you have when JVM crashes?
>
> > Before some selects i create new connections (and close them after
> > select), because if i use old connection i sometimes get false
> > results. (another bug in jaybird, i've never seen this behavior
> > with interclient).
>
> What does "false result" means here? Can it be connected with
> transaction isolation?
>
> Best regards,
> Roman Rokytskyy
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>