[JBoss JIRA] (SECURITY-750) Database*LoginModules should use the transactionManagerJndiName module option
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-750?page=com.atlassian.jira.plug... ]
Stefan Guilhen updated SECURITY-750:
------------------------------------
Description:
The DatabaseCertLoginModule and DatabaseServerLoginModule use for role search a routine from a class org.jboss.security.auth.spi.DbUtil. But there is a hardcoded reference to JNDI name for Transaction Manager lookup "java:/TransactionManager" - which is not valid in the EAP 6. The JNDI name should be provided as a parameter.
The login module option "transactionManagerJndiName" is already implemented in the DatabaseServerLoginModule, but it should be also added to the DatabaseCertLoginModule.
> Database*LoginModules should use the transactionManagerJndiName module option
> -----------------------------------------------------------------------------
>
> Key: SECURITY-750
> URL: https://issues.jboss.org/browse/SECURITY-750
> Project: PicketBox
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: PicketBox
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Fix For: PIcketBox_4_0_19.Final
>
>
> The DatabaseCertLoginModule and DatabaseServerLoginModule use for role search a routine from a class org.jboss.security.auth.spi.DbUtil. But there is a hardcoded reference to JNDI name for Transaction Manager lookup "java:/TransactionManager" - which is not valid in the EAP 6. The JNDI name should be provided as a parameter.
> The login module option "transactionManagerJndiName" is already implemented in the DatabaseServerLoginModule, but it should be also added to the DatabaseCertLoginModule.
--
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
11 years, 4 months
[JBoss JIRA] (WFLY-1899) Conversation timeout is broken
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1899?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann commented on WFLY-1899:
------------------------------------------
I upgraded to the latest WIldFly master (Undertow 1.0.0.Beta11). Now I get the following stacktrace:
{code}
15:57:13,938 ERROR [io.undertow.request] Exception while generating error page /error/conversationTimeout.xhtml?nocid=true: java.lang.RuntimeException: java.lang.RuntimeException: javax.servlet.ServletException: /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}" /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}": org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:394) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:315) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:222) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: java.lang.RuntimeException: javax.servlet.ServletException: /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}" /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}": org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:139) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at javax.servlet.http.HttpServlet.doPost(HttpServlet.java:357) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at io.undertow.servlet.handlers.DefaultServlet.doPost(DefaultServlet.java:123) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:82) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:57) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:139) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:388) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
... 10 more
Caused by: javax.servlet.ServletException: /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}" /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}": org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) [jsf-api-2.1.25.jar:2.1]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:82) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:57) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:139) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:388) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:307) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:137) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
... 24 more
Caused by: javax.faces.view.facelets.TagAttributeException: /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}" /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}": org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at com.sun.faces.facelets.tag.TagAttributeImpl.getObject(TagAttributeImpl.java:331) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.TagAttributeImpl.getBoolean(TagAttributeImpl.java:136) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:91) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:166) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:120) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:116) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jsf-api-2.1.25.jar:2.1]
at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jsf-api-2.1.25.jar:2.1]
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jsf-api-2.1.25.jar:2.1]
at com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jsf-api-2.1.25.jar:2.1]
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:164) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:914) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.25.jar:2.1.25]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jsf-api-2.1.25.jar:2.1]
... 36 more
Caused by: javax.el.ELException: /WEB-INF/templates/desktop/nav.xml @20,74 test="#{not empty javax.enterprise.context.conversation.id}": org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.facelets.tag.TagAttributeImpl.getObject(TagAttributeImpl.java:329) [jsf-impl-2.1.25.jar:2.1.25]
... 92 more
Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:74) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
at org.jboss.weld.proxies.Conversation$335089890$Proxy$_$$_WeldClientProxy.getId(Unknown Source) [weld-core-impl-2.0.3.Final.jar:]
at sun.reflect.GeneratedMethodAccessor968.invoke(Unknown Source) [:1.7.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
at javax.el.BeanELResolver.getValue(BeanELResolver.java:363) [javax.el-3.0-b07.jar:3.0-b07]
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.25.jar:2.1.25]
at com.sun.el.parser.AstValue.getValue(AstValue.java:140) [javax.el-3.0-b07.jar:3.0-b07]
at com.sun.el.parser.AstValue.getValue(AstValue.java:204) [javax.el-3.0-b07.jar:3.0-b07]
at com.sun.el.parser.AstEmpty.getValue(AstEmpty.java:66) [javax.el-3.0-b07.jar:3.0-b07]
at com.sun.el.parser.AstNot.getValue(AstNot.java:63) [javax.el-3.0-b07.jar:3.0-b07]
at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) [javax.el-3.0-b07.jar:3.0-b07]
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.25.jar:2.1.25]
... 93 more
{code}
> Conversation timeout is broken
> ------------------------------
>
> Key: WFLY-1899
> URL: https://issues.jboss.org/browse/WFLY-1899
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha4
> Reporter: Juergen Zimmermann
> Assignee: Stuart Douglas
>
> When I'm already logged in in a JSF web app and get a CDI/Weld conversation timeout, then an error page should be shown.
> However, I'm getting the stacktrace below, and a blank page instead of the error page is shown.
> The error page is configured in web.xml:
> {code}
> <error-page>
> <exception-type>org.jboss.weld.context.NonexistentConversationException</exception-type>
> <location>/error/conversationTimeout.xhtml?nocid=true</location>
> </error-page>
> {code}
> Stacktrace with the current snapshot of WildFly using Undertow 1.0.0.Beta8 in the WildFly console:
> 16:20:12,466 ERROR [io.undertow.request] Exception while generating error page /error/conversationTimeout.xhtml?nocid=true: java.lang.RuntimeException: java.lang.IllegalStateException: JBAS017329: No security context found
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:394) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:315) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:222) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:623) [undertow-core-1.0.0.Beta8.jar:1.0.0.Beta8]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> Caused by: java.lang.IllegalStateException: JBAS017329: No security context found
> at org.wildfly.extension.undertow.security.SecurityActions$5.run(SecurityActions.java:119)
> at org.wildfly.extension.undertow.security.SecurityActions$5.run(SecurityActions.java:114)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
> at org.wildfly.extension.undertow.security.SecurityActions.pushRunAsIdentity(SecurityActions.java:114)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:88)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:139) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:388) [undertow-servlet-1.0.0.Beta8.jar:1.0.0.Beta8]
> ... 10 more
--
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
11 years, 4 months
[JBoss JIRA] (DROOLS-244) Sliding windows working incorrectly
by Vytautas Gimbutas (JIRA)
[ https://issues.jboss.org/browse/DROOLS-244?page=com.atlassian.jira.plugin... ]
Vytautas Gimbutas commented on DROOLS-244:
------------------------------------------
I think @timestamp attribute isn't working as expected (or i'm misunderstanding the whole concept).
It seems when timestamp attribute is set in the past then it will be in range of any time of window.
> Sliding windows working incorrectly
> -----------------------------------
>
> Key: DROOLS-244
> URL: https://issues.jboss.org/browse/DROOLS-244
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Vytautas Gimbutas
> Assignee: Mark Proctor
> Attachments: Event.java, file.drl, Transaction.java, TransactionCompletedEvent.java, TransactionCreatedEvent.java, TransactionEvent.java
>
>
> I'm having an issue with sliding windows. For some reason even though event is in the past it still gets into the window.
> I'm attaching drl file, the event/fact classes.
> I expect it to print 1 0, but instead it prints: 1 1
> The code that reproduces the issue:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newClassPathResource("file.drl") , ResourceType.DRL);
> if (kbuilder.hasErrors() ) {
> System.out.println( kbuilder.getErrors() );
> }
> KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
> kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
> StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
> Transaction transaction = new Transaction();
> TransactionCompletedEvent event = new TransactionCompletedEvent();
> event.setTransaction(transaction);
> ksession.insert(transaction);
> Date today = new Date();
> Calendar cal = new GregorianCalendar();
> cal.setTime(today);
> cal.add(Calendar.DAY_OF_MONTH, -30);
> event.setCreated(cal.getTime());
> WorkingMemoryEntryPoint wmep = ksession.getWorkingMemoryEntryPoint("TransactionCompletedEventStream");
> wmep.insert(event);
> ksession.fireAllRules();
> TransactionCreatedEvent event2 = new TransactionCreatedEvent();
> event2.setTransaction(transaction);
> ksession.insert(transaction);
> ksession.getWorkingMemoryEntryPoint("TransactionCreatedEventStream").insert(event2);
> ksession.fireAllRules();
--
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
11 years, 4 months
[JBoss JIRA] (WFLY-1533) UT015005: Error invoking method requestDestroyed on listener class
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann commented on WFLY-1533:
------------------------------------------
The issue still exists with Undertow 1.0.0.Beta11.
> 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
>
> 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
11 years, 4 months
[JBoss JIRA] (DROOLS-204) No poms such use <version> except for the droolsjbpm-parent pom
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-204?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer edited comment on DROOLS-204 at 8/30/13 9:28 AM:
------------------------------------------------------------------------
I have reviewed all projects and found some "problems" that I put in the problem list (attached)
The <version< tag was only controlle for all poms and dependencies, not for plugins.
was (Author: mbiarnes):
I have reviewed all projects and found some "problems" that I put in the problem list (attached)
> No poms such use <version> except for the droolsjbpm-parent pom
> ---------------------------------------------------------------
>
> Key: DROOLS-204
> URL: https://issues.jboss.org/browse/DROOLS-204
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
> Fix For: 6.0.0.CR2
>
> Attachments: problem_list.txt
>
>
> Open all projects (from the repository-list.txt) in IntelliJ (or Eclipse). Do a find in path (ctrl-shift-r) for "<version>" in all directories in files named "pom.xml".
> Export that result to txt (intellij has a button on the left for that) and paste that result as a comment on this issue.
> Only the droolsjbpm-parent pom file should show up in that result (in theory).
> For <version> each of those in that list:
> 1) If the droolsjbpm-parent already declares the same dependency (=> exact same groupId, artifactId (and optionally type, classifier)) with the same version, just remove the <version> line.
> If all cases of 1) are fixed and committed:
> 2) If the droolsjbpm-parent already declares the same dependency with a lower verion, remove the <version> line and notify the pom owner.
> 3) If the droolsjbpm-parent already declares the same dependency with a higher verion, add it to a the "problem list".
> 4) If the droolsjbpm-parent doesn't declare the dependency yet and EAP doesn't have it either (or it's the same version), add it in the droolsjbpm-parent pom and remove <version> line from the original pom.
> 5) If the droolsjbpm-parent doesn't declare the dependency yet and EAP has it in another version, add it to the "problem list".
> Copy the "problem list" as a comment to this issue too.
> Reqs: need to be done on master and 6.0.x (=> use git cherry-pick -x ...)
> Special cases that warrant exceptions:
> - The <scope>system</scope> artifact "downloaded-jdbc-driver-jar", which is a special hack of mriet. Leave it alone
--
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
11 years, 4 months
[JBoss JIRA] (DROOLS-204) No poms such use <version> except for the droolsjbpm-parent pom
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-204?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer edited comment on DROOLS-204 at 8/30/13 9:28 AM:
------------------------------------------------------------------------
I have reviewed all projects and found some "problems" that I put in the problem list (attached)
The <version< tag was only controlled for all poms and dependencies, not for plugins.
was (Author: mbiarnes):
I have reviewed all projects and found some "problems" that I put in the problem list (attached)
The <version< tag was only controlle for all poms and dependencies, not for plugins.
> No poms such use <version> except for the droolsjbpm-parent pom
> ---------------------------------------------------------------
>
> Key: DROOLS-204
> URL: https://issues.jboss.org/browse/DROOLS-204
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
> Fix For: 6.0.0.CR2
>
> Attachments: problem_list.txt
>
>
> Open all projects (from the repository-list.txt) in IntelliJ (or Eclipse). Do a find in path (ctrl-shift-r) for "<version>" in all directories in files named "pom.xml".
> Export that result to txt (intellij has a button on the left for that) and paste that result as a comment on this issue.
> Only the droolsjbpm-parent pom file should show up in that result (in theory).
> For <version> each of those in that list:
> 1) If the droolsjbpm-parent already declares the same dependency (=> exact same groupId, artifactId (and optionally type, classifier)) with the same version, just remove the <version> line.
> If all cases of 1) are fixed and committed:
> 2) If the droolsjbpm-parent already declares the same dependency with a lower verion, remove the <version> line and notify the pom owner.
> 3) If the droolsjbpm-parent already declares the same dependency with a higher verion, add it to a the "problem list".
> 4) If the droolsjbpm-parent doesn't declare the dependency yet and EAP doesn't have it either (or it's the same version), add it in the droolsjbpm-parent pom and remove <version> line from the original pom.
> 5) If the droolsjbpm-parent doesn't declare the dependency yet and EAP has it in another version, add it to the "problem list".
> Copy the "problem list" as a comment to this issue too.
> Reqs: need to be done on master and 6.0.x (=> use git cherry-pick -x ...)
> Special cases that warrant exceptions:
> - The <scope>system</scope> artifact "downloaded-jdbc-driver-jar", which is a special hack of mriet. Leave it alone
--
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
11 years, 4 months
[JBoss JIRA] (DROOLS-204) No poms such use <version> except for the droolsjbpm-parent pom
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-204?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-204:
------------------------------------------
Attachment: problem_list.txt
list with poms using still <version>
> No poms such use <version> except for the droolsjbpm-parent pom
> ---------------------------------------------------------------
>
> Key: DROOLS-204
> URL: https://issues.jboss.org/browse/DROOLS-204
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
> Fix For: 6.0.0.CR2
>
> Attachments: problem_list.txt
>
>
> Open all projects (from the repository-list.txt) in IntelliJ (or Eclipse). Do a find in path (ctrl-shift-r) for "<version>" in all directories in files named "pom.xml".
> Export that result to txt (intellij has a button on the left for that) and paste that result as a comment on this issue.
> Only the droolsjbpm-parent pom file should show up in that result (in theory).
> For <version> each of those in that list:
> 1) If the droolsjbpm-parent already declares the same dependency (=> exact same groupId, artifactId (and optionally type, classifier)) with the same version, just remove the <version> line.
> If all cases of 1) are fixed and committed:
> 2) If the droolsjbpm-parent already declares the same dependency with a lower verion, remove the <version> line and notify the pom owner.
> 3) If the droolsjbpm-parent already declares the same dependency with a higher verion, add it to a the "problem list".
> 4) If the droolsjbpm-parent doesn't declare the dependency yet and EAP doesn't have it either (or it's the same version), add it in the droolsjbpm-parent pom and remove <version> line from the original pom.
> 5) If the droolsjbpm-parent doesn't declare the dependency yet and EAP has it in another version, add it to the "problem list".
> Copy the "problem list" as a comment to this issue too.
> Reqs: need to be done on master and 6.0.x (=> use git cherry-pick -x ...)
> Special cases that warrant exceptions:
> - The <scope>system</scope> artifact "downloaded-jdbc-driver-jar", which is a special hack of mriet. Leave it alone
--
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
11 years, 4 months
[JBoss JIRA] (DROOLS-204) No poms such use <version> except for the droolsjbpm-parent pom
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-204?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer commented on DROOLS-204:
-----------------------------------------------
I have reviewed all projects and found some "problems" that I put in the problem list (attached)
> No poms such use <version> except for the droolsjbpm-parent pom
> ---------------------------------------------------------------
>
> Key: DROOLS-204
> URL: https://issues.jboss.org/browse/DROOLS-204
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
> Fix For: 6.0.0.CR2
>
>
> Open all projects (from the repository-list.txt) in IntelliJ (or Eclipse). Do a find in path (ctrl-shift-r) for "<version>" in all directories in files named "pom.xml".
> Export that result to txt (intellij has a button on the left for that) and paste that result as a comment on this issue.
> Only the droolsjbpm-parent pom file should show up in that result (in theory).
> For <version> each of those in that list:
> 1) If the droolsjbpm-parent already declares the same dependency (=> exact same groupId, artifactId (and optionally type, classifier)) with the same version, just remove the <version> line.
> If all cases of 1) are fixed and committed:
> 2) If the droolsjbpm-parent already declares the same dependency with a lower verion, remove the <version> line and notify the pom owner.
> 3) If the droolsjbpm-parent already declares the same dependency with a higher verion, add it to a the "problem list".
> 4) If the droolsjbpm-parent doesn't declare the dependency yet and EAP doesn't have it either (or it's the same version), add it in the droolsjbpm-parent pom and remove <version> line from the original pom.
> 5) If the droolsjbpm-parent doesn't declare the dependency yet and EAP has it in another version, add it to the "problem list".
> Copy the "problem list" as a comment to this issue too.
> Reqs: need to be done on master and 6.0.x (=> use git cherry-pick -x ...)
> Special cases that warrant exceptions:
> - The <scope>system</scope> artifact "downloaded-jdbc-driver-jar", which is a special hack of mriet. Leave it alone
--
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
11 years, 4 months