I suggest that the distributed services level should be optional. Only
the agent level and the instrumentation level should be there by
default. This will also comply with the current Derby architecture
with embedded vs. the network server.
Let me restate to make sure I understand what
Sanket Sharma wrote:
I would also appreciate your suggestions on features the community would
like to see being implemented as JMX extensions.
On the top of my head:
- Performancs statistics (e.g., transactions committed/aborted per second)
- Change dynamic properties (e.g.,
Øystein Grøvlen wrote (2006-06-01 09:24:18):
Sanket Sharma wrote:
I would also appreciate your suggestions on features the community would
like to see being implemented as JMX extensions.
On the top of my head:
- Performancs statistics (e.g., transactions committed/aborted per second)
On Jun 1, 2006, at 1:51 AM, Bernt M. Johnsen wrote:
Øystein Grøvlen wrote (2006-06-01 09:24:18):
Sanket Sharma wrote:
I would also appreciate your suggestions on features the
community would
like to see being implemented as JMX extensions.
On the top of my head:
- Performancs
Hey everyone...
I´m a google SOC student assigned the task of adding JMX extensions to
Derby! Before I actually start working on my project, I just
thought of dropping a ´lil Hi to the community :-)
I would also appreciate your suggestions on features the community would like to see being
