On 04 Mar 2014 00:15:45 -0800, <hugo.larson@...> wrote:

> I cannot reproduce the problem. We have around 200 installations and

this

> problem occurs a couple of times a day.
>> As to the actual cause: what part of Jaybird do you use to create the
> > connections?
> Looking in the DataExpress Database class the connection is created this
> way:
> connection = DriverManager.getConnection(cDesc.getConnectionURL(),
> properties);
> The DataBase class is long. If you want the source code I can send it to
> you.

I don't think I will need it, but for the sake of completeness could you
mail it to me directly?

>> For the first case there is no workaround except abandoning the
> > connection without closing.
> I think I found a way to replace the jdbc connection in the DataExpress
> DataBase object. Will try it in action.

Thanks for the information (and the stacktrace in your other e-mail).
Could you also indicate the Jaybird version that created the stacktrace? I
see the error occurred with a metadata statement, and these are handled
differently from normal statements.

Mark