[
https://issues.apache.org/jira/browse/SOLR-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420120#comment-15420120
]
Alexandre Rafalovitch commented on SOLR-9383:
---------------------------------------------
So, the root cause here is SystemInfoHandler that looks for various optional
system MBeans and populates them into the property map as is.
So, we can see that [IBM
MBean|http://www.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.api.60.doc/com.ibm.lang.management/com/ibm/lang/management/OperatingSystemMXBean.html]
has a different set of property names from the [generic and Unix
one|https://docs.oracle.com/javase/7/docs/jre/api/management/extension/com/sun/management/OperatingSystemMXBean.html]
directly from Sun/Oracle. (Javadoc references are just samples, but
representative).
The question is: do we normalize this naming discrepancy on the server side so
any call for that (and other similar) naming mismatches only need to know about
Sun naming version (e.g. API client). Or do we handle it only when we process
it for display purposes on the Admin UI side?
> New Admin UI Dashboard page doesn't show system info and args on IBM JVM
> ------------------------------------------------------------------------
>
> Key: SOLR-9383
> URL: https://issues.apache.org/jira/browse/SOLR-9383
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 5.4, 5.5, 6.0, 6.0.1, 6.1
> Reporter: Colvin Cowie
> Assignee: Alexandre Rafalovitch
> Priority: Minor
> Attachments: index_ibm.har
>
>
> This has the same symptoms as
> [SOLR-7686|https://issues.apache.org/jira/browse/SOLR-7686] (grey boxes for
> Swap Space, JVM-Memory and no Args) but was not fixed by it when using the
> IBM JVM on Windows and Linux.
> Chrome shows this:
> {quote}
> angular.js:11617 TypeError: Cannot read property 'match' of undefined
> at parse_memory_value (index.js:78)
> at index.js:34
> at angular-resource.min.js:33
> at processQueue (angular.js:13193)
> at angular.js:13209
> at Scope.$eval (angular.js:14406)
> at Scope.$digest (angular.js:14222)
> at Scope.$apply (angular.js:14511)
> at done (angular.js:9669)
> at completeRequest (angular.js:9859)
> {quote}
> Which appears to be because the IBM JVM is returning {{totalPhysicalMemory}}
> rather than {{totalPhysicalMemorySize}} as the Oracle JVM does in the system
> response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
