I guess you're right, here is the orion console output I've got recently:
"ApplicationServerThread" (TID:0x408bfd90, sys_thread_t:0x87bc148,
state:S,
native ID:0x600a) prio=5
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java(Compiled
Code)
)
at
com.evermind.server.http.EvermindHttpServletRequest.ay(JAX(Compiled C
ode))
at com.evermind.server.http.ea.sg(JAX(Compiled Code))
at com.evermind.util.f.run(JAX)
"ApplicationServerThread" (TID:0x402c7cd8, sys_thread_t:0x811d1c8,
state:S,
native ID:0x4010) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java(Compiled Code))
at com.evermind.util.f.run(JAX)
I'll move to Sun's JDK now.
Thanks a lot.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Frank Carver
> Sent: Thursday, September 28, 2000 6:29 PM
> To: Orion-Interest
> Subject: Re: URGENT: accidental stops
>
>
>
> Thursday, September 28, 2000, 12:10:07 PM, you wrote:
>
> SM> Hello,
>
> SM> I've very urgent and annoying problem: Orion's web-service
> (or maybe whole
> SM> app)just stops responding in less than 10-20 hours of not
> very intensive use
> SM> (development, testing), but the "java -jar orion.jar" process
> still resides
> SM> in memory. Today I've found that even process died.
> SM> I'm having Intel 2xPIII 512M, Linux Debian, IBM JDK 1.3 and
> Orion 1.3.7
> SM> installed.
>
> Users of the Resin web server have reported very similar problems on
> their mailing list (archived at
> http://www.caucho.com/support/resin-interest/). Research so far seems
> to show that it is a threading problem in the IBM 1.3.0 JDK, which can
> happent on all systems, but is much more frequent with SMP. If you
> can, try with another JVM and see if the problem persists.
>
> --
> Frank Carver Efficacy Solutions Limited www.efsol.com
>
>
>
