Subject | Re: FireBird lock problem |
---|---|
Author | nrajagopal35 |
Post date | 2003-12-04T09:50:38Z |
As I have said in my previous mail, that issue occured with JCA JDBC
driver version 0.9 which I have got from FirebirdSQL-1.0.1.zip. The
same is downloaded from sourceforge.net site.
From your help, I have tried with the latest driver version
FirebirdSQL-1.5_20031030.zip. Then there is no problem and everything
is working fine. This zip I have downloaded from this groups file section.
Basically I am new to this FireBird and JCA driver.
Can you tell me about the licensing details of these two. Can I use
the latest zip which I have downloaded from this group into my
application?
For using this driver and redistributing does anything needs to be paid?
What kind of licensing, is is LGPL or GPL?
Kindly help me in this regard.
Thanks & Regards,
Rajagopal N
--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:
driver version 0.9 which I have got from FirebirdSQL-1.0.1.zip. The
same is downloaded from sourceforge.net site.
From your help, I have tried with the latest driver version
FirebirdSQL-1.5_20031030.zip. Then there is no problem and everything
is working fine. This zip I have downloaded from this groups file section.
Basically I am new to this FireBird and JCA driver.
Can you tell me about the licensing details of these two. Can I use
the latest zip which I have downloaded from this group into my
application?
For using this driver and redistributing does anything needs to be paid?
What kind of licensing, is is LGPL or GPL?
Kindly help me in this regard.
Thanks & Regards,
Rajagopal N
--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:
> > Actually I am giving the thread dump of driver,
> >
> > while doing an executeUpdate the following trace locks up some
> > statement
> > ...
> > at java.net.SocketInputStream.socketRead0(Native Method)
> > at java.net.SocketInputStream.read(Unknown Source)
> > ...
> >
> > For this statement other thread waits, but the above threads doesn't
> > return and stays there itself.
> > ...
> > Is there anything like we have to with the DB handle or something
> > like that, or how we can we solve this problem
>
> If the first thread is blocked forever in socket read, then this is a
> bug in the wire protocol implementation in the driver and I would like
> to have a reproducable test case.
>
> If it is blocked only because query/update execution takes a lot of
> time, there's nothing you can do about it. Server will not accept any
> other statement until this one is finished.
>
> If you need to execute some statement, while another is running, you
> need to use another connection.
>
> Can you provide some code that reproduces your problem?
>
> Thanks!
> Roman