Subject | Re: [Firebird-Java] Re: GDS Exception. 335544721. Unable to complete network request to host |
---|---|
Author | Mark Rotteveel |
Post date | 2013-05-13T07:06:22Z |
On Mon, 13 May 2013 04:54:46 -0000, "psureshkumar14@..."
<sureshkumar.p@...> wrote:
IOException and thus "Unable to complete network request to host "" " in
the driver. The only guess is that the IOException causes the termination
of the thread and the connection is - eventually - returned to a connection
pool in an inconsistent state. Subsequent use of that connection throws
this exception.
That is a nice theory, but the connection shouldn't be in an inconsistent
state if a Jaybird method completed before the IOException occurred in a
different part of your application.
Could you try to reproduce the issue with Jaybird 2.2.3 and share the
exception that should now include the IOException stacktrace?
Mark
<sureshkumar.p@...> wrote:
> Hi Mark,",
>
> For the exception "Unable to complete network request to host ""
> I got an clue. Whenever an IOException throws in our producthandled
> server/running environment, this error occurs. If i properly
> in my server(tomcat/java program), this issue fixed. what i amI have no clue how an unrelated IOException elsewhere could cause an
> telling is, this issue is not happened due to Firebird.
>
> Please let me if i am wrong!.
IOException and thus "Unable to complete network request to host "" " in
the driver. The only guess is that the IOException causes the termination
of the thread and the connection is - eventually - returned to a connection
pool in an inconsistent state. Subsequent use of that connection throws
this exception.
That is a nice theory, but the connection shouldn't be in an inconsistent
state if a Jaybird method completed before the IOException occurred in a
different part of your application.
> Note: Two of customers faced that issue, from analyzing java logs theI
> IOException is throwed in our code(This code is not related to DB Call.
> am still wondering, how this is possible!!). After handling thatIt is good to know, but I am not yet closer to a solution ;)
> IOException, the reported above issue not reproduced in our setup.
>
> Trust this helps.
Could you try to reproduce the issue with Jaybird 2.2.3 and share the
exception that should now include the IOException stacktrace?
Mark