-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.1, jboss-fuse-6.2.1, jboss-fuse-6.3
-
None
-
ALL
- In thread-dump we found that there are multiple JAAS authenticate from Jetty request org.apache.zookeeper.ClientCnxn.submitRequest which might be leading to more resource utilization. It would be better if we can cache the response so that for certain interval cached response can be provided back instead of invoking everytime.
"qtp336363853-369722" prio=10 tid=0x00007f0c38215800 nid=0x2275 in Object.wait() [0x00007f0c6d15b000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1309) - locked <0x00000006b3b6f1e0> (a org.apache.zookeeper.ClientCnxn$Packet) at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1149) at org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:302) at org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:291) at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107) at org.apache.curator.framework.imps.GetDataBuilderImpl.pathInForeground(GetDataBuilderImpl.java:287) at org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:279) at org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:41) at io.fabric8.zookeeper.utils.ZooKeeperUtils.getStringData(ZooKeeperUtils.java:188) at io.fabric8.zookeeper.utils.ZooKeeperUtils.getStringData(ZooKeeperUtils.java:184) at io.fabric8.zookeeper.utils.ZooKeeperUtils.getContainerTokens(ZooKeeperUtils.java:441) at io.fabric8.jaas.ZookeeperLoginModule.initialize(ZookeeperLoginModule.java:78) at org.apache.karaf.jaas.boot.ProxyLoginModule.initialize(ProxyLoginModule.java:76) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
