ou are using only single ODL controller and not a cluster
>>> – right ?
>>>
>>>
>>>
>>> Regards
>>>
>>> Muthu
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>
;
>
>
>
>
>
>
> *From:* openflowplugin-dev-boun...@lists.opendaylight.org [mailto:
> openflowplugin-dev-boun...@lists.opendaylight.org] *On Behalf Of *Santosh
> Singh
> *Sent:* Friday, February 17, 2017 1:08 PM
> *To:* Anil Vishnoi <vishnoia...@gmail.com>
> *Cc:*
ugin-dev@lists.opendaylight.org
Subject: Re: [openflowplugin-dev] opendaylight [ Lithuim ] crashes due to
"java.lang.OutOfMemoryError: unable to create new native thread"
My guess is that because of the connection flapping it ends up submitting many
FutureCallback for setRole future. And i
gin-dev-boun...@lists.opendaylight.org [mailto:
> openflowplugin-dev-boun...@lists.opendaylight.org] *On Behalf Of *Santosh
> Singh
> *Sent:* Friday, February 17, 2017 1:08 PM
> *To:* Anil Vishnoi <vishnoia...@gmail.com>
> *Cc:* openflowplugin-dev@lists.opendaylight.org
ct: Re: [openflowplugin-dev] opendaylight [ Lithuim ] crashes due to
"java.lang.OutOfMemoryError: unable to create new native thread"
Hi Anil ,
Thanks for your response ..
We are running with following memory option , I think which is sufficient for
ODL instance having 150 OF conne
Hi Anil ,
Thanks for your response ..
We are running with following memory option , I think which is sufficient
for ODL instance having 150 OF connection.
-Xms128M -Xmx31393m -XX:MaxPermSize=15696m
Any thoughts on this ??
We would be trying to recreate this issue in order to get heap dump
Hi Santosh,
Looks like your controller crashed while spawning a new native JVM thread,
because your JVM Is out of native heap space.
Can you increase your native heap space and see if you still hit the issue
(it might take longer to recreate the issue). Meanwhile if you have the
heapdump, please
Hello openflowplugin developers ,
I have been using lithium release of opendaylight. We are seeing ODL
crashes with error mentioned in the subject line , when we test the
scenario of frequent connection flap .
If this issue has been already addressed as part of the latest release ,
could
