llation as mentioned
earlier, but other users could also suffer from this.
How do we proceed?
Best regards,
Lars Engholm Johansen
On Wed, Nov 12, 2014 at 12:15 PM, Mark Thomas wrote:
> On 10/11/2014 09:57, Lars Engholm Johansen wrote:
> > Hi Mark,
> >
> > I looked in
.
This was due to bug https://issues.apache.org/bugzilla/show_bug.cgi?id=54716,
that I can see should be fixed long time ago (thanks).
Can this cause the selector's keyset to be accessed by more than one thread?
Best regards,
Lars Engholm Johansen
On Mon, Oct 6, 2014 at 2:14 PM, Mark Thomas
le
for two weeks now.
Best regards to all,
Lars Engholm Johansen
On Thu, Sep 18, 2014 at 7:03 PM, Filip Hanik wrote:
> Thanks Lars, if you are indeed experiencing a non caught error, let us know
> what it is.
>
> On Thu, Sep 18, 2014 at 2:30 AM, Lars Engholm Johansen
> wrote:
en Tomcat starts. and
> > a stack over flow on a processing thread should never affect the
> > poller thread.
>
> OP reported in the initial post that the thread had disappeared:
>
> On 6/16/14, 5:40 AM, Lars Engholm Johansen wrote:
> > We have no output in tomcat or our
6 bit short count minus some reserved
> addresses. So your system should become unresponsive, you've run out of
> ports (the 16 bit value in a TCP connection).
>
> netstat -na should give you your connection state when this happens, and
> that is helpful debug information.
>
dump with a dump from a
>> newly launched Tomcat:
>> One of http-nio-80-ClientPoller-0 or http-nio-80-ClientPoller-1 is
>> missing/has died.
>>
>> We have observed this problem at least since Tomcat 7.0.48 and can not
>> find
>> indications in Tomca
his problem at least since Tomcat 7.0.48 and can not find
indications in Tomcat 7.0.x change logs that it should have been fixed in
newer releases.
Any help or advises are appreciated,
Best regards,
Lars Engholm Johansen
Our connector configuration:
