Subject | Re: Jaybird possible bug (CLASSIC failure with INETD?) |
---|---|
Author | Roman Rokytskyy <rrokytskyy@acm.org> |
Post date | 2003-03-03T23:24:02Z |
Ray,
No, we are using Classic on Linux.
Roman
No, we are using Classic on Linux.
Roman
> Thanks for your reply. I have done some more research
> and perhaps the reason you are not having this problem
> is you are probably using the SuperServer. My partner
> in this application only has the problem when using
> the Classic version of Interbase/Firebird. The problem
> appears to be that JayBird WILL NOT connect to the
> classic beast at all. I suspect it is a problem with
> INETD, but Ann H. has been totally quiet so I cannot
> confirm. We are going to the superserver as it may be
> better anyway.
>
> Ray
> --- "Roman Rokytskyy <rrokytskyy@a...>"
> <rrokytskyy@a...> wrote:
> > > We are using RESIN, Linux Firebird and Jaybird.
> > When
> > > we replace the "application.war" (hate that
> > suffix)
> > > file on the server, it seems to cause Jaybird to
> > loose
> > > it. In order to get Jaybird to connect to the Db
> > > again, we have to bring up InterClient; make a
> > > connection; and then switch the control file back
> > to
> > > Jaybird and all is fine.
> >
> > Can you create a sample WAR (or small ant build.xml
> > to create such
> > WAR) that reproduces your problem on clean Resin
> > installation? We use
> > Resin for a long time and did not experience such
> > problems.
> >
> > Best regards,
> > Roman Rokytskyy
> >
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/