If you have a large java app that uses many threads for simultaneous db
access, I have to ask why you aren't writing it as a j2ee application on
JBoss.

I suggest that each thread use its own connection. Is this what you are
already doing?

Note that the type 4 driver can be set up to do connection pooling
internally, so having short lived threads obtain and close connections will
not result in actually making and closing physical db connections. Sharing
a connection among several threads is not a good idea IMO even if it
usually works.

david jencks

On 2002.04.19 11:04:25 -0400 Sanjay Amatya wrote:
> More experiments with IB:
>
> Single thread model of reading and writing data works fine. When multiple
> threads
> try to access the db, gor following error:
>
> interbase.interclient.CommunicationException: [interclient] Communication
> error: An
> IO exception occurred while trying to receive data from server desktop83.
> The message of the IOException is "socket closed (code=0)".
> See API reference for exception interbase.interclient.CommunicationException
>
> Thoughts?
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
>
> 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/
>
>
>
>
>