I think what we are looking for is here :
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#NIO_specific_configuration
useComet (bool)Whether to allow comet servlets or not. Default value is true.
I set connetor attribute to false useComet to false,but did not work as I
expected,
still
Thanks for clarifying it. That helped.
--
View this message in context:
http://tomcat.10.n6.nabble.com/Embedded-Tomcat-6-7-logging-to-file-tp4984104p4984163.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
Hi Christopher,
I've found a solution to my problem although I believe it's more accurate
to say I guessed it :) Maybe you'll be able to explain it to me. Here is
the complete code:
Tomcat tomcat = new Tomcat();
tomcat.setBaseDir(baseDir);
tomcat.getConnector().setPort(8080);
tomcat.getServer().s
In http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
you can read about pollerThreadCount and useComet flags for the APR
implementation.
You don't need Comet unless you applications specifically are using it, most
likely they are not.
Filip
- Original Message -
> From: "Jeffrey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 7/16/12 9:54 AM, CRANFORD, CHRIS wrote:
> When upgrading from 7.0.26 to 7.0.29, MyEclipse cannot start the
> Tomcat instance without reaching an OutOfMemoryError exception that
> results from a "GC overhead limit exceeded" when Tomcat begins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 7/16/12 10:01 AM, Jeffrey Janner wrote:
> Thanks Chris, I'd seen a lot of traffic on the topic over the
> years, so knew someone had real-world experience on the subject.
> I'll check out what you did a little further. Of course, thinking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander,
On 7/17/12 6:42 AM, Alexander Shutyaev wrote:
> Ok, I've figured out it DOES listen on ALL addresses no matter
> what hostname is, but somehow requests only succeed if they have
> the hostname matching with the one set by Tomcat.setHostname
Ok, I've figured out it DOES listen on ALL addresses no matter what
hostname is, but somehow requests only succeed if they have the hostname
matching with the one set by Tomcat.setHostname(...) (which is localhost by
default). I'm not sure where the requests fail, but they do.
2012/7/17 Alexander
the Image did not show .so I paste what is in that image
Daemon Thread [http-apr-80-Poller-1] (Running)
Daemon Thread [http-apr-80-Poller-0] (Running)
Daemon Thread [http-apr-80-Poller-2] (Running)
Daemon Thread [http-apr-80-Poller-4] (Running)
Daemon Thread [http-apr-80-Poller-3]
Maybe I am wrong, I saw that tomcat 7.0.28 (didnt notice other version) create
Threads like in the picture, I thought that tomcat created thread named
http-apr-80-cometPoller-1.
if these threads are not created for web-socket ,then what is it for? I am
confused.
_
Hi all!
I've embedded tomcat 7 using org.apache.catalina.startup.Tomcat class. It
seems that by default it listens on "localhost". I've noticed there is a
method org.apache.catalina.startup.Tomcat.setHostname(String) which I can
use to change this. But I can't find how I can tell tomcat to listen
2012/7/17 Abduxkur Ablimit :
> By disable tomcat comet, I dont want tomcat create thread for web-socket,
> how do I do that?
There is no such thing as "thread for web-socket".
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.a
While latest websocket protocol is supported in Tomcat, a lot of
browsers out there are using older versions of the protocol. It may take
them years to phase out.
Considering this, I also need to support older protocol versions. I am
not sure how to do this.
One route is I install jwebsock
Yes, I have also increased the one in the server.xml of te tomcat instance.
Haven't tried using it as an http just to see if its going to make a
difference. I'm going to ask the users. Thanks.
On 17/07/2012, at 4:59 PM, Rainer Jung wrote:
> On 17.07.2012 06:15, ann ramos wrote:
>> Thanks Tim
By disable tomcat comet, I dont want tomcat create thread for web-socket,
how do I do that?
Best Regards,
Abduxkur.Ablimit
On 17.07.2012 06:15, ann ramos wrote:
Thanks Tim for your quick reply.
I have already increased the max_packet_size to the maximum allowable value way
way before and it still comes up:
worker.wlb.max_packet_size=65536
You need to increase the size on the Tomcat side to.
Just the "Request
16 matches
Mail list logo
