Description of problem: Cluster monitoring tool is getting http 500 error code after starting browbeat rally session. As a result, the cluster/shard status is not available. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. deploy cluster in scale lab 2. start cluster monitoring tool. All is good. 3. start browbeat rally. Cluster monitoring stops working. Actual results: http 500 error code Expected results: Should be able to see the cluster status. Additional info:
2018-07-27T19:56:48,163 | WARN | qtp1274429340-2676 | HttpChannel | 165 - org.eclipse.jetty.util - 9.3.21.v20170918 | //172.16.0.15:8081/jolokia/read/org.opendaylight.controller:Category=ShardManager,name=shard-manager-config,type=DistributedConfigDatastore org.apache.shiro.session.UnknownSessionException: There is no session with id [706e11e0-e53b-47f7-a7c5-50185ea46a97] at org.apache.shiro.session.mgt.eis.AbstractSessionDAO.readSession(AbstractSessionDAO.java:170) ~[?:?] at org.apache.shiro.session.mgt.DefaultSessionManager.retrieveSessionFromDataSource(DefaultSessionManager.java:236) ~[?:?] at org.apache.shiro.session.mgt.DefaultSessionManager.retrieveSession(DefaultSessionManager.java:222) ~[?:?] at org.apache.shiro.session.mgt.AbstractValidatingSessionManager.doGetSession(AbstractValidatingSessionManager.java:118) ~[?:?] at org.apache.shiro.session.mgt.AbstractNativeSessionManager.lookupSession(AbstractNativeSessionManager.java:148) ~[?:?] at org.apache.shiro.session.mgt.AbstractNativeSessionManager.lookupRequiredSession(AbstractNativeSessionManager.java:152) ~[?:?] at org.apache.shiro.session.mgt.AbstractNativeSessionManager.getHost(AbstractNativeSessionManager.java:237) ~[?:?] at org.apache.shiro.session.mgt.DelegatingSession.getHost(DelegatingSession.java:111) ~[?:?] at org.apache.shiro.session.ProxiedSession.getHost(ProxiedSession.java:93) ~[?:?] at org.apache.shiro.session.ProxiedSession.getHost(ProxiedSession.java:93) ~[?:?]
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2598