Thanks Chrisopher, apprecaite the reply.
The only puzzle is that I haven't changed the cocoon.xconf--it has been
the same for the last four years. (I am trying to upgrade from 2.1.7 to
2.1.11)
It gives me a clue though.
rgds
Paul
Christofer Dutz wrote:
Hi Paul,
I guess one or more components in your cocoon.xconf are failing during
cocoon startup. I ran into this problem quite some times. As soon as a
component fails, Cocoon does a second initialization of all components. It
seems the scheduler isn't correctly shut down prior to reinitializing.
Hope this helps,
Chris
-----Ursprüngliche Nachricht-----
Von: Paul Joseph [mailto:[email protected]]
Gesendet: Sonntag, 22. Februar 2009 04:31
An: [email protected]
Betreff: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Hi There,
Any idea why I get this error when I try to access my Cocoon App?
Thx.
Paul
----------------
Initialization Problem
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
cause
Scheduler with name 'Cocoon' already exists.
request-uri
/array/webtask/login/
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
