Hi Stefan,

Thanks for the info about connection property. Will use it. However I dont think I use "Load.asNeeded". I'm using "Load.All"

Dont think firebird crash. Should it not create a log? Also remote clients uses the same firebird server and it works.

Also i dont think its corruption because then the problem would not occur occasionally. After application restart everything works fine, until the next time.

BR,

--- In Firebird-Java@yahoogroups.com, Stefan Schmaltz <schlocke@...> wrote:
>
> We are also using Borland's DataExpress components.
> When you do a commit (savechanges) on your datasets with open resultsets
> (Load.asNeeded keeps them open), every resultset is closed, so accessing
> new data on your datasets causes exception "Resultset is already
> closed", this is not a multithreading issue. Use connection property
> "defaultResultSetHoldable", "true" to keep them open.
>
> "Unable to complete network request to host" is thrown if the connection
> to your firebird sql server is lost or firebird crashes. Firebird
> crashes often when your database is corrupt. Try to backup+restore your
> database.
>
> regards,
> S
>
>
> Am 13.03.2013 00:06, schrieb hugo.larson:
> >
> >
> >
> > --- In Firebird-Java@yahoogroups.com
> > <mailto:Firebird-Java%40yahoogroups.com>, Mark Rotteveel <mark@> wrote:
> > >
> > > On 7-3-2013 20:34, hugo.larson wrote:
> > > > Hello,
> > > > I'm not using iscSeekBlob or iscBlobInfo.
> > >
> > > If you are using Blobs, then iscBlobInfo most likely is getting used
> > > (iscSeekBlob depends on how you use blobs).
> > >
> > > > The problem can't be related to network issues since it happens on
> > localhost.
> > > > I think that JBuilder DataExpress does not like that different
> > threads execute statements simultaneously with same connections but
> > that usually (I think) throws an exception "Resultset is already closed".
> > > > I don't think I do that but will do some logging to exclude the
> > possibility.
> > >
> > > On localhost it likely isn't a network problem. The only reasons would
> > > be that the Firebird server closes connections for some reason (this
> > > would include Jaybird misbehaving), or you have a firewall or
> > > virusscanner that allows connections, but only closes a port if it
> > > generates too much traffic, but if that would be the cause, then I
> > would
> > > expect this to be a much more frequent occurrence.
> > >
> > > What connection properties are you using?
> > >
> > > Mark
> > > --
> > > Mark Rotteveel
> > >
> > Hello Mark,
> > Sorry i missed this post.
> > > virusscanner
> > We have seen this problem on machines that do not have virusscanner
> > installed.
> > > What connection properties are you using?
> > Connection properties: (problem existed before these new props)
> > "connectTimeout", "3"
> > "columnLabelForName", "true"
> >
> > I have now logging which logs every database query. No problem with
> > threads that use same database connection.
> >
> > I have furthermore noticed this. Normally when a client cant access
> > database which is a remote computer the following exception is thrown:
> > com.borland.dx.dataset.DataSetException:
> > GDS Exception. 335544721. Unable to complete network request to host
> > "KASSA1".
> >
> > But I have same exception thrown on computer which try to access
> > remote database but with empty host, same as localhost:
> > com.borland.dx.dataset.DataSetException: GDS Exception. 335544721.
> > Unable to complete network request to host "".
> >
> > Regards,
> >
> >
> >
>
>
> --
>
> Dipl. Inform. (FH)
> Stefan Schmaltz
> Softwareentwicklung
>
> Fronäckerstr. 48/Büro: Sommerstr. 11
> 68219 Mannheim
> schlocke@...
> http://www.schlocke.de
>
>
>
> [Non-text portions of this message have been removed]
>