[
https://issues.jboss.org/browse/RF-11409?page=com.atlassian.jira.plugin.s...
]
Juraj Huska commented on RF-11409:
----------------------------------
I have tried to reproduce this error with 4.1.0.20111011-M3 showcase, and I found that
this error is logged to the console only when I am starting Tomcat *not with startup
scripts*, which should set all variables but via calling specific jar files with specific
flags, which is also done in Arquillian, to start Tomcat(I have written the plugin for
Arquillian).
*In documentation for Tomcat is written:*
When running Tomcat on unixes, the console output is usually redirected to the file named
catalina.out.
Whatever is written to System.err/out will be caught into that file. That may include:
Uncaught exceptions printed by java.lang.ThreadGroup.uncaughtException(..)
Thread dumps, if you requested them via a system signal
So in case that there are logged all exceptions in catalina.out when starting Tomcat via
startup scripts from CATALINA_HOME/bin, *then issue is not related to RichFaces* but it is
problem of improper starting of Tomcat. Another clue for this is that in stacktrace
exception there are only Tomcat relative classes.
showcase - aj4:push - all samples - when push is done then
NullPointerException is thrown but the expected result of push is there
----------------------------------------------------------------------------------------------------------------------------------
Key: RF-11409
URL:
https://issues.jboss.org/browse/RF-11409
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll, showcase
Affects Versions: 4.1.0.Milestone2
Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
container - Tomcat 7.0.20
browser - Chrome 13, IE 9, FF 3.6
Reporter: Juraj Huska
Assignee: Lukáš Fryč
When push is done on all samples for aj4:push in showcase, then NullPointerException is
thrown but the expected result of push is there. So the functionality is correct, only on
the server console exception is thrown, with this stacktrace:
{code}
SEVERE: Exception sending request initialized lifecycle event to listener instance of
class org.jboss.weld.environment.servlet.Listener
java.lang.NullPointerException
at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:81)
at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:115)
at
org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestDestroyed(ForwardingServletListener.java:42)
at
org.apache.catalina.core.StandardContext.fireRequestDestroyEvent(StandardContext.java:6008)
at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:281)
at
org.apache.coyote.http11.AbstractHttp11Processor.asyncDispatch(AbstractHttp11Processor.java:1220)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:511)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
This exception is thrown after each push execution, and it is not broken after first
trowing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira