[JBoss JIRA] (WFLY-3529) UT000010: Session not found
by Shark Xu (JIRA)
[ https://issues.jboss.org/browse/WFLY-3529?page=com.atlassian.jira.plugin.... ]
Shark Xu commented on WFLY-3529:
--------------------------------
I met this issue yesterday also, below is my analysis after code check hope it can help:
This issue raise in concurrency.
In same session, when 2 threads come to server concurrently 2 HttpServletRequestImpl object & 2 HttpSessionImpl object(have same session data) created.
When HttpSessionImpl in one thread be invalidated, the state not sync to the HttpSessionImpl in the other thread, while the session data(instance of InMemorySessionManager.InMemorySession) be removed.
In this case when invoke HttpSessionImpl.getAttribut() in the other thread, it will throw IllegalStateException
> UT000010: Session not found
> ----------------------------
>
> Key: WFLY-3529
> URL: https://issues.jboss.org/browse/WFLY-3529
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Environment: Wildfly 8.1.0.Final ,
> Reporter: Youssef BIKHCHICHE
> Assignee: Stuart Douglas
> Attachments: WFLY-3529.tar.gz, WFLY-3529.war
>
>
> After migration our AS from Woldfly 8.0.0 to 8.1.0 we get this issue that we think has been fixed in the previous release of wildfly.
> ERREOR code :
> 2014-06-20 12:45:21,092 ERROR [io.undertow.request] (default task-11) Blocking request failed HttpServerExchange{ GET /xenturion/faces/public/500.xhtml}: java.lang.RuntimeException: java.lang.IllegalStateException: UT000010: Session not found cX6YRwOmoXcB8FFUdNY2r7Te
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:408)
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:311)
> at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:128)
> at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:142)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:273)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> Caused by: java.lang.IllegalStateException: UT000010: Session not found cX6YRwOmoXcB8FFUdNY2r7Te
> at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:319)
> at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:121)
> at org.springframework.security.web.context.HttpSessionSecurityContextRepository.readSecurityContextFromSession(HttpSessionSecurityContextRepository.java:144)
> at org.springframework.security.web.context.HttpSessionSecurityContextRepository.loadContext(HttpSessionSecurityContextRepository.java:86)
> at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:82)
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:343)
> at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:260)
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132)
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:229)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:172)
> at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:402)
> ======================================================
> this issue happens after a http session invalidate action and it' not a regular problems.
> Best regards,
> Youssef
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFLY-4409) java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4409?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reassigned WFLY-4409:
------------------------------------
Assignee: Stuart Douglas (was: Jason Greene)
> java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4409
> URL: https://issues.jboss.org/browse/WFLY-4409
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.2.0.Final
> Reporter: Alexandr Sokolov
> Assignee: Stuart Douglas
>
> In the log during the application server startup we see in the log file:
> {code}
> [0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
> at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
> at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
> at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> ... 5 more
> ...
> [0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
> "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
> "jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
> "jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
> "jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
> ...
> {code}
> From this output it's not clear what exactly is absent in the ear file.
> Could you refactor logging for this error. In order to display which exactly annotation was not found.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (DROOLS-729) Android Support
by Mark Kedzierski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-729?page=com.atlassian.jira.plugin... ]
Mark Kedzierski commented on DROOLS-729:
----------------------------------------
I've refactored and rebased this change on master. It is now an addon module called drools-android. The core code checks if it is running within Android by checking the classpath and if drools-android is present in the classpath to load the dex classloader implementations or to use regular ones.
I am working on adding KieContainer support but am still working through issues. There are a lot of complexities. I did manage to get a classpath container loaded from a kmodule.xml file. Issues:
-Dex 65K method limit. Adding all the drools-compiler dependencies and Jaxp implementation pushes this limit. I needed to use proguard but still right at the limit. Could explore multi-dex but that is generally annoying, and raises classloader issues.
-All jars are merged into a single apk file. Which means kmodule.xml files would overwrite each other if there are multiple kjar dependencies. Also currently the pom.properties file is found without using the releaseId as part of it. And the APK will include all the pom.properties files from all dependencies. I used the maven-android-plugin Meta-inf filter to only include the file from the main artifact. Again multiple kjars are a problem.
> Android Support
> ---------------
>
> Key: DROOLS-729
> URL: https://issues.jboss.org/browse/DROOLS-729
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.0.1.Final
> Environment: Android
> Reporter: Mark Kedzierski
> Assignee: Mario Fusco
> Priority: Optional
> Labels: Android
>
> I've done some work porting Drools 6.0.1.Final to work on Android. My current effort uses Dex classloaders for all generated classes. Precompiled rule packages execute on Android with either java or mvel dialect.
> code:
> http://www.github.com/kedzie/drools-android
> http://www.github.com/kedzie/drools-android-sample
> Features:
> -Dex classloaders for all generated classes
> -Roboguice integration for injecting knowledge bases from precompiled packages
> -Maven plugin which pre-compiles rule packages
> Issues:
> -Unit tests don't work because it always uses dex classloader, which doesn't work on a desktop system
> -Haven't tested drools-compiler on android platform
> I am wondering how to move forward and contribute this code. I think it would be ideal if the same codebase worked on both desktop and android platforms. Otherwise it would need to be a seperate fork. Also how to manage unit testing in the Android version. Any thoughts welcome.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-586) domain controller does not timeout on bad app deploy
by Ian Kent (JIRA)
[ https://issues.jboss.org/browse/WFCORE-586?page=com.atlassian.jira.plugin... ]
Ian Kent closed WFCORE-586.
---------------------------
Thanks for the quick response.
> domain controller does not timeout on bad app deploy
> ----------------------------------------------------
>
> Key: WFCORE-586
> URL: https://issues.jboss.org/browse/WFCORE-586
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Environment: WF 8.2.0-FINAL
> Reporter: Ian Kent
> Assignee: Brian Stansberry
>
> We have a WildFly domain setup with 5 server groups and at least one server in each group. We continuous deploy applications (wars) into the domain from out continuos integration/deployment tool (Bamboo) using the WildFly CLI.
> {noformat}
> jboss-cli --connect --controller=host:port --timeout=10000 --command="deploy x.war --name=x.war --runtime-name=x-version.war --server-groups=A"
> {noformat}
> If an app has trouble deploying due to looping on resource connection attempts it blocks the bamboo agent and domain controller for undetermined amount of time.
> I know there is a connection timeout, but what about a deployment timeout?
> If a deploy does not finish within timeout then it it cancelled.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-586) domain controller does not timeout on bad app deploy
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-586?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFCORE-586.
-------------------------------------
Resolution: Duplicate Issue
My assumption is this is a duplicate of https://issues.jboss.org/browse/WFLY-2741, which is fixed in WildFly Core master and in full WildFly 9.0.0.Alpha1. Please re-open if it still fails for you with that release and a build of the latest WildFly master.
See https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Contro...
> domain controller does not timeout on bad app deploy
> ----------------------------------------------------
>
> Key: WFCORE-586
> URL: https://issues.jboss.org/browse/WFCORE-586
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Environment: WF 8.2.0-FINAL
> Reporter: Ian Kent
> Assignee: Brian Stansberry
>
> We have a WildFly domain setup with 5 server groups and at least one server in each group. We continuous deploy applications (wars) into the domain from out continuos integration/deployment tool (Bamboo) using the WildFly CLI.
> {noformat}
> jboss-cli --connect --controller=host:port --timeout=10000 --command="deploy x.war --name=x.war --runtime-name=x-version.war --server-groups=A"
> {noformat}
> If an app has trouble deploying due to looping on resource connection attempts it blocks the bamboo agent and domain controller for undetermined amount of time.
> I know there is a connection timeout, but what about a deployment timeout?
> If a deploy does not finish within timeout then it it cancelled.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFLY-4410) LogContextTestCase should be removed
by James Perkins (JIRA)
James Perkins created WFLY-4410:
-----------------------------------
Summary: LogContextTestCase should be removed
Key: WFLY-4410
URL: https://issues.jboss.org/browse/WFLY-4410
Project: WildFly
Issue Type: Task
Components: Logging, Test Suite
Reporter: James Perkins
Assignee: James Perkins
The [{{LogContextTestCase}}|https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/logging/LogContextTestCase.java] should likely be removed. It uses an ugly hack that is very fragile especially since logging is in core. It's simply testing for a possible leak that shouldn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months