> Yes you are right. I have not figured out what the cause is, > but I've also seen this happen a couple of times. I was not > able to reproduce it though.
But I think this results in problems. From the top of my head, you can only get a jms connection to the repository if and only if the repository is running. If you start the cms and then the repository, the jms reconnection won't work. If you start a repo, then the cms, stop the repo and start again, the jms connection will reconnect. So, unfortunately, at startup of the cms, a repository needs to be running. This, also gives me the idea that the problem you have is in the jms connection. So, in your cocoon.xconf, the problem might be in <parameter name="java.naming.provider.url" value="tcp://www.localhost.nl:3035/"/> where you either have some wrong host or a problem with some firewall and the port. Might that give you a hint to know where to look? AFAIK, first starting the cms and then the repository will result in having no jms connection Regards Ard > > Regards, > > Jeroen Reijn > > Andrew Savory wrote: > > Hi, > > > > On 11/14/07, Jeroen Reijn <[EMAIL PROTECTED]> wrote: > >> Try to start it the other way around and see what happens: > >> > >> First the CMS and then start up the repository. > > > > > > That seems to work fine. I automatically start the > repository first, > > so I never spotted it :-( > > > > Seems this is a problem though, since the CMS and repo are > supposed to > > be started and stopped independently... > > > > > > Andrew. > > -- > > Sourcesense: Making sense of Open Source > > Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 > > Web: http://www.sourcesense.com/ > > ******************************************** > > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
