Hi
Check to see if the WebSocket examples that ship with Tomcat work with
your configuration. If they don't compare the differences between the
default configuration and you configuration to and find the change that
breaks stuff.
First, thanks for the reply.
I downloaded tomcat 7.0.32
On 10/10/2012 17:41, Steffen Heil (Mailinglisten) wrote:
Hi
Check to see if the WebSocket examples that ship with Tomcat work with
your configuration. If they don't compare the differences between the
default configuration and you configuration to and find the change that
breaks stuff.
Hi
I just took a look at this. The examples work out of the box for HTTPS
with
BIO but not with NIO. This looks like a Tomcat bug at this point.
I'll take a look.
What would I need to do to switch to BIO for now?
And does Comet work with BIO?
Regards,
Steffen
smime.p7s
Description:
On 10/10/2012 19:51, Steffen Heil (Mailinglisten) wrote:
Hi
I just took a look at this. The examples work out of the box for HTTPS
with
BIO but not with NIO. This looks like a Tomcat bug at this point.
I'll take a look.
What would I need to do to switch to BIO for now?
Change the
Hi
I have a server with several websocket connections.
(Or at least I will have at some time, see thread about ssl problems...)
Now just as in the chat example, I need to send some data from time to time
so some (but not neccessarily all) of those connections.
Now, what happens if one of the
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
I am able to connect from browser to tomcat using non secure WS connection:
ws://127.0.0.1:8080/Myserver
If I switch the connection string to secure protocol
ws://127.0.0.1:8080/Myserver
I get following error. Can somebody confirm if this has been
implemented/known to work? I am using tomcat
On 16/06/2012 20:28, Ravi wrote:
I am able to connect from browser to tomcat using non secure WS connection:
ws://127.0.0.1:8080/Myserver
If I switch the connection string to secure protocol
ws://127.0.0.1:8080/Myserver
That is neither the correct protocol nor the correct port.
I get
Thank you Mark for pointing out the mistake. Following url works
wss://127.0.0.1:8443/Myserver
On 6/16/2012 2:32 PM, Mark Thomas wrote:
On 16/06/2012 20:28, Ravi wrote:
I am able to connect from browser to tomcat using non secure WS connection:
ws://127.0.0.1:8080/Myserver
If I switch
on the connector just like HTTP.
And how to do it?
Use the NIO or APR/native connector and it just works.
Perhaps you can describe more deeply how you handle websockets in regard
of blocking/non blocking and thread handling?
See above. If you want more detail, look at the source code. I am not
going
to use websockets. But now it
would be sad, if I need multiple tomcat instances only for connection
handling although the process handling itself is not very complicated
(cpu and memory intensive).
Thank you,
Chris
are the configuration possibilities for that?
And how to do it?
Perhaps you can describe more deeply how you handle websockets in regard
of blocking/non blocking and thread handling?
Thank you,
Chris
-
To unsubscribe, e-mail: users
/native connector and it just works.
Perhaps you can describe more deeply how you handle websockets in regard
of blocking/non blocking and thread handling?
See above. If you want more detail, look at the source code. I am not
going to translate that into pseudo code for you.
Mark
Hello,
as far I understood, the websocket implementation of tomcat is using one
thread per client.
Is there also a possibility to configure it to use non blocking IO?
Then it should be easier to serve lots of connections without creating
unlimited threads.
Thank you,
Chris
On 31/05/2012 10:02, Christian Finckler wrote:
Hello,
as far I understood, the websocket implementation of tomcat is using one
thread per client.
Is there also a possibility to configure it to use non blocking IO?
No. That has not yet been implemented. It shouldn't be too hard provided
that
fast. Thats why I want to use websockets. But now it
would be sad, if I need multiple tomcat instances only for connection
handling although the process handling itself is not very complicated
(cpu and memory intensive).
Thank you,
Chris
To: Tomcat Users List
Subject: Re: non blocking Websockets?
Am 31.05.2012 11:09, schrieb Mark Thomas:
On 31/05/2012 10:02, Christian Finckler wrote:
Hello,
as far I understood, the websocket implementation of tomcat is using
one
thread per client.
Is there also a possibility
201 - 217 of 217 matches
Mail list logo
