Adriano,

Thank you for your reply. Unfortunately, I don't understand your questions. I didn't know I had a choice of drivers. What I've been doing is attaching the Jaybird-full-2.1.6.jar file (for Java 1.4) to the Rhapsody Database Communication Points. I tried Jaybird 2.2 with the same result.

There is no reference to 64 bit in any of the downloads from the Wiki, nor native versus java -- except that the early Jaybird 1.0 was pure java.

Pete

--- In Firebird-Java@yahoogroups.com, Adriano dos Santos Fernandes <adrianosf@...> wrote:
>
> Peter Welch escreveu:
> > Roman,
> >
> > Thank you for your thoughtful reply.
> >
> > Regarding a test case -- well, that wouldn't be easy. I can describe the configuration and events. We are feeding the Firebird database with HL7 messages (healthcare data). For the first month or two it all (Firebird 2.5 and Jaybird 2.1.6) seemed to work fine. Then, every so often there would be a hung message (in the Rhapsody interface engine) that stopped everything from getting through to the database and finally just stopped accepting data at all. One factor might be volume; we are inserting tens of thousands of rows per second at peak loads. As the database grew in size to over 100G the problem grew, or so it seemed. But, there were problems with lesser volume database feeds to FB2.5. Never a problem with FB2.1, though.
> Are you using pure-java or native driver?
>
> As you said about 64 bit, I suppose it's pure Java, but is better if you
> confirm.
>
> I think the native driver may have problems with multiple concurrent
> threads, as the Mutex class just doesn't work there AFAIR.
>
>
> Adriano
>