Noel J. Bergman wrote:
Well, we need to shutdown the container/application. What is the
recommended means?
Hopefully there is a means to do this from outside of James.
We provide a telnet admin interface. You've never seen it? Ideally we can replace it with a JMX interface.
- shutdown: take down the entire system
That's the topic at hand.
- redeploy: decommission and recommission incorporating
any changes to deployment information and/or resoruces
As far as I know, Phoenix doesn't support that idea, but we'd like to be able to restart parts of James with a new configuration without having to shut it down. For example, if I've changed the mailet configuration, I'd like to restart the spooler. I should not have to shutdown the SMTP server, since it should not be impacted.
Just for reference ...
I am working on JMX stuff right now. My objective is to provide fine-grain redeployment of an appliance inside a container. This means that all components would be redeployable (without changing existing component code). Given a hierachy of managers this would enable selective subsystem redeployment. But this will not bne available tommorow - things are currently focussing on sensible and intiative presentation of JMX information.
Cheers, Steve.
Phoenix has a JMX access point and I belive that MX4J supports SSL based
connections (going on memory here) - so in pricipal this should be
possible.
We disabled MX4J when we found out that it was permitted unsecured administration. I'd like to re-enable. Hopefully Steve will help us get that all square.
--- Noel
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
