Logging this is really of little use. There has to be a timeout that fails deployments so that error level logging can be captured and used as a trigger to page an admin if desired. Having the the state of a deployment including its dependencies available through jmx would be more useful for debugging than logging.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 8:17 PM Subject: Re: [JBoss-dev] Waiting for classes to appear to deploy > It lets packages deploy successfully in more orders than without it, and > lets you undeploy and redeploy a class without having to undeploy and > redeploy the mbean instances of that class. > > That being said, the "silent" feature we have now is not very helpful. > I've been wondering what a solution might be, and now suggest... > > What if the DeploymentScanner logged all the waiting stuff after every > scan? > > --packages waiting for deployers > --mbeans waiting for their classes > --mbeans waiting for their dependencies to be satisfied > > Then you would surely notice if something was awry. > > Comments? > > david jencks _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
