Re: HttpSessionBindingListener details

Right, makes sense. Thank you. On Thu, Feb 5, 2015 at 10:21 AM, Konstantin Kolinko wrote: > 2015-02-05 21:07 GMT+03:00 Igor Urisman : > > Hello, folks. > > > > I can't seem to find a good solution for the following problem. I have > an > > object that i

HttpSessionBindingListener details

Hello, folks. I can't seem to find a good solution for the following problem. I have an object that is added to the HTTP session via the setAttribute() method. The object implements the HttpSessionBindingListener interface and its valueUnbound() method is dutifully called by the contained at the

Re: Java to JavaScript RMI framework available.

. Not on the immediate roadmap, though. -Igor. > > On 31 December 2013 01:55, Igor Urisman wrote: > > > Folks, > > > > I needed to write this for something I am working on and thought there > > might be a wider audience for it. > > Tomcat 8 su

Java to JavaScript RMI framework available.

Folks, I needed to write this for something I am working on and thought there might be a wider audience for it. Tomcat 8 supports standard compliant Websockets, which provide convenient asynchronous full-duplex server to client data transport. The framework I am offering builds on top of that a fe

Re: Minor grammar glitch in a Websocket exception message.

Precisamente. On Fri, Dec 13, 2013 at 3:11 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 12/12/13, 4:43 PM, Mark Thomas wrote: > > On 12/12/2013 06:35, Igor Urisman wr

Minor grammar glitch in a Websocket exception message.

As seen in 8.0.0 RC5: java.lang.IllegalStateException: javax.websocket.DeploymentException: Multiple Endpoints may not be deployed to using the same path [/conntestCloseEndpoint] IMHO, the message can't make up its mind between "to the same path" and "using the same path". -Igor.

Re: setting the text or binary buffer size for websockets

Upgraded my environment to 8RC5 and this feature works for me. Don't know how much help this is, but here's my deployment descriptor: http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://ja

Re: setting the text or binary buffer size for websockets

Johan, What you've described is exactly what works for me. But I am still on RC1. -Igor. On Sat, Nov 16, 2013 at 6:12 AM, Johan Compagner wrote: > sorry, mail did go to soon... > > I do this in the web.xml (directly in the web-app tag) > > > org.apache.tomcat.websocket.textBufferSize >

Re: Servlet init method called multiple times

Print the call stack from a subsequent init()? On Wed, Oct 23, 2013 at 8:33 AM, Richard Pierce < rpie...@empoweredbenefits.com> wrote: > Hey Chris. I wish it was, that would be an easy fix. It's not- grepped the > whole codebase for it, and visually inspected these servlets. > > -Richard > > > >

Re: WebSocket message size limits

i Dokovski wrote: > On Tue, Sep 24, 2013 at 8:15 AM, Igor Urisman >wrote: > > > Thanks again, Mark, for the quick turnaround. > > Which of the 5 parameters on this page would be responsible for changing > > the 125-byte max whole text message size? > > > > Mark

Re: WebSocket message size limits

Thanks again, Mark, for the quick turnaround. Which of the 5 parameters on this page would be responsible for changing the 125-byte max whole text message size? -Igor. On Mon, Sep 23, 2013 at 9:07 AM, Mark Thomas wrote: > On 23/09/2013 08:44, Igor Urisman wrote: > > Thanks for the spe

Re: WebSocket message size limits

e use case. If there is a way to change the default min size of a whole message, that would certainly be the way to go,---another right for you. There's only one problem: I don't know how. Do you? -Igor. On Mon, Sep 23, 2013 at 3:39 AM, Mark Thomas wrote: > On 22/09/2013 21

Re: WebSocket message size limits

} } } } Thanks, -Igor. On Wed, Sep 18, 2013 at 1:12 AM, Mark Thomas wrote: > On 18/09/2013 06:19, Igor Urisman wrote: > > Dear All, > > > > I am looking for help in understanding why the size of the inbound > > WebSocket message is limited to

WebSocket message size limits

Dear All, I am looking for help in understanding why the size of the inbound WebSocket message is limited to 125 bytes. I realize that this may not even be the right place for my question, but am still hoping for a clue. >From looking at the RFC 6455, Sec. 5.2 Base Framing Protocol, I am making

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

I couldn't agree more. WebSocket is provided by the container. But the time any app code gets to run, Spring of Fall, container ought to be done. -Igor. On Fri, Sep 13, 2013 at 10:38 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA

8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

Dear all, It appears that if I obtain the ServletContext object via Spring's WebApplicationInitializer mechanism, it is not yet seeded with the WebSocket ServerContainer object. Alt

Re: 8.0.0-RC1: WebSocket Exception

Right on. Thank you both, Mark and Niki. -Igor. On Sun, Sep 1, 2013 at 3:00 AM, Mark Thomas wrote: > On 31/08/2013 02:40, Igor Urisman wrote: > > That's correct. I call close() inside onOpen(). You correctly call > > onClose() on the endpoint as well, so my code is hap

Re: 8.0.0-RC1: WebSocket Exception

ntics, perhaps you ought to throw an exception in my thread when I call close() inside onOpen()? Thanks! -Igor. On Fri, Aug 30, 2013 at 6:12 PM, Niki Dokovski wrote: > On Sat, Aug 31, 2013 at 12:33 AM, Igor Urisman >wrote: > > > Dear all, > > > > Getting the followin

8.0.0-RC1: WebSocket Exception

Dear all, Getting the following exception with none of my code on the stack: SEVERE: Error reading request, ignored java.lang.IllegalStateException: The WebSocket session has been closed and no method (apart from close()) may be called on a closed session at org.apache.tomcat.websocket.WsSess

A Couple of 8.0.0 WebSocket Questions

Dear all, 1. I see how to close a session from either end of the connection. That, of course, leaves the underlying endpoint intact. Is there a way to un-deploy an entire server endpoint so that no new connections can be made to it? If so, will it close existing sessions? 2. Is there a way to q

Re: 8.0.0 Problems With javax.websocket.*

Martin, I can't because the mailing list will strip the attachment. Please suggest a way to submit a case. -Igor. On Tue, Aug 6, 2013 at 12:21 PM, Martin Grigorov wrote: > Hi Igor, > > Send this message to Tomcat's users mailing list. > > > On Tue, Aug 6, 2013 at

8.0.0 Problems With javax.websocket.*

Dear all, I am running into snags with the new JEE7 compliant implementation of Websockets in 8.0.0-RC1. What's the right way to pass on the test cases? -Igor.

Re: Tomcat Websocket Implementation

> > On Aug 2, 2013, at 12:05 PM, Igor Urisman wrote: > > > >> Dear all, > >> > >> I'm looking into a solution that will make extensive use of websockets. > >> Details are unimportant, but here's the question that I'd like to have > so

Tomcat Websocket Implementation

Dear all, I'm looking into a solution that will make extensive use of websockets. Details are unimportant, but here's the question that I'd like to have some insight into. The current implementation (official example

Re: Resource management in new Tomcat JDBC connection pool.

gt;for > a bug in the current Tomcat version and its workaround. This seems to > affect MySQL primarily. > > Regards, > Bertrand > > > On 10/04/2013 4:05 PM, Igor Urisman wrote: > >> Hello, >> >> The new Tomcat 7 JDBC >> pool<http://people.apache

Resource management in new Tomcat JDBC connection pool.

Hello, The new Tomcat 7 JDBC poolis quite new and not much has been written on it yet. Has anyone looked it how well it manages underlying resources, both in java domain and in the database? More specifically, what happens when I call Co