November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBREM-1325) Release 2.5.4.SP5

by Ron Sigal (JIRA)

Ron Sigal created JBREM-1325: -------------------------------- Summary: Release 2.5.4.SP5 Key: JBREM-1325 URL: https://issues.jboss.org/browse/JBREM-1325 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal -- 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

12 years, 8 months

1
0
0 / 0

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

by Leonardo Loch Zanivan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.... ] Leonardo Loch Zanivan commented on WFLY-1533: --------------------------------------------- [~mkouba] you're right. Thanks. > UT015005: Error invoking method requestDestroyed on listener class > ------------------------------------------------------------------- > > Key: WFLY-1533 > URL: https://issues.jboss.org/browse/WFLY-1533 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > 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, testcase-wildfly-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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2435) Upgrade Generic JMS RA to 1.0.1.CR1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2435?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2435: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1026397 > Upgrade Generic JMS RA to 1.0.1.CR1 > ----------------------------------- > > Key: WFLY-2435 > URL: https://issues.jboss.org/browse/WFLY-2435 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2435) Upgrade Generic JMS RA to 1.0.1.CR1

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-2435: --------------------------------- Summary: Upgrade Generic JMS RA to 1.0.1.CR1 Key: WFLY-2435 URL: https://issues.jboss.org/browse/WFLY-2435 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JCA Affects Versions: 8.0.0.Beta1 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 8.0.0.CR1 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2430) App with custom ContainerResponseFilter (JAX-RS) fails deploy

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2430?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-2430: -------------------------------------- Definitly works for me. Can you post your full stack trace here? > App with custom ContainerResponseFilter (JAX-RS) fails deploy > ------------------------------------------------------------- > > Key: WFLY-2430 > URL: https://issues.jboss.org/browse/WFLY-2430 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7 > Reporter: Rudy De Busscher > Assignee: Stuart Douglas > Attachments: exampleRest.zip > > > Created a simple rest application with a ContainerResponseFilter. The deploy fails with a ClassNotFoundException of javax.ws.rs.container.ContainerResponseFilter. > See also https://community.jboss.org/message/844105 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-317) Multiple issues with named consequences

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-317?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-317. -------------------------------- Fix Version/s: 6.0.0.Final Resolution: Done > Multiple issues with named consequences > --------------------------------------- > > Key: DROOLS-317 > URL: https://issues.jboss.org/browse/DROOLS-317 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.0.Final > > > Named consequences have the following issues: > - consequence name not set for MVEL (java ok) > - branch update using wrong leftTuple in phreak > - missing consequence names not detected at compile time > - LogicTransformer doesn't process branches with or correctly > - Conditional named consequence cannot be invoked after an eval > - Conditional named consequence doesn't work with inherited rules -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2433) please tag 7.3 in community repository

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2433?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-2433. ----------------------------- Resolution: Rejected EAP codebase is part of different repository that only gets some backported fixes from upstream (wildfly/as7). as such we cannot tag it in upstream repository as code is not there. All EAP sources can be found at ftp://ftp.redhat.com/redhat/jbeap/ > please tag 7.3 in community repository > -------------------------------------- > > Key: WFLY-2433 > URL: https://issues.jboss.org/browse/WFLY-2433 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Eicher > > According to JBoss dowload page, at EAP 6.2.0, there is a JBoss AS 7.3.0 release; however no such release can be found in as7 or wildfly repository. > Please tag the 7.3.0 in either repository, so as not to have the community completely out of the loop. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-317) Multiple issues with named consequences

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-317?page=com.atlassian.jira.plugin... ] Mario Fusco updated DROOLS-317: ------------------------------- Description: Named consequences have the following issues: - consequence name not set for MVEL (java ok) - branch update using wrong leftTuple in phreak - missing consequence names not detected at compile time - LogicTransformer doesn't process branches with or correctly - Conditional named consequence cannot be invoked after an eval - Conditional named consequence doesn't work with inherited rules was: Named consequences have the following issues: - consequence name not set for MVEL (java ok) - branch update using wrong leftTuple in phreak - missing consequence names not detected at compile time - LogicTransformer doesn't process branches with or correctly > Multiple issues with named consequences > --------------------------------------- > > Key: DROOLS-317 > URL: https://issues.jboss.org/browse/DROOLS-317 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > > Named consequences have the following issues: > - consequence name not set for MVEL (java ok) > - branch update using wrong leftTuple in phreak > - missing consequence names not detected at compile time > - LogicTransformer doesn't process branches with or correctly > - Conditional named consequence cannot be invoked after an eval > - Conditional named consequence doesn't work with inherited rules -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2430) App with custom ContainerResponseFilter (JAX-RS) fails deploy

by Rudy De Busscher (JIRA)

[ https://issues.jboss.org/browse/WFLY-2430?page=com.atlassian.jira.plugin.... ] Rudy De Busscher commented on WFLY-2430: ---------------------------------------- Retried with Beta2-snapshot (build 766 from CI) - Unzipped - Started standalone - mvn clean package on exampleRest app - through management console deploy - Call URL -> Exception So no idea what I'm doing wrong. > App with custom ContainerResponseFilter (JAX-RS) fails deploy > ------------------------------------------------------------- > > Key: WFLY-2430 > URL: https://issues.jboss.org/browse/WFLY-2430 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7 > Reporter: Rudy De Busscher > Assignee: Stuart Douglas > Attachments: exampleRest.zip > > > Created a simple rest application with a ContainerResponseFilter. The deploy fails with a ClassNotFoundException of javax.ws.rs.container.ContainerResponseFilter. > See also https://community.jboss.org/message/844105 -- 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

12 years, 8 months

1
0
0 / 0

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

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-1533: ------------------------------------ [~pangalz] your testcase covers a different issue, see also WELD-1542. > UT015005: Error invoking method requestDestroyed on listener class > ------------------------------------------------------------------- > > Key: WFLY-1533 > URL: https://issues.jboss.org/browse/WFLY-1533 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > 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, testcase-wildfly-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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013