On 18/10/2013 19:37, Mark Thomas wrote:
> On 18/10/2013 13:54, Mark Thomas wrote:
>> On 18/10/2013 12:48, Mark Thomas wrote:
>>> When it goes wrong, the sequence is:
>>> Read result [1]
>>> Read result [48]
>>> Read result [-20014]
>>> 18-Oct-2013 12:23:25.298 SEVERE [http-apr-8443-exec-1]
>>> webs
On 18.10.2013 13:14, Violeta Georgieva wrote:
> The proposed Apache Tomcat 7.0.47 release is now available for voting.
> This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
> Note that use of this functionality requires Java 7.
>
> It can be obtained from:
> https://dist.apa
Sorry, accidentally posted this to USERS, when it should be here in DEV
I am testing what happens when Encode/Decode Exceptions occur during JSR-356
communication and found that in the following code in onMessage, the
((WsSession)session) is NULL. As a result, the actual DecodeException (cause)
> -Original Message-
> From: Niki Dokovski [mailto:nick...@gmail.com]
> Sent: Saturday, October 19, 2013 10:06 AM
> To: Tomcat Developers List
> Subject: Re: websocket connection (at startup) between 2 webapps in same
> Tomcat 7.0.47 instance hangs indefinitely
>
> On Sat, Oct 19, 2013 a
On Sat, Oct 19, 2013 at 4:26 PM, Bob DeRemer wrote:
>
>
> > -Original Message-
> > From: Niki Dokovski [mailto:nick...@gmail.com]
> > Sent: Saturday, October 19, 2013 9:24 AM
> > To: Tomcat Developers List
> > Subject: Re: websocket connection (at startup) between 2 webapps in same
> > Tom
> -Original Message-
> From: Niki Dokovski [mailto:nick...@gmail.com]
> Sent: Saturday, October 19, 2013 9:24 AM
> To: Tomcat Developers List
> Subject: Re: websocket connection (at startup) between 2 webapps in same
> Tomcat 7.0.47 instance hangs indefinitely
>
> On Sat, Oct 19, 2013 at
On Sat, Oct 19, 2013 at 4:20 PM, Niki Dokovski wrote:
>
>
>
> On Sat, Oct 19, 2013 at 12:09 AM, Bob DeRemer
> wrote:
>
>> Hi Guys,
>>
>> ** **
>>
>> In our implementation, we have a gateway app that uses jsr websockets to
>> communication with our main application server. In a small system
On Sat, Oct 19, 2013 at 12:09 AM, Bob DeRemer wrote:
> Hi Guys,
>
> ** **
>
> In our implementation, we have a gateway app that uses jsr websockets to
> communication with our main application server. In a small system, we want
> to run them both on a single Tomcat instance using the same To
Author: rjung
Date: Sat Oct 19 11:32:00 2013
New Revision: 1533732
URL: http://svn.apache.org/r1533732
Log:
Javadoc fixes.
Partial backport of r1531099 from trunk.
Modified:
tomcat/tc7.0.x/trunk/ (props changed)
tomcat/tc7.0.x/trunk/java/org/apache/tomcat/util/net/AprEndpoint.java
Pro
On 18.10.2013 13:14, Violeta Georgieva wrote:
The proposed Apache Tomcat 7.0.47 release is now available for voting.
This release candidate contains JSR-356 Java WebSocket 1.0 implementation.
Note that use of this functionality requires Java 7.
...
The proposed 7.0.47 release is:
[ ] Broken - d
On 16/10/2013 19:21, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC4 are:
> - Stability fixes in the APR/native c
https://issues.apache.org/bugzilla/show_bug.cgi?id=50175
--- Comment #6 from Mark Thomas ---
First of all, the memory leak detection is not going to be disabled. For far
too long Tomcat was being blamed for PermGen based OOME errors triggered by web
application reloads. The leak detection code ha
https://issues.apache.org/bugzilla/show_bug.cgi?id=55674
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=55674
--- Comment #2 from Mark Thomas ---
Whoops, I mean bug 50175.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-uns
https://issues.apache.org/bugzilla/show_bug.cgi?id=55674
--- Comment #1 from Mark Thomas ---
The attribute names and values are logged to assist with the identification of
the cause of the memory leak.
Memory leaks are logged at SEVERE as they represent a serious bug that could
eventually lead t
https://issues.apache.org/bugzilla/show_bug.cgi?id=55675
Mark Thomas changed:
What|Removed |Added
OS||All
Severity|normal
16 matches
Mail list logo