[
https://issues.apache.org/jira/browse/SOLR-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4526:
---------------------------
Description:
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.
was:
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-6495, the same problem with OpenJDK.
I'm confused: SystemInfoHandler doesn't directly depend on
UnixOperatingSystemMXBean, it uses reflection to ensure that it only calls
methods on the OperatingSystemMXBean if they already exist -- so even if it
isn't a sun JVM, or isn't an UnixOperatingSystemMXBean instance, or is an older
version of UnixOperatingSystemMXBean that doesn't have some of those methods,
it still shouldn't be an error -- at worst those properties just won't be
included in the response.
perhaps the problem is just that that admin UI Javascript assumes those
properties will always be available? (but that wouldn't explain the comment
about "tracked it down to an exception while trying to get open file descriptor
info")
can anyone who can actually reproduce this problem please post the specifics of
the exception they see, or the behavior they see in the admin ui (ie:
screenshot)
> 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
>
> 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]
