[daisy] Problem installing parallel daisy instances
Paul Focke
paul at outerthought.org
Wed Dec 6 07:02:22 CST 2006
On Tuesday 05 December 2006 11:09, Nicolas Cebron wrote:
> I tried to install a second daisy instance, following the description in
> http://www.cocoondev.org/daisydocs-2_0/admin/349.html .
> In the repository installation part, it is stated that:
> =================
> "Now follow the instructions about mail configuration.
>
> When you reach the embedded JMS part (activeMQ) make sure to use the right
> URL :
>
> jdbc:mysql://localhost/activemqalt?characterEncoding=UTF-8
>
> The rest of the steps you can use the defaults if you like."
> =================
>
> I have reached the mail installation part, but was never prompted for the
> embedded JMS part. I followed all other instructions, but
> if I try to start the repository, it fails (see exception report). Does
> anyone have a clue what went wrong and how I can fix this?
> Thanks in advance for your help!
>
> - Nicolas
>
>
> ---- exception report
> ----------------------------------------------------------
> Exception: org.apache.avalon.merlin.KernelException
> Message: Kernel startup failure.
> ---- cause
> ---------------------------------------------------------------------
> Exception: org.apache.avalon.merlin.KernelException
> Message: Cannot deploy application.
> ---- cause
> ---------------------------------------------------------------------
> Exception: org.apache.avalon.activation.LifecycleException
> Message: Unable to create a new component instance in appliance
> [/daisy/repository/fulltextindexupdater] due to a component deployment
> failure.
> ---- cause
> ---------------------------------------------------------------------
> Exception: javax.jms.JMSException
> Message: fullTextIndexer is already registered
> ---- stack trace
> ---------------------------------------------------------------
> javax.jms.JMSException: fullTextIndexer is already registered
> org.exolab.jms.messagemgr.ConsumerManager.createDurableConsumerEndpoint(Con
>s umerManager.java:404)
> org.exolab.jms.server.JmsServerSession.createSubscriber(JmsServerSession.ja
>v a:771)
> org.exolab.jms.server.mipc.IpcJmsSessionConnection.createSubscriber(IpcJmsS
>e ssionConnection.java:588)
> org.exolab.jms.server.mipc.IpcJmsSessionConnection.notify(IpcJmsSessionConn
>e ction.java:165)
> org.exolab.jms.server.mipc.IpcJmsReceiver.notify(IpcJmsReceiver.java:100)
> org.exolab.jms.server.mipc.IpcServerChannel.run(IpcServerChannel.java:161)
> ---------------------------------------------------------------------------
>- ----
>
> xargs: /usr/java/jdk1.5.0_06//bin/java: exited with status 255; aborting
>
Based on your stack trace I'm guessing that you are running a daisy-1.4 (or
older?) which still used openjms. The instructions you found in the
documentation were for daisy 2.0 and 1.5 (apparently I still have to create a
variant for the 1.5 documentation.)
If you want to run parallel instances of an older daisy then I think the only
way to do this is to make copies of the whole daisy directory. You might be
able to use the instructions for 1.5&2.0 to have an idea of what you might
have to change. Basically you have to change the database configuration, and
all ports daisy listens to. The biggest difference would probably be in the
jms configuration. The openjms configuration is found in
<daisy_home>/openjms/conf if I recall correctly but what exactly needs
changing I'd have to lookup and try for myself.
hth,
Paul
More information about the daisy
mailing list