db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Re: JMX Extensions to Derby
Date Thu, 01 Jun 2006 08:51:59 GMT
>>>>>>>>>>>> Ø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)
> - Change dynamic properties (e.g., derby.storage.pageSize)
> - Stop a network server (would require some kind of authorization)
> 
> A question:  How will JMX work in an embedded environment? Will it be 
> possible to connect from another process?  If yes, if yes that 
> introduces security issues that one today does need to address for an 
> embedded configuration.

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.

-- 
Bernt Marius Johnsen, Database Technology Group, 
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway

Mime
View raw message