Hi,
I've just started looking into the NIO Connector.
And I see why it's great to combine NIO+Comet...
But does it makes any difference outside of Comet?
1) Namely, if I only have old-fashioned Servlets (not a CometProcessor) -
will it improve performance to use NIO connector (versus the good
On 29/11/2010 16:23, sol myr wrote:
Hi,
I've just started looking into the NIO Connector.
And I see why it's great to combine NIO+Comet...
But does it makes any difference outside of Comet?
Yes.
1) Namely, if I only have old-fashioned Servlets (not a CometProcessor) -
will it improve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sol,
On 11/29/2010 11:23 AM, sol myr wrote:
I've just started looking into the NIO Connector.
And I see why it's great to combine NIO+Comet...
But does it makes any difference outside of Comet?
Some data: please read the initial slides
Mark Thomas schrieb am 29.11.2010 um 16:34 (+):
On 29/11/2010 16:23, sol myr wrote:
I've just started looking into the NIO Connector.
And I see why it's great to combine NIO+Comet...
But does it makes any difference outside of Comet?
Yes.
1) Namely, if I only have old-fashioned
From: Michael Ludwig [mailto:mil...@gmx.de]
Subject: Re: (Tomcat) Does NIO connector make a difference outside of 'Comet'
?
can we say that:
(a) blocking IO requires one thread (or, in some other
server environments, one process) per socket
Well, sort of. The actual requirement is one
On Fri, Mar 5, 2010 at 8:35 AM, Ashish Jain ashja...@gmail.com wrote:
Hi,
I am having an application which is based on comet and dojo. The
application uses ActiveMQ to publish messages.I am using firebug to see the
request/response of the XMLHttprrequests. I see a difference in behaviour in
On 05/03/2010 13:25, Ashish Jain wrote:
On Fri, Mar 5, 2010 at 8:35 AM, Ashish Jain ashja...@gmail.com wrote:
Hi,
I am having an application which is based on comet and dojo. The
application uses ActiveMQ to publish messages.I am using firebug to see the
request/response of the
Hi Mark,
Since I have registered today to the users@tomcat.apache.org I was not sure
if my registration has been successful. So I was confused if my
question has made it to the list and that is the reason I have re-posted it.
Thanks
Ashish
On Fri, Mar 5, 2010 at 7:01 PM, Mark Thomas
Hi,
I am having an application which is based on comet and dojo. The application
uses ActiveMQ to publish messages.I am using firebug to see the
request/response of the XMLHttprrequests. I see a difference in behaviour in
tomcat 6.0.18 where for every request there is a response. However in case
Hello!
I think I have something for you to reproduce this issue. I managed to
create a test-servlet which causes the problem (every time) when I call it
on Linux kernel 2.4 with the NIO-connector (and no problem in kernel 2.6 or
with the BIO-connector).
I have also created a VMWare-installation
Hi!
We've been using Tomcat on Linux for a very long time (and the good old
JServe before it), and we recently started testing the NIO-connector instead
of the old blocking one. We are currently running the latest Tomcat v6.0.20.
We have a pretty large website with quite a lot of traffic
nightmare.
Filip
On 01/13/2010 07:57 AM, Tobias Lind wrote:
Hi!
We've been using Tomcat on Linux for a very long time (and the good old
JServe before it), and we recently started testing the NIO-connector instead
of the old blocking one. We are currently running the latest Tomcat v6.0.20.
We
Ok, so chances are that we will not encounter this issue if we upgrade to a
newer kernel (and/or another machine - we are currently also thinking about
upgrading the hardware)?
It would be nice to see that others are using the NIO-connector on Linux in
a productive environment without problems
libraries.
It would be nice to see that others are using the NIO-connector on Linux in
a productive environment without problems before we start upgrading...
Anyone?
Is there anything we can do to assist you in reproducing this issue?
In order to test a workaround for this issue, one would need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/27/2009 10:03 AM, Filip Hanik - Dev Lists wrote:
the warning would only print when a GC happens and there are some keys
that haven't been cancelled but dereferenced.
I will work on this, but it should not cause any problems since the
the NIO connector (along with the NIO connector
with sendFile disabled) from Apache 6.0.20 along with tcnative 1.1.16 on
a 32-bit JVM on Linux:
java version 1.6.0_13
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/27/2009 8:45 AM, Filip Hanik - Dev Lists wrote:
Christopher Schultz wrote:
These are the warnings I received:
May 23, 2009 5:03:20 AM
org.apache.tomcat.util.net.NioBlockingSelector$KeyReference finalize
WARNING: Possible key leak,
Thanks Chris,
the warning would only print when a GC happens and there are some keys
that haven't been cancelled but dereferenced.
I will work on this, but it should not cause any problems since the keys
will be cleaned out.
Filip
Christopher Schultz wrote:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/24/2009 6:19 AM, André Warnier wrote:
Christopher Schultz wrote:
Although fresh from the tree, my lemon juice doesn't work, neither does
the sun of Spain as heat source.
Chris, you may be posting stuff, but it doesn't get here.
I'm
Christopher Schultz wrote:
...
Your last one about Apache vs Tomcat.. (including NIO results) got
there fine.
But the last couple which you sent on NIO connector: appear empty,
apart from an attachment that just says Version 1.
Anyway, that's how I saw them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
(I have no idea why my messages are getting messed-up... apologies for
the empty messages... I swear I'm sending whole messages!)
During performance testing, I got the following warnings in
catalina.out. I'm using the NIO connector (along
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/26/2009 12:32 PM, André Warnier wrote:
Christopher Schultz wrote:
...
Your last one about Apache vs Tomcat.. (including NIO results) got
there fine.
But the last couple which you sent on NIO connector: appear empty,
apart from
Christopher Schultz wrote:
Although fresh from the tree, my lemon juice doesn't work, neither does
the sun of Spain as heat source.
Chris, you may be posting stuff, but it doesn't get here.
-
To unsubscribe, e-mail:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/22/2009 10:14 AM, Filip Hanik - Dev Lists wrote:
[The NIO connector in 6.0.18] simply never called close on the FD when it was
done
I tried the tomcat-coyote.jar from Tomcat 6.0.20 and everything worked
quite well. Thanks a lot
binVidpPi1ODn.bin
Description: PGP/MIME version identification
a critical size.
Meaning that the kernel can't keep up, or the NIO connector can't keep
up? I suspect the latter, because the other tests under the same
conditions at least complete... the NIO one appears not to have a
chance. Now, I'm running 6 tests and the NIO test is the 5th one, so
it's
--
Connector port=8003
protocol=org.apache.coyote.http11.Http11AprProtocol
useSendfile=false
connectionTimeout=2
server=Coyote1.1APRw/osendfile
/
!-- NIO Connector --
Connector port=8004
and the combination of web server and stress test tool leads to
TIME_WAITs, after 15 seconds your table size might reach a critical size.
Meaning that the kernel can't keep up, or the NIO connector can't keep
up? I suspect the latter, because the other tests under the same
conditions
, each using a file twice the size of the previous
test. After the 128k file test, every single test fails after that.
The last test I ran (with only 1 thread instead of 40), the NIO
connector died in the same way, but the NIO connector without sendfile
enabled appeared to work properly
connections, am I?
And there was also a file descriptor leak in the NIO connector, fixed in
http://svn.apache.org/viewvc?rev=734454view=rev
this is when Tomcat NIO serves up static content.
Yup, I'm only serving up static content (using sendfile in the first
test that failed to complete
and interesting. So we would benefit
from understanding what's going on.
Filip indicates that there is a resource leak fixed in the NIO
connector. I'll have to build that and upgrade my TC installation to see
if it fixes this problem.
Are there chances you can try again and see, whether those additional
with
ulimit -n 1024 and 40 concurrent connections, am I?
And there was also a file descriptor leak in the NIO connector, fixed in
http://svn.apache.org/viewvc?rev=734454view=rev
this is when Tomcat NIO serves up static content.
Yup, I'm only serving up static content (using sendfile
On 22.05.2009 15:46, Christopher Schultz wrote:
Rainer,
On 5/22/2009 8:55 AM, Rainer Jung wrote:
You could run a JSP including a call to System.gc();
Right. The JVM is out of file descriptors. I cannot deploy a new JSP
onto the server without restarting it. ;) I mentioned this in my
Filip,
On 5/22/2009 10:14 AM, Filip Hanik - Dev Lists wrote:
if you look at the commit, there are changelog changes in there. one of
them being a FD leak with static content.
Gotcha. I was just looking at the commit comment itself.
It simply never called close on the FD when it was done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/22/2009 10:32 AM, Rainer Jung wrote:
On 22.05.2009 15:46, Christopher Schultz wrote:
Rainer,
On 5/22/2009 8:55 AM, Rainer Jung wrote:
You could run a JSP including a call to System.gc();
Right. The JVM is out of file descriptors. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/22/2009 8:48 AM, Rainer Jung wrote:
The file descriptos thing is totaly independent. I hijacked the thread :)
Yeah, I know. Filip independently mentioned that there's a fd leak in
the NIO implementation includes in 6.0.18. I have yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I've been testing the performance of various Tomcat configurations
against Apache httpd and my serious tests are not completing for the NIO
connector because the server is running out of files:
May 20, 2009 2:35:55 AM
On 21.05.2009 17:55, Christopher Schultz wrote:
All,
I've been testing the performance of various Tomcat configurations
against Apache httpd and my serious tests are not completing for the NIO
connector because the server is running out of files:
May 20, 2009 2:35:55 AM
2 remarks about all your stress testing efforts:
A) TIME_WAIT
When not doing HTTP Keep-Alive, under high load the size of the TCP hash
table and the effectiveness of the system to lookp up TCP connections
can limit the throughput you can reach. More precisely, depending on the
excat way of
hi Christopher, generally, ulimit -n 1024 is too low for any kind of web
server.
And there was also a file descriptor leak in the NIO connector, fixed in
http://svn.apache.org/viewvc?rev=734454view=rev
this is when Tomcat NIO serves up static content.
Filip
Christopher Schultz wrote
() 0);
}
}
Thanks for any help,
Peter
--
View this message in context:
http://www.nabble.com/nio-connector-configuration-tp21969270p22252460.html
Sent from the Tomcat - User mailing list archive at Nabble.com
Sorry to bump this thread. I'm willing to pay for some assistance if
anyone's interested in helping. I'm trying to figure out 2 problems
when running my system under a light-moderate load test:
1) why do my comet timeout events not get generated on time (supposed
to be every 50 seconds,
peter, if you post your test code packaged in such a way that who ever
helps you doesn't have to reverse engineer your app to setup the test
case and test it locally, then you most likely wont have to pay anyone
to help you.
The more effort you provide in providing information to the list,
has a max heap set to 384MB)
- network latency isn't a problem
I ran 2 tests with different configurations for the nio connector: 1
test with bare-bones settings, and 1 test with everything that seemed
like it might make a difference.
Connector port=80 protocol=org.apache.coyote.http11
.
I also get the warning when trying to use keepAliveTimeout. Is this
property available for the nio connector?
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
property 'keepAliveTimeout' to '12' did not find a matching
property.
I also get the warning when trying to use
From: Peter Warren [mailto:tomcat.subscript...@gmail.com]
Subject: nio connector configuration
I can't answer your real questions, but here's a bit for your minor ones.
the acceptorThreadPriority and pollerThreadPriority are
set using ints because I get the following warnings
Thanks for the tips. Very helpful.
I also get the warning when trying to use keepAliveTimeout.
Is this property available for the nio connector?
No; it's only listed under the older connector (the one labeled Standard
Implementation that then somewhat ambiguously refers to HTTP).
I
I'm now looking for an example of how to use the NIO connector
with Tomcat--I
need this in order to use chat. I've found the following
example of how to
configure this on the Tomcat side:
Connector
port=8443
protocol=org.apache.coyote.http11.Http11NioProtocol
maxThreads=150
scheme=https
production release?
Thanks
- Original Message
From: Filip Hanik - Dev Lists devli...@hanik.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, October 29, 2008 7:15:01 AM
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks
@tomcat.apache.org
Sent: Wednesday, October 29, 2008 7:15:01 AM
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks it was fixed in trunk
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/net/NioEndpoint.java?view=diffr1=618058r2=618059
I just
7:15:01 AM
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks it was fixed in trunk
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/net/NioEndpoint.java?view=diffr1=618058r2=618059
I just forgot to backport it
Filip
Alex
Message
From: Filip Hanik - Dev Lists devli...@hanik.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, October 29, 2008 7:15:01 AM
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks it was fixed in trunk
http://svn.apache.org/viewvc
?
Thanks
- Original Message
From: Filip Hanik - Dev Lists devli...@hanik.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, October 29, 2008 7:15:01 AM
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks it was fixed in trunk
Hi Burak, I will take a look at the trace and see if I can find anything
Filip
Burak Oguz wrote:
Hi,
I am using Tomcat 6.0.18 with NIO Connector with Comet. And I have crashed
into a real problem. I want to use Comet to transfer data on high rate over
http but Tomcat gives such an error when
not
support nio. Can you offer any methods about this?
Thanks again..
On Mon, Nov 3, 2008 at 4:02 PM, Filip Hanik - Dev Lists
[EMAIL PROTECTED]wrote:
Hi Burak, I will take a look at the trace and see if I can find anything
Filip
Burak Oguz wrote:
Hi,
I am using Tomcat 6.0.18 with NIO Connector
Hi,
I am using Tomcat 6.0.18 with NIO Connector with Comet. And I have crashed
into a real problem. I want to use Comet to transfer data on high rate over
http but Tomcat gives such an error when data starts to come too rapid. I
have a multithreaded architecture behind Tomcat to handle
Hi,
My Tomcat 6.0.18 throws NPEs if there are incoming connections to an NIO
connector before the connector had a chance to initialize. The behavior that I
would expect is for Tomcat to simply refuse incoming connections until the
connector is ready.
I found a similar post on this mailing
to an NIO connector before the connector had a chance to initialize. The behavior that I would expect is for Tomcat to simply refuse incoming connections until the connector is ready.
I found a similar post on this mailing list (http://mail-archives.apache.org/mod_mbox/tomcat-users/200802.mbox
with NIO connector
thanks for the report, looks it was fixed in trunk
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/net/NioEndpoint.java?view=diffr1=618058r2=618059
I just forgot to backport it
Filip
Alex Talis wrote:
Hi,
My Tomcat 6.0.18 throws NPEs
Subject: Re: NullPointerExceptions on startup with NIO connector
thanks for the report, looks it was fixed in trunk
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/net/NioEndpoint.java?view=diffr1=618058r2=618059
I just forgot to backport it
Filip
Alex Talis wrote:
Hi
I've been using the NIO connector for a while now for HTTP. Now I'm adding
an SSL connector, and as long as I don't use NIO, everything is working
fine:
Connector port=8443
SSLEnabled=true
scheme=https secure=true
clientAuth=false sslProtocol=TLS
keystoreFile
Hmm, I just tried converting the keystore to JKS (using
org.mortbay.util.PKCS12Import) and that worked. So the JKS keystore seems
to work fine with the NIO connector, but the PKCS12 keystore only works with
non-NIO.
On 9/11/08, Tim McCune [EMAIL PROTECTED] wrote:
I've been using the NIO
I'm trying to enable SSL with Tomcat's NIO connector. Using SSL with the
HTTP connector works fine. Using NIO without SSL works fine. However, when
I combine the two, Tomcat starts to flake out when serving up any files that
are a little on the larger side (in my case, 1.6 MB). The connection
it's in the java directory of the zip file
Filip
neil davudo wrote:
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
TIA
Neil
markt-2 wrote:
neil davudo wrote:
Where can I find the source code for the NIO connector that uses
neil davudo wrote:
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
Did you even try searching for files with nio in the name? I really don't
see why you expect me to do this for you.
Mark
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
TIA
Neil
markt-2 wrote:
neil davudo wrote:
Where can I find the source code for the NIO connector that uses the
CometProcessor?
http://tomcat.apache.org
Mark
for the NIO connector that uses the
CometProcessor?
http://tomcat.apache.org
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
this will be resolved.
Regards,
-Emile
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Monday, February 25, 2008 5:57 PM
To: Tomcat Users List
Subject: Re: NIO connector under heavy load drops incoming requests?
you don't need four (4) acceptor threads
On Thu, Oct 25, 2007 at 12:19 PM, Filip Hanik - Dev Lists devm wrote:
browser don't work the way you might it expect to, firefox for example,
will not display anything until the entire request is complete. so the
chat example is no good that way.
write a client application for your
Hello everyone,
We have a high load environment where we are running tomcat 5.5.15
successfully. We are interesting in reducing the system CPU load and
switching to Tomcat 6 with NIO, but so far have run into a few issues.
After trying out the patch Filip recommended
Actually I've seen something like this. I'm under a lot of pressure to
get something out so I haven't investigated it further, but what seemed
to be happening is that if the client slowed down the NIO connector was
throwing a SocketTimeout. I tried messing about with the timeout
settings
you don't need four (4) acceptor threads, turn that to one (1)
also, you omited the most interesting stack trace :)
Filip
Emile Litvak wrote:
Hello everyone,
We have a high load environment where we are running tomcat 5.5.15
successfully. We are interesting in reducing the system CPU load
Alan Chaney wrote:
Actually I've seen something like this. I'm under a lot of pressure to
get something out so I haven't investigated it further, but what seemed
to be happening is that if the client slowed down the NIO connector was
throwing a SocketTimeout. I tried messing about
Where can I find the source code for the NIO connector that uses the
CometProcessor?
TIA
Neil
--
View this message in context:
http://www.nabble.com/NIO-connector-source-code-tp15621736p15621736.html
Sent from the Tomcat - User mailing list archive at Nabble.com
neil davudo wrote:
Where can I find the source code for the NIO connector that uses the
CometProcessor?
http://tomcat.apache.org
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL
]
Sent: Friday, February 01, 2008 6:45 AM
To: Tomcat Users List
Subject: Re: NIO connector
hi Filip,
Still no success there ... I think I'm missing something fundamental.
Just in case anyone is interested, I'm running Tomcat 6.0.13, JDK
1.6.0_04, with libnative for the APR connector. I'm going
public Connector createConnector(String address, int port,String protocol)
set org.apache.coyote.http11.Http11NioProtocol as the protocol value
should work
Filip
brien colwell wrote:
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using Tomcat embedded, so I have an Engine instance,
from which I have a Session object. Can anyone take me from there?
Thanks
use
public Connector createConnector(String address, int port,String protocol)
set org.apache.coyote.http11.Http11NioProtocol as the protocol value
should work
Filip
brien colwell wrote:
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using
brien colwell wrote:
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using Tomcat embedded, so I have an Engine instance,
from which I have a Session object. Can anyone take me from there?
Thanks
,String protocol)
set org.apache.coyote.http11.Http11NioProtocol as the protocol value
should work
Filip
brien colwell wrote:
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using Tomcat embedded, so I have an Engine instance
I am trying to use NIO connector for getting comet chat example work.
Here is what I have in server.xml. I commented out original connector on
8080 (as you can see below) and added NIO on port 8080.
!--Connector port=8080 protocol=HTTP/1.1
connectionTimeout=2
that I searched the
forum already but still confused on NIO connector entry in server.xml.
Any ideas?
Thanks,
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
event in that particular case.
However, I can't test it personally, so maybe you can look into
this a
bit deeper (otherwise, most likely Filip will).
Rémy
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR
not going to get an error event in that particular case.
However, I can't test it personally, so maybe you can look into
this a
bit deeper (otherwise, most likely Filip will).
Rémy
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR events
sent after the client disconnect (I guess the connection might timeout
sometime later), but the original problem of 100% CPU usage is gone.
ok, lets put an end to this now
into this a
bit deeper (otherwise, most likely Filip will).
Rémy
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR events
sent after the client disconnect (I guess the connection might timeout
sometime later
maybe you can look into
this a
bit deeper (otherwise, most likely Filip will).
Rémy
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR events
sent after the client disconnect (I guess the connection might timeout
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run into a problem that I hope
you guys can help me with. I'm testing a servlet that looks like this:
public final class QueryEvent extends HttpServlet implements CometProcessor {
public
On 4/6/07, Elias Naur [EMAIL PROTECTED] wrote:
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run into a problem that I hope
you guys can help me with. I'm testing a servlet that looks like this:
public final class QueryEvent extends
On 4/6/07, Rémy Maucherat [EMAIL PROTECTED] wrote:
On 4/6/07, Elias Naur [EMAIL PROTECTED] wrote:
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run into a problem that I hope
you guys can help me with. I'm testing a servlet
Elias Naur wrote:
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run into a problem that I hope
you guys can help me with. I'm testing a servlet that looks like this:
public final class QueryEvent extends HttpServlet implements
Elias Naur wrote:
On 4/6/07, Rémy Maucherat [EMAIL PROTECTED] wrote:
On 4/6/07, Elias Naur [EMAIL PROTECTED] wrote:
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run into a problem that I hope
you guys can help me with. I'm testing
On 4/6/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote:
Elias Naur wrote:
On 4/6/07, Rémy Maucherat [EMAIL PROTECTED] wrote:
On 4/6/07, Elias Naur [EMAIL PROTECTED] wrote:
Hi,
I'm experimenting with the new tomcat 6 NIO connector to get a
CometProcessor servlet running. I've run
On 4/6/07, Elias Naur [EMAIL PROTECTED] wrote:
I'm aware that a correct implementation must empty the buffer on a
READ event, but as I stated in the original post, a READ event is
never received (not even when the client forces a disconnect), only
the initial BEGIN event, so had I included a
the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR events
sent after the client disconnect (I guess the connection might timeout
sometime later), but the original problem of 100% CPU usage is gone.
- elias
On 4/7/07, Elias Naur [EMAIL PROTECTED] wrote:
No. Compiling and enabling the APR connector instead of the NIO
connector made the problem go away. There were still no ERROR events
sent after the client disconnect (I guess the connection might timeout
sometime later), but the original problem
101 - 197 of 197 matches
Mail list logo
