[ 
https://issues.apache.org/jira/browse/SOLR-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Buenemann updated SOLR-4526:
----------------------------------

    Attachment: SOLR-4526.patch

The attached patch makes the dashboard js code less reliant on provided system 
and jvm data by checking for their existance. It also improves the matching of 
load average among operating systems (should now work with Linux, Mac OS X, 
*BSD, Irix, etc.)
                
> Admin UI dependence on UnixOperationSystemMXBean
> ------------------------------------------------
>
>                 Key: SOLR-4526
>                 URL: https://issues.apache.org/jira/browse/SOLR-4526
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 4.1
>         Environment: Oracle Corporation OpenJDK 64-Bit Server VM (1.7.0_15 
> 23.7-b01)
>            Reporter: Shawn Heisey
>            Assignee: Stefan Matheis (steffkes)
>         Attachments: built-in-jetty8.png, SOLR-4526.patch, ubuntu-jetty6.png
>
>
> A user on IRC was having trouble getting file descriptor counts and JVM 
> memory usage in the admin UI, but it worked perfectly fine on another system. 
>  The problem system uses OpenJDK, the other one uses the Apple JDK.  The user 
> had tracked it down to an exception while trying to get open file descriptor 
> info.
> Looking in the SystemInfoHandler.java file, I see a comment reference to 
> com.sun.management.UnixOperatingSystemMXBean at the point where it is getting 
> file descriptor info.  A little extra searching turned up ZOOKEEPER-1579 
> which refers to HBASE-6945, the same problem with OpenJDK.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to