https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #21 from Mark Thomas ---
What you are describing is a Tomcat bug rather than the issue being discussed
here.
Please open a new issue and provide a test case that reproduces the issue with
the latest release of any supported Tomcat
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #20 from Jonathan Leech ---
(In reply to Mark Thomas from comment #19)
> (In reply to Jonathan Leech from comment #18)
> > I'll try again here. The current Tomcat implementation of this API throws
> > IllegalStateException / TEXT_FU
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #19 from Mark Thomas ---
(In reply to Jonathan Leech from comment #18)
> I'll try again here. The current Tomcat implementation of this API throws
> IllegalStateException / TEXT_FULL_WRITING even if the client synchronizes
> access
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #18 from Jonathan Leech ---
I'll try again here. The current Tomcat implementation of this API throws
IllegalStateException / TEXT_FULL_WRITING even if the client synchronizes
access to the methods and / or ensures that the last mes
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #17 from Remy Maucherat ---
(In reply to Lukas Lieb from comment #16)
> So my question is more is there anything planed or an open enhancement
> request to change this?
As Mark said: "You'll have to take up your concerns over the A
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #16 from lukas.l...@axonivy.com ---
Hi all
I've run currently in the same problem with Tomcat 9.0.63.
In my case there are not really concurrent calls but sometimes multiple calls
shortly after each other, which also can result in
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
Ryan changed:
What|Removed |Added
CC||ryan.slomin...@gmail.com
--
You are receiving
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #15 from Mark Thomas ---
You'll have to take up your concerns over the API with the WebSocket EG.
Although given there has been no WebSocket activity at all for Java EE 8 that
might be a slow process.
Tomcat's starting position is
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #14 from Jonathan Leech ---
synchronizing on session as suggested doesn't appear to be sufficient to
prevent the IllegalStateException, although it may help reduce the frequency.
How is an API that can't be successfully used not bro
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #13 from a...@bgprotect.com ---
I've ran into this issue too and I must say that although tomcat's current
behavior doesn't directly contradict the standard, it's very unexpected and
goes against simple common sense. This is an async
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #12 from balusc ---
Just in case, I investigated this issue for JSF and OmniFaces
too. This threadsafety problem doesn't occur on Jetty, Undertow
(WildFly) nor Tyrus (GlassFish/Payara). It occurs on Tomcat only.
Work around was t
https://bz.apache.org/bugzilla/show_bug.cgi?id=56026
lijia changed:
What|Removed |Added
CC||walnutpri...@gmail.com
--
You are receiving t
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #11 from Mark Thornton ---
Some emails amongst the expert group doesn't constitute information of which
users could be expected to be aware. Is this really the only place that the
intent is described?
--
You are receiving this
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Mark Thornton changed:
What|Removed |Added
CC||mthorn...@optrak.com
--
You are r
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #10 from Mark Thornton ---
It may be worth noting that the Tyrus 1.5 implementation does appear to be
thread safe. Even arbitrary mixtures of Basic and Async sends work as one might
expect: all messages are delivered without err
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #9 from Simone Bordet ---
(In reply to Sebb from comment #8)
> Would it be worth updating the Javadoc to make this restriction explicit?
Would not that require a maintenance review of the specification via the JCP,
since Javado
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #8 from Sebb ---
(In reply to Mark Thomas from comment #1)
> I have some sympathy with this view. Given that the Javadoc for
> RemoteEndpoint.Basic explicitly states that concurrent attempts to send
> messages are not allowed an
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #7 from Mark Thomas ---
You are equating the complexity of implementing buffering for a single
application with known constraints and the complexity of implementing a general
buffering solution appropriate for all applications w
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #6 from Simone Bordet ---
Konstantin, thanks for your comments.
The "tricky buffering requirements" is actually a quote from the expert group.
Given how simply you have implemented these "tricky buffering requirements", it
is
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #5 from Konstantin Preißer ---
Hi Simone,
(In reply to Simone Bordet from comment #2)
> Mark, thanks for your comments.
>
> I am frankly surprised that an expert group states that:
>
> "[async writes] should not be permitted
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #4 from Remy Maucherat ---
Feedback and comments on the specification should be sent to the Websockets EG.
--
You are receiving this mail because:
You are the assignee for the bug.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
--- Comment #3 from Simone Bordet ---
Remy, can I have a comment from you too, since you re-closed this issue as
invalid ?
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
---
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Remy Maucherat changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Simone Bordet changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALI
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=56026
ckell...@timocom.com changed:
What|Removed |Added
CC||ckell...@timocom.com
--
You
26 matches
Mail list logo
