>>>at what point does your websocket class extend org.apache.tomcat.
websocket.server.WsFilter
I am not extending the o.a.t.w.s.WsFilter at any point , i am using the
JSR(356) where i only need to define the @ServerEndPoint.
If you look at the 6th observation in
This time to the list...
On 29/05/17 16:49, Bhuvan Gupta wrote:
> Mark,
>
>>> Explicitly declare Tomcat's WebSocket filter and ensure it is the first
> filter in the processing chain.
> Can you please give a sample , how to create such filter.
>
> I looked into the documentation , but cant find
Hello Chris,
Thanks for the valuable input, that helps!! We shall go with getting the source
package of Tomcat 7, put them in Tomcat 6 and use the filters of Tomcat 7 in
Tomcat 6.
Can you please let me know from where I can get/download the source package of
Tomcat 7? Also can you please
Hello,
Can you please help in sharing the Source Package file path location in Tomcat
6 and 7 versions?
We need to put the Source Package of Tomcat 7 in Tomcat 6 so that we can use
the security filters of Tomcat 7 in Tomcat 6.
Regards,
Mohammad Nayeem
This
>
> > But now i have websockets, if i connect to ##1 first and i have the end
> > point there
> > Then i add a ##2 version of the context
> > then i guess a new user that opens a websocket will go to ##2
> > but if the existing user does a refresh in the browser then it will also
> > suddenly go
In a similar situation, I do the following :
* go full stateless, use no session ;
* configure WS client to frequently reconnect
* use atmosphere with an internal JMS backend, such as ActiveMQ, to share data
transparently between parallely deployed versions.
With Atmosphere, you avoid losing
Hi,
if i read this:
http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Parallel_deployment
then i see it will go to the "old" version of a war based on session
information
i guess this is jsessionid?
So a refresh in the browser or another request with the jsessionid will go
to the
On 30/05/17 11:09, Johan Compagner wrote:
> Hi,
>
> if i read this:
>
> http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Parallel_deployment
>
> then i see it will go to the "old" version of a war based on session
> information
> i guess this is jsessionid?
>
> So a refresh in the
http://tomcat.apache.org/download-70.cgi
Check the left side menu .. you will find downloads for all versions of
Tomcat.
In the download page you can download binary distributions and also source
code.
"No olvides, no traiciones, lo que llevas bien dentro de ti. No olvides, no
traiciones, lo
On 30/05/17 16:12, Bhuvan Gupta wrote:
> I have added some observation for the issue and observation 5 is interesting
> Basically it shows that web.xml filter are registered before WsFilter can
> register, which creates a problem
>
> Please clarify:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jared,
On 5/29/17 5:03 PM, Jared Walker wrote:
> Hello,
>
> I have a question about how BackupManager enforces or performs
> session replication.
>
> I have added print outs to the serializing methods of an object
> I'm binding to the http
I have added some observation for the issue and observation 5 is interesting
Basically it shows that web.xml filter are registered before WsFilter can
register, which creates a problem
Please clarify:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Einav,
On 5/29/17 2:25 PM, Einav Hollander wrote:
> Are there plans to support the QUIC protocol in Apache Tomcat?
> When?
There are no current plans to support QUIC, but there was a
conversation at ApacheCon about the possibility of supporting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mohammad,
On 5/30/17 2:13 AM, Shaik, Mohammad N. wrote:
> Thanks for the valuable input, that helps!! We shall go with
> getting the source package of Tomcat 7, put them in Tomcat 6 and
> use the filters of Tomcat 7 in Tomcat 6.
>
> Can you please
Another one I failed to send to the list first time around...
On 29/05/17 08:26, Thomas Eliassen wrote:
> Hi,
>
> Since https://bz.apache.org/bugzilla/show_bug.cgi?id=60718 (r1783148 in
> tc8.5.x), ClientAbortExceptions are logged in the access log as status 500,
> changed from the previous
15 matches
Mail list logo