[
https://issues.apache.org/jira/browse/CASSANDRA-14686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyril Scetbon resolved CASSANDRA-14686.
---------------------------------------
Resolution: Not A Problem
Assignee: Cyril Scetbon
Looking in the cassandra core code, I didn't find any bridge code between the
Jolokia agent and the JMX. I think the issue comes from the agent itself. I'm
gonna look at it and try to find what's going on.
> Jolokia agent not accepting requests during an operation
> --------------------------------------------------------
>
> Key: CASSANDRA-14686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14686
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Cassandra 3.11.2
> Ubuntu Xenial
> Jolokia 1.3.7
> Reporter: Cyril Scetbon
> Assignee: Cyril Scetbon
> Priority: Major
>
> I've noticed that when I run a long operation like a rebuild using Jolokia, I
> can no longer query Jolokia and get a timeout error even when trying to read
> a simple attribute like the Java version in use :
> {code:java}
> jmx4perl http://cassandra-3.11.2:8778/jolokia read java.lang:type=Runtime
> SpecVersion
> ERROR: Error while fetching http://
> cassandra-3.11.2:8778/jolokia/read/java.lang%3Atype%3DRuntime/SpecVersion :
> 408 Got timeout in 180s
> {code}
> I also removed the default flag
> [-XX:+PerfDisableSharedMem|https://github.com/apache/cassandra/blob/cassandra-3.11/NEWS.txt#L769-L771]
> but did not get more luck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
