[jboss-jira] [JBoss JIRA] (WFLY-1533) UT015005: Error invoking method requestDestroyed on listener class

Juergen Zimmermann (JIRA) jira-events at lists.jboss.org
Fri Sep 6 11:22:04 EDT 2013


     [ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Zimmermann updated WFLY-1533:
-------------------------------------

    Attachment: mojarra-2.1.zip
                testcase-WFLY-1533.zip


Instructions for the testcase:

1) Install WildFly from the latest master.

2) Add the modules for Mojarra 2.1.26 because even the latest release of RichFaces doesn't work with Mojarra 2.2.x, i.e. just unzip mojarra-2.1.zip in $JBOSS_HOME/modules.

3) In standalone/configuration/standalone.xml add the security domain "testcase" which is configured via users.properties and roles.properties in the testcase itself:
{code}
<security-domain name="testcase" cache-type="default">
   <authentication>
      <login-module code="UsersRoles" flag="required"/>
   </authentication>
</security-domain>

{code}

4) Start the WildFly server, i.e. $JBOSS_HOME/bin/standalone.bat

5) Prepare the testcase in a shell:
{code}
mvn package
cp target/testcase.war $JBOSS_HOME/standalone/deployments
{code}
Remark 1: During deployment on Windows you see a warning about package-info because of https://hibernate.atlassian.net/i#browse/HHH-8394
Remark 2: "mvn jboss-as:deploy" doesn't work because users.properties is searched in the CLASSPATH.

6) Now in a webbrowser submit http://localhost:8080/testcase, and then log in using ID 1 and password p in the right upper corner. Then just click the new logout link. After about 30 seconds the stacktrace appears in the WildFly console.
                
> UT015005: Error invoking method requestDestroyed on listener class 
> -------------------------------------------------------------------
>
>                 Key: WFLY-1533
>                 URL: https://issues.jboss.org/browse/WFLY-1533
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld
>    Affects Versions: 8.0.0.Alpha2, 8.0.0.Alpha4
>            Reporter: Juergen Zimmermann
>            Assignee: Jozef Hartinger
>         Attachments: mojarra-2.1.zip, testcase-WFLY-1533.zip
>
>
> I'm using a WildFly snapshot with Undertow 1.0.0.Alpha19 and Weld 2.0.1.Final. I'm getting the following stacktrace:
> 16:55:04,534 ERROR [io.undertow.servlet.request] UT015005: Error invoking method requestDestroyed on listener class org.jboss.weld.servlet.WeldListener: java.lang.IllegalStateException: UT000010: Session not found MDEkG_Aum5OlXUsjh11kGkh9
> 	at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:221) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:106) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:25) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:13) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at org.jboss.weld.context.AbstractConversationContext.dissociate(AbstractConversationContext.java:161) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at org.jboss.weld.servlet.ConversationContextActivator.disassociateConversationContext(ConversationContextActivator.java:162) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at org.jboss.weld.servlet.HttpContextLifecycle.requestDestroyed(HttpContextLifecycle.java:159) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:91) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29]
> 	at io.undertow.servlet.core.ApplicationListeners.requestDestroyed(ApplicationListeners.java:196) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:159) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:114) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:90) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:607) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> 	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list