Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
When using the Topology UI sometimes when switching the topology provider an "Error occured. See Karaf.log" Notfiication is shown.
Investigating the log file, reveals this:
Caused by: java.lang.IllegalStateException: Cannot remove from parent when the session is not locked. Furthermore, there is another locked session, indicating that the component might be about to be moved from one session to another.
at com.vaadin.ui.AbstractSingleComponentContainer.removeFromParent(AbstractSingleComponentContainer.java:170)[93:com.vaadin.server:7.2.7]
at com.vaadin.ui.AbstractComponentContainer.addComponent(AbstractComponentContainer.java:207)[93:com.vaadin.server:7.2.7]
at com.vaadin.ui.AbstractOrderedLayout.addComponent(AbstractOrderedLayout.java:90)[93:com.vaadin.server:7.2.7]
at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.wrap(TopologyUI.java:398)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT]
at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.wrap(TopologyUI.java:377)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT]
at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.lambda$getInfoPanelComponents$14(TopologyUI.java:410)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT]
at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider$$Lambda$107/1176880036.apply(Unknown Source)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT]
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)[:1.8.0_45]
There seems to be an issue. This should be investigated.
Having a deeper look at the code the problem is the CommandManager. It is responsible to update the menu bar for all topology ui in the following cases:
Menu item click
New/removed Operation or Command
Whereas the 2nd scenario works, the first does not.
It results in user 1 triggering a ui update on user 2's session. This is what the original exception is expressing.
Jesse White April 21, 2016 at 2:02 PM
It looks like occurs when we try to add a component, which was previously attached to a container, to a new container.
The only component provided by any of the InfoPanelItems that is shared among many containers is the HudDisplay. All of the other components are created on demand.
That said, we should avoid sharing the HudDisplay components as well in order to avoid this.
When using the Topology UI sometimes when switching the topology provider an "Error occured. See Karaf.log" Notfiication is shown.
Investigating the log file, reveals this:
Caused by: java.lang.IllegalStateException: Cannot remove from parent when the session is not locked. Furthermore, there is another locked session, indicating that the component might be about to be moved from one session to another. at com.vaadin.ui.AbstractSingleComponentContainer.removeFromParent(AbstractSingleComponentContainer.java:170)[93:com.vaadin.server:7.2.7] at com.vaadin.ui.AbstractComponentContainer.addComponent(AbstractComponentContainer.java:207)[93:com.vaadin.server:7.2.7] at com.vaadin.ui.AbstractOrderedLayout.addComponent(AbstractOrderedLayout.java:90)[93:com.vaadin.server:7.2.7] at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.wrap(TopologyUI.java:398)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT] at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.wrap(TopologyUI.java:377)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT] at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider.lambda$getInfoPanelComponents$14(TopologyUI.java:410)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT] at org.opennms.features.topology.app.internal.TopologyUI$InfoPanelItemProvider$$Lambda$107/1176880036.apply(Unknown Source)[104:org.opennms.features.topology.app:18.0.0.SNAPSHOT] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)[:1.8.0_45]There seems to be an issue. This should be investigated.