If we use SelectorThread.stopEndpoint() Grizzly does not stop, it carries on
accepting requests. If we use controller.stop() it looks like Grizzly goes
into a loop, consuming all available CPU.
Mark.
Jeanfrancois Arcand-2 wrote:
>
> Hi Mark,
>
> how do you stop Grizzly? By calling SelectorThread.stopEndpoint()? Let
> me investigate.
>
> A+
>
> -- Jeanfrancois
>
> Mark Hig wrote:
>> Hi,
>>
>> We currently have a new problem in version 1.8.5.4 when trying to stop
>> Grizzly. when connector.stop() is called Grizzly goes into a loop,
>> consuming
>> 99% of the CPU. This used to work correctly in 1.8.3.
>>
>> Any ideas?
>>
>> T.I.A.
>>
>> Mark.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/Cannot-stop-Grizzly-tp19495137p19509312.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.