[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Newbie question
On 22 Mar 2001 19:46:25 +0100, Falko Braeutigam wrote:
> On Tue, 13 Mar 2001, Szabó Péter wrote:
> > > On Sun, 11 Mar 2001, Szabó Péter wrote:
> > > > ----- Original Message -----
> > > > From: "Falko Braeutigam" <falko@smb-tec.com>
> > > > To: "SZABO Peter" <petike@inf.elte.hu>; <OZONE-USERS@OZONE-DB.ORG>
> > > > Sent: Friday, March 09, 2001 6:42 PM
> > > > Subject: Re: Newbie question
> > > >
> > > >
> > > > > On Fri, 09 Mar 2001, SZABO Peter wrote:
> > > > > > Hi!
> > > > > >
> > > > > > I have been using Ozone 0.6 for a few days.
> > > > > > My application works fine, but on the ozone console I can see
> > > > > > java.net.SocketExceptions appearing.
> > > > >
> > > > > Does this happen when you close the client app? Do you have a
> > > > database.close()
> > > > > in your client code?
> > > >
> > > > No. It happens after accessing db objects.
> > > >
> > > > I made a debug session (on the client side), and the exception is thrown
> > in
> > > > the server, when the method that made the request on the client side
> > > > terminates. (after the last statement, but before the "return" is
> > complete)
> > > >
> > > > I open the database only once per client session, and the
> > > > exceptions keep coming even right after a db reinstall,
> > > > db startup.
> > >
> > > Are you an Linux or win?
> >
> > I am on Linux. The client is a java servlet running under
> > Jakarta-Tomcat. The files are compiled with VisualAge.
> > Can this be a problem?
>
> Don't know. I did not yet work with VisualAge.
>
I'm not sure which version of VA you are using, but if it is 3.0, then
it is based on a 117 JVM
I seem to remember some discussion a while ago stating ozone is for
1.2.x, 1.3 or higher, (I might be totally remembering somthing else from
some other list), maybe this is the problem
Sean Allen