You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Paul Joseph <pj...@gmail.com> on 2009/02/22 04:30:34 UTC
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: AW: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Posted by Paul Joseph <pj...@gmail.com>.
Hi Chris,
I changed to the 2.1.11 cocoon.xconf and the problem went away...
Thanks again.
Paul
Christofer Dutz wrote:
> Hi Paul,
>
> make sure the logging is configured and active. I would also try increasing
> the log-level until you find any messages.
>
> Did I understand you correctly? You have upgraded Cocoon from 2.1.7 to
> 2.1.11 and have reused the old cocoon.xconf?
> If this is the case, there will certainly be the one or the other
> configuration problem. I would suggest using the original 2.1.11 xconf and
> adjusting it to match the needed settings of your application.
>
> Chris
>
>
> -----Ursprüngliche Nachricht-----
> Von: Paul Joseph [mailto:pjoseph@gmail.com]
> Gesendet: Montag, 23. Februar 2009 12:24
> An: users@cocoon.apache.org
> Betreff: Re: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
>
> 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:pjoseph@gmail.com]
>> Gesendet: Sonntag, 22. Februar 2009 04:31
>> An: users@cocoon.apache.org
>> 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: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: AW: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Posted by Paul Joseph <pj...@gmail.com>.
Chris,
Good idea--and yes, I was using the 2.1.7 xconf!!! Will change to the
new xconf!.
Paul
Christofer Dutz wrote:
> Hi Paul,
>
> make sure the logging is configured and active. I would also try increasing
> the log-level until you find any messages.
>
> Did I understand you correctly? You have upgraded Cocoon from 2.1.7 to
> 2.1.11 and have reused the old cocoon.xconf?
> If this is the case, there will certainly be the one or the other
> configuration problem. I would suggest using the original 2.1.11 xconf and
> adjusting it to match the needed settings of your application.
>
> Chris
>
>
> -----Ursprüngliche Nachricht-----
> Von: Paul Joseph [mailto:pjoseph@gmail.com]
> Gesendet: Montag, 23. Februar 2009 12:24
> An: users@cocoon.apache.org
> Betreff: Re: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
>
> 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:pjoseph@gmail.com]
>> Gesendet: Sonntag, 22. Februar 2009 04:31
>> An: users@cocoon.apache.org
>> 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: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
AW: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Posted by Christofer Dutz <ma...@c-ware.de>.
Hi Paul,
make sure the logging is configured and active. I would also try increasing
the log-level until you find any messages.
Did I understand you correctly? You have upgraded Cocoon from 2.1.7 to
2.1.11 and have reused the old cocoon.xconf?
If this is the case, there will certainly be the one or the other
configuration problem. I would suggest using the original 2.1.11 xconf and
adjusting it to match the needed settings of your application.
Chris
-----Ursprüngliche Nachricht-----
Von: Paul Joseph [mailto:pjoseph@gmail.com]
Gesendet: Montag, 23. Februar 2009 12:24
An: users@cocoon.apache.org
Betreff: Re: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
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:pjoseph@gmail.com]
> Gesendet: Sonntag, 22. Februar 2009 04:31
> An: users@cocoon.apache.org
> 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: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Posted by Paul Joseph <pj...@gmail.com>.
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:pjoseph@gmail.com]
> Gesendet: Sonntag, 22. Februar 2009 04:31
> An: users@cocoon.apache.org
> 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: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
AW: Cocoon 2.1.11--Scheduler with name "Cocoon" already exists.
Posted by Christofer Dutz <ma...@c-ware.de>.
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:pjoseph@gmail.com]
Gesendet: Sonntag, 22. Februar 2009 04:31
An: users@cocoon.apache.org
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org