[daisy] Multiple remote wiki's one repository

[Bruno Dumon]

Is this with Daisy 1.5 or 2.0?

Could you check that in

<wiki data dir>/daisy.xconf

the first listed component is the JMS component

<component class="org.outerj.daisy.jms.impl.JmsClientImpl"
logger="daisy.jmsclient" role="org.outerj.daisy.jms.JmsClient">


On Wed, 2007-05-09 at 13:47 -0700, Chris wrote:
> Thanks for your help.  I can get two wiki's talking to the same
> repository but I'm not sure about the clientId for the jms connection:
> 
> Errors in cocoon.log with existing client name in wiki daisy.xconf
> <jmsConnection><clientId>daisy-wiki</clientId>...
> 
> javax.jms.InvalidClientIDException: Broker: DaisyJMS - Client: daisy-wiki already
> connected
> 
> So, if I change the clientId on the second wiki to something 
> like <clientId>daisy-wiki2</clientId> I get these errors in cocool.log:
> 
> RemoteRepositoryManager: failed to lookup jms client component, will do without.
> ERROR (2007-05-09) 12:32.28:375 [access] (Unknown-URI)
> Unknown-Thread/RemoteRepositoryManager: RemoteRepositoryManager: JmsClient is not
> available, will do without.
> 
> But at least the wiki works!  It's just that the cache invalidation may
> not be working.  This is ok for my development environment.
> 
> So, is the activeMQ broker set up for multiple client(wiki's) to talk
> to it?
> 
> thanks,
> 
> -chris
> 

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno at outerthought.org                          bruno at apache.org