[
https://issues.apache.org/jira/browse/ARTEMIS-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016211#comment-18016211
]
Gašper Čefarin commented on ARTEMIS-5633:
-----------------------------------------
[~jbertram] without delving too deep into the jolokia cache - as long as
jolokia does not return all the data that did not change since last time, then
yes, that would be the solution to this as well.
I was, however, thinking about caching this on frontend/browser side.
> Cache "list" request to jolokia
> -------------------------------
>
> Key: ARTEMIS-5633
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5633
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: console-1.2.1
> Reporter: Gašper Čefarin
> Priority: Major
> Attachments: queue.txt
>
>
> I'm referring to the request to URL
> {code:java}
> https://xxx/console/jolokia/?maxDepth=9&maxCollectionSize=50000&ignoreErrors=true&canonicalNaming=false&mimeType=application/json&listCache=true{code}
> with the following request body:
> {code:java}
> {"type":"list"}{code}
>
> and request response (4mb+ in my case) - high level overview:
> {code:java}
> {
> "request": {
> "type": "list"
> },
> "value": {
> "cache": {
> "java.lang:MemoryManager": {},
> "java.lang:MemoryPool": {},
> "java.nio:BufferPool": {}
> },
> "domains": {
> "org.apache.activemq.artemis": {},
> "java.util.logging": {},
> "jdk.management.jfr": {},
> "JMImplementation": {},
> "java.lang": {},
> "com.sun.management": {},
> "hawtio": {},
> "java.nio": {},
> "jolokia": {}
> }
> },
> "status": 200,
> "timestamp": 1755862162
> }{code}
> There's a lot of duplicated info as well. I didn't dig deeper, i'm just
> creating this issue for now. There's also a lot of data for every queue,
> attached in the queue.txt file. Notice all the descriptions as well.
> A more "concise" list of all queues is fetched from jolokia in another
> request, which results in only ~14kb of data in my case.
> The request can take a long time to be processed and/or downloaded.
> I'm not sure where all this info is needed, and if it's needed at all (like
> mentioned, I didn't dig deeper).
> Also notice the argument inside the url:
>
> {code:java}
> listCache=true{code}
> Not sure what this does, maybe it caches the response on jolokia side. The
> client still downloads all the data though.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
