Phoenix is no longer supported.
The product has been replaced by a new container named Merlin. An example of Merlin based deployment of James has just been committed to the James CVS (earlier today). Unfortunately there is no released version of James - however, getting James up and running in Merlin is dead simple (in fact I've just fired up James and I'm sending this message using the latest build). If your interested in resolving your problem though migration - yell out and I'll you to the resources you need. Cheers, Steve. > -----Original Message----- > From: Marco Castillo [mailto:[EMAIL PROTECTED] > Sent: 28 August 2004 17:39 > To: [EMAIL PROTECTED] > Subject: Problems with Phoenix 4.0.1 > > Hi there, I have a problem with Phoenix 4.0.1 > I'm running debian 3.0 Release 1 on a powerpc machine. 'cause there isn't > direct support for Java in debian, I'm using Blackdown J2SDK 1.3.1.02b. In > this machine I installed James 2.2.0 which comes with Phoenix 4.0.1. > When I run the startup script, which in turn calls the phoenix.sh startup > script I receive the following exception: > > Using PHOENIX_HOME: /opt/james/james-2.2.0 > Using PHOENIX_TMPDIR: /opt/james/james-2.2.0/temp > Using JAVA_HOME: /usr/lib/j2se/1.3 > Running Phoenix > > Phoenix 4.0.1 > > There was an uncaught exception: > ------------------------------------------------------- > --- Message --- > org/apache/avalon/phoenix/components/manager/AbstractSystemManager.dispo se > --- Stack Trace --- > java.lang.AbstractMethodError: > org/apache/avalon/phoenix/components/manager/AbstractSystemManager.dispo se > at > org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil. ja > va > :251) > at > org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.setupCompo ne > nt > (DefaultEmbeddor.java:532) > at > org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.setupCompo ne > nt > s(DefaultEmbeddor.java:507) > at > org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.initialize (D > ef > aultEmbeddor.java:200) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(Container Ut > il > .java:235) > at > org.apache.avalon.phoenix.frontends.CLIMain.startup(CLIMain.java:194) > at > org.apache.avalon.phoenix.frontends.CLIMain.execute(CLIMain.java:122) > at > org.apache.avalon.phoenix.frontends.CLIMain.main(CLIMain.java:102) > at java.lang.reflect.Method.invoke(Native Method) > at org.apache.avalon.phoenix.launcher.Main.startup(Main.java:94) > at org.apache.avalon.phoenix.launcher.Main.main(Main.java:46) > > ------------------------------------------------------- > The log file may contain further details of error. > Please check the configuration files and restart Phoenix > If the problem persists, contact the Avalon project. See > http://jakarta.apache.org/avalon for more information > > And the log file that was generated has the following information: > INFO 2004-08-28 08:59:13.631 [Phoenix ] (): Logger started > WARN 2004-08-28 08:59:14.104 [Phoenix ] (): Phoenix was not started by > the > daemon thus it will not be possible to restart the JVM via the Management > Interface. > > Does somebody has any clue???, or any idea that could help??? > > Thank you in advance for your kind reply... > > Ing. Marco Antonio Castillo > Chief Design Engineer > Van Der Kaaden IT Consulting > Guatemala, Guatemala C.A. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
