Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Result set is dead...

4 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-05-21 16:37:00.0Z
lplanchenault Posted on 1997-05-09 17:51:57.0Z
Message-ID: <3373643D.7944@comtech.lu>
Date: Fri, 09 May 1997 19:51:57 +0200
From: lplanchenault@comtech.lu
X-Mailer: Mozilla 3.0 (Win95; I)
MIME-Version: 1.0
Subject: Result set is dead...
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 15
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:834
Article PK: 252586

I use an SQL request server from WebLogic, so my architecture is a
three-tier one.

When I issue a select statement with a where clause including an integer
(eg, select * from table where id = n), I have an exception on the
following call to ResultSet.getResultSetMetaData().

I can't enable a very good trace, but the exception is raised by
a call to checkResultSet, then the message is "RESULT SET IS DEAD".
This does not happen when any other kind of select, neither with a
two-tier architecture.

What is the meaning of this message, how can I investigate ?


Lance Andersen Posted on 1997-05-19 21:18:15.0Z
Message-ID: <3380C397.54AD@sybase.com>
Date: Mon, 19 May 1997 17:18:15 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: lplanchenault@comtech.lu
Subject: Re: Result set is dead...
References: <3373643D.7944@comtech.lu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 32
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:817
Article PK: 252569

Hi,

I am not sure whether you will get any assistance in this newsgroup on
the WebLogic jdbc driver. The readers of this newsgroup are using the
Sybase jConnect jdbc driver.


-Lance

lplanchenault@comtech.lu wrote:
>
> I use an SQL request server from WebLogic, so my architecture is a
> three-tier one.
>
> When I issue a select statement with a where clause including an integer
> (eg, select * from table where id = n), I have an exception on the
> following call to ResultSet.getResultSetMetaData().
>
> I can't enable a very good trace, but the exception is raised by
> a call to checkResultSet, then the message is "RESULT SET IS DEAD".
> This does not happen when any other kind of select, neither with a
> two-tier architecture.
>
> What is the meaning of this message, how can I investigate ?

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Technical Support Phone:(617) 564-6336
77 South Bedford Street Fax: (617) 564-6148
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


lplanchenault Posted on 1997-05-14 17:47:29.0Z
Message-ID: <3379FAB1.3132@comtech.lu>
Date: Wed, 14 May 1997 19:47:29 +0200
From: lplanchenault@comtech.lu
X-Mailer: Mozilla 3.0 (Win95; I)
MIME-Version: 1.0
Subject: Re: Result set is dead...
References: <3373643D.7944@comtech.lu> <3380C397.54AD@sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 41
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:802
Article PK: 252555

May be I didn't make myself clear. I am using jConnect Too between the
server and
the database. The exception is coming from the sybase classes...
I just need more explanations about the esoteric message "Result is
dead".
We are all mortal...

Lance Andersen wrote:
>
> Hi,
>
> I am not sure whether you will get any assistance in this newsgroup on
> the WebLogic jdbc driver. The readers of this newsgroup are using the
> Sybase jConnect jdbc driver.
>
> -Lance
> lplanchenault@comtech.lu wrote:
> >
> > I use an SQL request server from WebLogic, so my architecture is a
> > three-tier one.
> >
> > When I issue a select statement with a where clause including an integer
> > (eg, select * from table where id = n), I have an exception on the
> > following call to ResultSet.getResultSetMetaData().
> >
> > I can't enable a very good trace, but the exception is raised by
> > a call to checkResultSet, then the message is "RESULT SET IS DEAD".
> > This does not happen when any other kind of select, neither with a
> > two-tier architecture.
> >
> > What is the meaning of this message, how can I investigate ?
>
> --
> ===============================================================================
> Lance J. Andersen Email: lancea@sybase.com
> Sybase Technical Support Phone:(617) 564-6336
> 77 South Bedford Street Fax: (617) 564-6148
> Burlington, MA 01803
>
> The Dark Knight Returns!!! Let's Go Penguins!!!
> ===============================================================================


David Clegg Posted on 1997-05-21 16:37:00.0Z
Message-ID: <338324AC.7CC9C417@sybase.com>
Date: Wed, 21 May 1997 09:37:00 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: lplanchenault@comtech.lu
Subject: Re: Result set is dead...
References: <3373643D.7944@comtech.lu> <3380C397.54AD@sybase.com> <3379FAB1.3132@comtech.lu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 58
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:799
Article PK: 252551

All method calls on a ResultSet will throw this exception after
the resultSet has been closed. A result set is closed either
explicitly by you calling its close() method, or implicitly by
using the Statement the resultSet comes from for something else
(executing a new query, calling statement.nextResult(),
Statement.cancel(), etc.)

If you change your CLASSPATH to pick up th $JDBC_HOME/devclasses
version of the classes, and add a call to
com.sybase.utils.Debug.debug(true,"ALL");
in the beginning of your program, you should be able to find out
how that resultset is getting closed.

dave

>
> May be I didn't make myself clear. I am using jConnect Too between the
> server and
> the database. The exception is coming from the sybase classes...
> I just need more explanations about the esoteric message "Result is
> dead".
> We are all mortal...
>
> Lance Andersen wrote:
> >
> > Hi,
> >
> > I am not sure whether you will get any assistance in this newsgroup on
> > the WebLogic jdbc driver. The readers of this newsgroup are using the
> > Sybase jConnect jdbc driver.
> >
> > -Lance
> > lplanchenault@comtech.lu wrote:
> > >
> > > I use an SQL request server from WebLogic, so my architecture is a
> > > three-tier one.
> > >
> > > When I issue a select statement with a where clause including an integer
> > > (eg, select * from table where id = n), I have an exception on the
> > > following call to ResultSet.getResultSetMetaData().
> > >
> > > I can't enable a very good trace, but the exception is raised by
> > > a call to checkResultSet, then the message is "RESULT SET IS DEAD".
> > > This does not happen when any other kind of select, neither with a
> > > two-tier architecture.
> > >
> > > What is the meaning of this message, how can I investigate ?
> >
> > --
> > ===============================================================================
> > Lance J. Andersen Email: lancea@sybase.com
> > Sybase Technical Support Phone:(617) 564-6336
> > 77 South Bedford Street Fax: (617) 564-6148
> > Burlington, MA 01803
> >
> > The Dark Knight Returns!!! Let's Go Penguins!!!
> > ===============================================================================