AFAIK, that log message has always been there. If you are getting it
now, it is because either:
(1) previously it was not visible due to your log configuration
(2) it was not visible because jms was available
I assume it is because of (1).
However, it is not normal that you get this message on every request.
You should only create one instance of RemoteRepositoryManager to
handle all requests of all users. There are a few good reasons to do
so, such as there are some (small, essential) caches maintained which
are otherwise lost, and there is an http connection pool on this
level.
So I suggest you first fix that. If you want the JMS client (important
for cache invalidation), you not only need to the libraries on the
classpath, but you actually need to instantiate the JmsClient and pass
it to the RemoteRepositoryManager. There are some docs at the bottom
of
http://daisycms.org/daisydocs-2_3/373-cd/375-cd/28-cd.htmlbut they are very out of date.
On Thu, Aug 6, 2009 at 5:49 PM, John Stubing<
jstubing@...> wrote:
> Hello,
>
> I have been using Daisy for a web application that I have been working on
> and I recently updated to version 2.3. Since the update, I have been getting
> the following warning upon each request to the content repository:
>
> - RemoteRepositoryManager: JmsClient is not available, will do without.
>
> I have included all of the JMS jar files and this warning still persists.
> Prior to the 2.3 update, I had no problems.
>
> I would appreciate any guidance you can give me on getting rid of this
> warning.
>
> Thank you,
> John
--
Bruno Dumon
Outerthought ~
http://outerthought.org/Daisy ~
http://www.daisycms.org/Kauri ~
http://www.kauriproject.org/_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/en/services/daisy/support.htmlmail to:
daisy@...
list information:
http://lists.cocoondev.org/mailman/listinfo/daisy
