Alexis Agahi wrote:
On Tuesday 07 October 2003 19:08, Noel J. Bergman wrote:
Steve,
Merlin doesn't have support for JMX and one of the goals on the
James roadmap is to improve monitoring / management via JMX.
Quite correct. However, today James does use better logging than Merlin supports, and does not use JMX. Today. So the logging is the primary blocking factor, because we'd have to give something up to use Merlin.
JMX is on the work list for Merlin. Perhaps Stephen would use James as a
test bed when implementing JMX. That could lead towards a community effort
to do some very nice JMX within Merlin and James.
Ok so what is the next move?
Should we wait for Merlin 3.1 featuring JMX & extended logging? (BTW I could help Steve on this task to boost the release cycle)
My short term preferences would be to focus engeries on getting the logging subsystem upgraded so that we have a viable migration path for James.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
