Again there is a need for logical service aliases to avoid this. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 27, 2003 10:13 AM Subject: RE: [JBoss-user] Migration to JBoss 3.0.6: farming deployment fails during start > Sh*t, who has modified this name?!? > > The change is crap as it makes the farm service fail but it is good as if we > can have a single name for both jetty/tomcat it is easier to write mbean > dependencies. > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de Vladyslav > > Kosulin > > Envoye : lundi, 27 janvier 2003 18:50 > > A : [EMAIL PROTECTED] > > Objet : Re: [JBoss-user] Migration to JBoss 3.0.6: farming deployment > > fails during start > > > > > > Sacha Labourey wrote: > > > Can you make sure you have all these mbeans started: > > > jboss:service=DefaultPartition > > > jboss.ejb:service=EJBDeployer > > > jboss.web:service=JBossWeb > > > jboss.system:service=MainDeployer > > > > > > (in http://localhost:8080/jmx-console/ for example) > > > > > > I suspect: > > > - either jbossweb (aka jetty) is not started > > > - you have not started the all configuration (i.e. > > DefaultPartition is not > > > there) => "run -c all" > > > > I found the cause: "JBossWeb" is obsolete name now. > > Starting with JBoss 3.0.6 Jetty is being deployed as "WebServer" instead > > of "JBossWeb". > > After I made the corresponding changes to farm-service.xml, it starts > > O.K. Can somebody commit this changes to CVS? > > > > Vlad ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
