On Mon, May 18, 2015 at 2:24 PM, Mark Thomas wrote:
> On 18/05/2015 13:40, Stephen Dawkins wrote:
>> On Mon, May 18, 2015 at 12:30 PM, Mark Thomas wrote:
>
> Bingo.
>
> I think I have found the problem (well, a problem anyway). It looks like
> there is a bug in javame
On Mon, May 18, 2015 at 12:30 PM, Mark Thomas wrote:
> Thanks. That rules out some possibilities for application error.
>
> When you get two threads writing to the response, if would be useful to
> know which of the following those threads are:
> - the Tomcat thread that handled the original reque
On Mon, May 18, 2015 at 12:00 PM, Mark Thomas wrote:
> On 18/05/2015 11:50, Stephen Dawkins wrote:
>> On Mon, May 18, 2015 at 11:22 AM, Mark Thomas wrote:
>>> On 18/05/2015 10:31, Stephen Dawkins wrote:
>>>> Does anyone have any suggestions as to where the issue c
On Mon, May 18, 2015 at 11:22 AM, Mark Thomas wrote:
> On 18/05/2015 10:31, Stephen Dawkins wrote:
>
> Tomcat will call flushBuffer() internally.
>
> Tomcat does re-use Request/Response objects so if a reference is
> accidentally retained to one of them you can see this is
Hi
I have an application that uses embedded Tomcat (8.0.22) to serve SOAP
services. I've recently attempted to add javamelody[1] to the app to gather
some stats, however I've run into an issue where occasionally the response
is incorrect, mostly it just duplicates response, although sometimes it's
