follow up the following preference while closing your jdbc con ...

        1. ResultSet
        2. Statement
        3. Connection

        If the above said order is collapsed, that would issue the
        similar error, what you are facing now.

        If you still face the similar problem, send your code to me,
        i try to analyse it.

        ----------------------------------------------------------------
        Regards,
        g ramesh

On Wed, 19 Apr 2000, Eddy wrote:

> Yes I do use jdbc. What do you mean by "incorrect closing"? Is there a
> way to generate a traceback so I can tell what line generated the error?
> thanks,
> Eddy
>
> > -----Original Message-----
> > From: A mailing list for discussion about Sun Microsystem's Java Servlet
> > API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of G
> > Ramesh [Support]
> > Sent: Wednesday, April 19, 2000 6:46 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: FW: How to tell which method crashed?
> >
> >
> >         Are you accessing any database through Jdbc-Odbc Bridge driver ?
> >         if yes, the incorrect closing of resultset, statment, connection
> >         could throw that error.
> >
> >         ----------------------------------------------------------------
> >         Regards,
> >         g ramesh
> >
> > On Wed, 19 Apr 2000, Eddy wrote:
> >
> > > I have a servlet running on WinNT using the web server that
> > > comes with JSDK. Sporadically, I get the following error (pop-up
> > > dialog box), even though I still see my debug logging from
> > > my servlet code until I click on the OK box.
> > > Is this a the JVM, the web server, or my servlet code that
> > > is aborting? How can I track down the problem?
> > >
> > > thanks,
> > > Eddy
> > > -----
> > >
> > > java.exe - Application Error
> > >
> > > the instruction at "0x05d668d0" referenced memory at "0x05d668d0".  The
> > > memory could not be "read". Click on OK to abort, Cancel to debug.
> > >
> > >
> > __________________________________________________________________
> > _________
> > > To unsubscribe, send email to [EMAIL PROTECTED] and include
> > in the body
> > > of the message "signoff SERVLET-INTEREST".
> > >
> > > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > > Resources: http://java.sun.com/products/servlet/external-resources.html
> > > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> > >
> >
> > __________________________________________________________________
> > _________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include
> > in the body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> >
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to