[
https://issues.apache.org/jira/browse/RIVER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972552#action_12972552
]
Chris Dolan commented on RIVER-376:
-----------------------------------
For the unchanging subset of information, like hostname, this could simply be a
service attribute.
> Get VM specific information from only a service proxy
> -----------------------------------------------------
>
> Key: RIVER-376
> URL: https://issues.apache.org/jira/browse/RIVER-376
> Project: River
> Issue Type: New Feature
> Reporter: Tom Hobbs
> Assignee: Tom Hobbs
> Priority: Minor
>
> It would be useful, if given a service proxy a caller were able to retrieve
> some useful subset of information about the remote VM in which that proxy
> came from.
> For example, if I had a proxy I might want to know the hostname of the
> machine it came from, or even the amount of memory available to it, memory
> used, number of threads etc. Such information could be made available by
> using JMX, however, this leaves callers having to perform some new kind of
> interrogation on the proxy, rather than just calling methods on it. This
> could lead to additional environment changes or headaches.
> It would be nice to be able to do something like:
> VmAdmin vmAdmin = (VmAdmin) ((Administrable)myProxy).getAdmin();
> vmAdmin.getHostname();
> The underlying implementation of VmAdmin is up for design/debate. This was
> first discussion on the dev mailing list here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201011.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
