I don't know if these messages in my console are related to the problem I
have (description a bit further in this message) but they keep terrorizing
my console since the use of Cocoon 2.1.3:
key = KeyObject, pos = 4623138
java.io.EOFException
at java.io.RandomAccessFile.readByte(RandomAccessFile.java:564)
at
com.coyotegulch.jisp.ObjectDatabaseFile.readObject(ObjectDatabaseFile.java:3
67)
at
com.coyotegulch.jisp.IndexedObjectDatabase.read(IndexedObjectDatabase.java:2
44)
.....
....
BTW: a normal shutdown of tomcat doesn't seem to be possible anymore. When
closing tomcat the kind way the java process directly jumps to 100% CPU
usage and it doesn't stop anymore.
Any idea what is happening since my coocon upgrade?
--
Danny
> -----Original Message-----
> From: Danny Bols [mailto:[EMAIL PROTECTED]
> Sent: zaterdag 15 november 2003 17:18
> To: [EMAIL PROTECTED]
> Subject: RE: Cocoon 2.1.3 / Woody / Flow - Endless Loop?
>
>
> I did not change any loglevels, the standard settings are INFO or ERROR.
> I am using Tomcat 4.1.24 and java 1.4.1_02.
> BTW I did not have any problems when using Cocoon 2.1.2.
>
> > -----Original Message-----
> > From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
> > Sent: zaterdag 15 november 2003 16:57
> > To: [EMAIL PROTECTED]
> > Subject: Re: Cocoon 2.1.3 / Woody / Flow - Endless Loop?
> >
> >
> > It can be the garbage collector. Also check your log level. If
> you set it
> > to debug, then flow component will register his own activity
> every 4 secs.
> > This activity is related to drop the old saved "continuities".
> >
> > BTW, what version of Tomcat are you using?
> >
> > Best Regards,
> >
> > Antonio Gallardo
> >
> >
> > Danny Bols dijo:
> > > Hello,
> > >
> > > since a few days I have been using the new released Cocoon
> > 2.1.3 and after
> > > a
> > > while without doing any requests to the server the java process
> > > spontaneously claims 100% of the CPU. Java behaves like it is in an
> > > endless
> > > loop. The only solution in that case is to hard kill the
> tomcat server!
> > >
> > > This behaviour only seems to happen when there has been a previously
> > > request
> > > (or requests) to the server which activated a woody flow form.
> > >
> > > Does anybody have any clue? Which component could possibly,
> without any
> > > client request, activate a process on the server?
> > >
> > > --
> > >
> > > Danny
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
