You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Marco Huber <mh...@project-team.de> on 2009/11/04 13:52:12 UTC
Log message : No RenderingContext has been created.
Hi all,
in our application (Trinidad 1.2.12, Seam 2.2.0, RichFaces 3.3.1, Spring
2.5.6) the following message appear from time to time in the log file:
SEVERE [CoreRenderKit] No RenderingContext has been created.
After searching the internet, there are different postings about this
problem, mainly regarding to exceptions. We have configured our
application from an example. All works correctly so far.
So is this message really SEVERE? Or where can I configure my
application that a RendingContext is set?
And suggestings are welcome.
Marco
Re: Log message : No RenderingContext has been created.
Posted by Marco Huber <mh...@project-team.de>.
Okay, some further investigation.
The exception occured because of a missing jar file. The seam-debug.jar
hides a NoClassDefFoundException and run itself into an exception. After
adding the missing jar our application starts correctly.
The tomcat log shows now also the SEVERE message, without breaking the
application.
I found out that if I reload the page, diverse threads are acting on the
server which have not instance of the RenderingContext.
Regards
Marco
Marco Huber wrote:
> So I investigated this a little more.
> I found out that on JBoss 5.1.0 there is only the SEVERE message in the
> log file.
> If I deploy our application on Tomcat 6.0.20 I got an exception (see
> stack trace below).
>
> @Cagatay : The requested page doesn't contains any rich faces, a4j or
> seam components. So I think there is configuration problem.
>
> Maybe someone could see any problem in the stacktrace :-)
>
> Marco
>
>
> SCHWERWIEGEND: No RenderingContext has been created.
> 05.11.2009 09:33:45 com.sun.faces.lifecycle.Phase handleBeforePhase
> WARNUNG: JSF1053: (Listener:
> org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(), Phase ID:
> RENDER_RESPONSE 6, View ID: /debug.xhtml) Excep
> tion thrown during phase-listener execution:
> java.lang.IllegalStateException: Kein RenderingContext
> 05.11.2009 09:33:45 com.sun.faces.lifecycle.Phase handleBeforePhase
> WARNUNG:
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:305)
>
> org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
>
> javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:813)
> javax.faces.component.UIComponent.encodeAll(UIComponent.java:928)
> javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
> org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:56)
>
> com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214)
> com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96)
> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
>
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
>
> org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
>
> org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
>
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
>
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
> java.lang.Thread.run(Thread.java:619)
>
>
> Cagatay Civici wrote:
>> Does it happen when you make a request which RichFaces?
>>
>> On Wed, Nov 4, 2009 at 12:52 PM, Marco Huber <mh...@project-team.de>
>> wrote:
>>
>>> Hi all,
>>>
>>> in our application (Trinidad 1.2.12, Seam 2.2.0, RichFaces 3.3.1, Spring
>>> 2.5.6) the following message appear from time to time in the log file:
>>>
>>> SEVERE [CoreRenderKit] No RenderingContext has been created.
>>>
>>> After searching the internet, there are different postings about this
>>> problem, mainly regarding to exceptions. We have configured our
>>> application
>>> from an example. All works correctly so far.
>>>
>>> So is this message really SEVERE? Or where can I configure my
>>> application
>>> that a RendingContext is set?
>>>
>>> And suggestings are welcome.
>>>
>>> Marco
>>>
>>>
>>
>
>
Re: Log message : No RenderingContext has been created.
Posted by Marco Huber <mh...@project-team.de>.
So I investigated this a little more.
I found out that on JBoss 5.1.0 there is only the SEVERE message in the
log file.
If I deploy our application on Tomcat 6.0.20 I got an exception (see
stack trace below).
@Cagatay : The requested page doesn't contains any rich faces, a4j or
seam components. So I think there is configuration problem.
Maybe someone could see any problem in the stacktrace :-)
Marco
SCHWERWIEGEND: No RenderingContext has been created.
05.11.2009 09:33:45 com.sun.faces.lifecycle.Phase handleBeforePhase
WARNUNG: JSF1053: (Listener:
org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(), Phase ID:
RENDER_RESPONSE 6, View ID: /debug.xhtml) Excep
tion thrown during phase-listener execution:
java.lang.IllegalStateException: Kein RenderingContext
05.11.2009 09:33:45 com.sun.faces.lifecycle.Phase handleBeforePhase
WARNUNG:
org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer.java:305)
org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin(HtmlFormRenderer.java:56)
javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:813)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:928)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:56)
com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
java.lang.Thread.run(Thread.java:619)
Cagatay Civici wrote:
> Does it happen when you make a request which RichFaces?
>
> On Wed, Nov 4, 2009 at 12:52 PM, Marco Huber <mh...@project-team.de> wrote:
>
>> Hi all,
>>
>> in our application (Trinidad 1.2.12, Seam 2.2.0, RichFaces 3.3.1, Spring
>> 2.5.6) the following message appear from time to time in the log file:
>>
>> SEVERE [CoreRenderKit] No RenderingContext has been created.
>>
>> After searching the internet, there are different postings about this
>> problem, mainly regarding to exceptions. We have configured our application
>> from an example. All works correctly so far.
>>
>> So is this message really SEVERE? Or where can I configure my application
>> that a RendingContext is set?
>>
>> And suggestings are welcome.
>>
>> Marco
>>
>>
>
Re: Log message : No RenderingContext has been created.
Posted by Cagatay Civici <ca...@gmail.com>.
Does it happen when you make a request which RichFaces?
On Wed, Nov 4, 2009 at 12:52 PM, Marco Huber <mh...@project-team.de> wrote:
> Hi all,
>
> in our application (Trinidad 1.2.12, Seam 2.2.0, RichFaces 3.3.1, Spring
> 2.5.6) the following message appear from time to time in the log file:
>
> SEVERE [CoreRenderKit] No RenderingContext has been created.
>
> After searching the internet, there are different postings about this
> problem, mainly regarding to exceptions. We have configured our application
> from an example. All works correctly so far.
>
> So is this message really SEVERE? Or where can I configure my application
> that a RendingContext is set?
>
> And suggestings are welcome.
>
> Marco
>
>