rg
Cc:
Data: Tue, 26 Oct 2010 17:06:07 +0200
Oggetto: Re: Tomcat cluster error (null pointer except) on NioReceiver.java:266
> In the post before I sed why accept() returns null, so i was> investigating
> in tomcat and jdk_1.6 source code, > and I found that the method accept in
&
In the post before I sed why accept() returns null, so i was
investigating in tomcat and jdk_1.6 source code,
and I found that the method accept in ServerSocketChannel.java can
return null in case of non-blocking socket e no connection available.
Should this be tested?
and why ask for session rep
Hi, thanks for reply,
I was watching too the NioReceiver.java source code, and I was wondering
why server.accept() does not throw an exception instead null, mha!.
The java version in production is 1.6.0_20 vendor Sun 64bit.
while in my devel environment is 1.6.0_11 vendor Sun 32bit.
In catalina.o
2010/10/22 Stefano Suzzi :
>
> Hi, i've 3 tomcat 6.0.26 on 3 different IBM machines linux RedHat el
> 5, kernel.osrelease = 2.6.18-194.el5 .
>
> The 3 tomcat are giving an error that cannot replicate the session,
> of course I cannot replicate the error in my devel systems that work
> perfectly w
gp456 wrote:
thanks for your reply.
first the fix you mentioned is not in the current tomcat release (6.0.16).
Since I have to build/patch the tomcat for a productive environment what
whould you recommend: patch the 6.0.16 sources or build tomcat from the
newest trunk?
either or, they haven'
thanks for your reply.
first the fix you mentioned is not in the current tomcat release (6.0.16).
Since I have to build/patch the tomcat for a productive environment what
whould you recommend: patch the 6.0.16 sources or build tomcat from the
newest trunk?
We've ran another test and encountered
you already asked this question, and I already answered.
http://marc.info/?l=tomcat-user&m=120290898727190&w=2
Filip
gp456 wrote:
Hello,
we have a similar problem as Raul Garcia has posted in
http://www.nabble.com/Tomcat-6---Cluster-error.-to14921385.html#a14921385
this message, but we're
[CLUSTERLOG] NioReceiver - WARN - 02/12/2008 17:34:23,895 - NioReceiver -
Channel key is registered, but has had no interest ops for the last 3000 ms.
(canc
elled:false):[EMAIL PROTECTED] last access:2008-02-12
17:34:17.957
and finally:
this message most likely indicates that the thread pool hand
