Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache reporting not OK #54

Open
dizzzz opened this issue Apr 9, 2018 · 1 comment
Open

Cache reporting not OK #54

dizzzz opened this issue Apr 9, 2018 · 1 comment
Labels

Comments

@dizzzz
Copy link
Member

dizzzz commented Apr 9, 2018

I think the numbers should be swapped (left <--> right)

capture

@joewiz
Copy link
Member

joewiz commented Apr 9, 2018

Monex is just passing the values from JMX. See the HTML template code at https://github.com/eXist-db/monex/blob/master/index.html#L299-L301 which pulls CurrentSize and MaxTotal from the JMX report; here is a sample returned on my machine showing CurrentSize > MaxTotal.

<jmx:CacheManager name="org.exist.management.exist:type=CacheManager">
    <jmx:MaxTotal>65536</jmx:MaxTotal>
    <jmx:CurrentSize>3735552</jmx:CurrentSize>
    <jmx:MaxSingle>58982</jmx:MaxSingle>
</jmx:CacheManager>

So perhaps this is actually an issue with eXist's JMX code - a difference in units or order of magnitude generated? I think the relevant code is this: https://github.com/eXist-db/exist/blob/develop/src/org/exist/management/client/JMXClient.java#L119-L147.

@duncdrum duncdrum added the bug label Aug 2, 2018
@triage-new-issues triage-new-issues bot removed the triage label Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants