Subject | Re: GDSError |
---|---|
Author | rrokytskyy |
Post date | 2002-06-21T07:07:18Z |
Hi,
I remember there was a discussion in FB-devel list how correctly we
handle big and little endian. At that point it seemed to ok, but I'm
not sure if any testing was made on 64-bit platforms (I assume that
Solaris 2.8 is 64-bit OS, correct me if I'm wrong).
Does anybody else tried accessing IB/FB running on 64-bit hardware
(not 64-bit IO, but true 64-bit processor with appropriate OS)? I will
check if I have access to any of such machines, but I'm afraid, no.
Best regards,
Roman
I remember there was a discussion in FB-devel list how correctly we
handle big and little endian. At that point it seemed to ok, but I'm
not sure if any testing was made on 64-bit platforms (I assume that
Solaris 2.8 is 64-bit OS, correct me if I'm wrong).
Does anybody else tried accessing IB/FB running on 64-bit hardware
(not 64-bit IO, but true 64-bit processor with appropriate OS)? I will
check if I have access to any of such machines, but I'm afraid, no.
Best regards,
Roman
--- In Firebird-Java@y..., "Blas Rodriguez Somoza" <blas@p...> wrote:
> Hello
>
> The driver expects every FB implementation to use the same
protocol and byte sizes for the communication, so usually if it work
> with one version must work with others.
>
> Please send the bug to the FB List. Solaris 64IO version is not
included in the version downloads because it is not enough
> tested, so I suppose any test help.
>
> Have you tried with the standard SolarisSparc version?
>
> Regards
> Blas Rodriguez Somoza
>
> ----- Original Message -----
> From: "Thomas Viohl" <t.viohl@o...>
> To: <Firebird-Java@y...>
> Sent: Thursday, June 20, 2002 8:36 PM
> Subject: Re: [Firebird-Java] Re: GDSError
>
>
> > We use Firebird SuperServer for Solaris (Sparc)
> >
<http://firebird.sourceforge.net/download/snapshot_builds/solaris_sparc/FirebirdSS-1.0.0.796-64IO-Solaris-Sparc.tar.gz>
> > (64 Bit I/O) on Solaris 2.8.
> > also the FirebirdSQL JDBC Driver, integrated in Apache-Tomcat
> > 4.0.3.(also on Solaris)
> > After debugging the java code we have following result:
> > Directly after the
> > sqlst = sqlcon.createStatement();
> > we get our message: GDSException: org.firebirdsql.gds.GDSException:
> > message length error (encountered 88, expected ).
> > It do not matter what sql statement. (All statements work in
IBConsole).
> > Its seems that we do not get this errors in Windows 2000 (same
> > configuration).
> >
> > BTW: We made a change in the firebirdSQL.jar file. We changed the
> > parameter for log4j from DEBUG to ERROR.
> >
> > Any Ideas?
> >
> > Thomas
> >
> >
> > Blas Rodriguez Somoza wrote:
> >
> > >Hello
> > >
> > > Please, include FB version and platform and Driver version,
it will be easier to identify the bug if it exists.
> > >
> > > The message you mention comes from FB through the status
vector. The message is FB isc_port_len (335544358). You can see in
> the
> > >Language Reference pdf.
> > >
> > > Why the message appears is another question.
> > >
> > > Apparently the message can be produced by
> > >
> > > - jrd/jrd.c -- GDS_TRANSACT_REQUEST
> > > - jrd/exe.c -- EXE_receive
> > > - jrd/exe.c -- EXE_send
> > >
> > > Are you using autocommit or explicit transaction control?.
> > >
> > > If you are using Autocommit change to explicit transaction
management. This way the problem can be identified as transaction
> > >related or not.
> > >
> > >Regards
> > >Blas Rodriguez Somoza.
> > >
> > >----- Original Message -----
> > >From: "rrokytskyy" <rrokytskyy@y...>
> > >To: <Firebird-Java@y...>
> > >Sent: Thursday, June 20, 2002 10:57 AM
> > >Subject: [Firebird-Java] Re: GDSError
> > >
> > >
> > >
> > >
> > >>>After successfully executing a statement with the Firebirdsql
> > >>>driver, we always get an exception:
> > >>>...
> > >>>GDSException: org.firebirdsql.gds.GDSException: message length
> > >>>error (encountered 64, expected )
> > >>>...
> > >>>
> > >>>What does this mean, and where can I get a list of possible error
> > >>>codes?
> > >>>
> > >>>
> > >>GDSException is an exception thrown by database server. There
are two
> > >>possible reasons: bug in driver and/or InterBase problem. I suspect
> > >>latter :)
> > >>
> > >>Check your interbase.log, you might have same message there.
> > >>
> > >>Also, is this exception reproducable? Can you try it on another
> > >>InterBase installation?
> > >>
> > >>Best regards,
> > >>Roman Rokytskyy
> > >>
> > >>
> > >>
> > >>To unsubscribe from this group, send an email to:
> > >>Firebird-Java-unsubscribe@y...
> > >>
> > >>
> > >>
> > >>Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> > >To unsubscribe from this group, send an email to:
> > >Firebird-Java-unsubscribe@y...
> > >
> > >
> > >
> > >Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > >
> >
> > --
> > Thomas Viohl
> > oraise GmbH
> > Am Wall 149/150
> > D-28195 Bremen (Germany)
> > ------------------------
> > eMail: t.viohl@o...
> > Fon:++49+421-335533
> > Fax:++49+421-3355355
> > ------------------------
> >
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > Firebird-Java-unsubscribe@y...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >
> >
> >