[
https://issues.apache.org/jira/browse/BROOKLYN-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161377#comment-16161377
]
ASF GitHub Bot commented on BROOKLYN-532:
-----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/815
BROOKLYN-532: karaf separate mgmt init and start
See https://issues.apache.org/jira/browse/BROOKLYN-532. This implements the
last of the suggestions in
https://issues.apache.org/jira/browse/BROOKLYN-532?focusedCommentId=16161370&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16161370
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server
karaf-separate-mgmt-init-and-start
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/815.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #815
----
commit 18ccb58f04de8483371097e7cff77f857234fa62
Author: Aled Sage <[email protected]>
Date: 2017-09-11T14:00:21Z
BROOKLYN-532: karaf separate mgmt init and start
----
> UI / rest api not available after a very long rebind
> ----------------------------------------------------
>
> Key: BROOKLYN-532
> URL: https://issues.apache.org/jira/browse/BROOKLYN-532
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.11.0
> Reporter: Aled Sage
>
> I restarted Brooklyn (in karaf-mode) when it had a huge number of entities
> (approx 50,000). It eventually finished rebinding, but the REST api and
> web-console didn't come up properly.
> The log showed the exception below:
> {noformat}
> 2017-08-31T18:15:49,691 ERROR 15 o.a.a.b.c.BlueprintContainerImpl [rint
> Extender: 1] Unable to start blueprint container for bundle
> org.apache.brooklyn.rest-resources/0.12.0.SNAPSHOT due to unresolved
> dependencies [(objectClass=org.apache.brooklyn.core.mgmt.ShutdownHandler),
> (objectClass=org.apache.brooklyn.core.mgmt.internal.ManagementContextInternal)]
> java.util.concurrent.TimeoutException: null
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:370)
> [15:org.apache.aries.blueprint.core:1.8.2]
> at
> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)
> [15:org.apache.aries.blueprint.core:1.8.2]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
