August 2013 - jboss-jira - Jboss List Archives

[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

12 years, 8 months

1
0
0 / 0

[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

12 years, 8 months

1
0
0 / 0

[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

12 years, 8 months

1
0
0 / 0

[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

12 years, 8 months

1
0
0 / 0

[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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1958) Provide machine readable referential document with information of default security constrains

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1958?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1958: ----------------------------------- Assignee: (was: Brian Stansberry) > Provide machine readable referential document with information of default security constrains > --------------------------------------------------------------------------------------------- > > Key: WFLY-1958 > URL: https://issues.jboss.org/browse/WFLY-1958 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Jakub Cechacek > Fix For: 8.0.0.CR1 > > > This is more of a future task, but at some point we should make sure that all security constraints are configured properly (right now we have no way of telling which resources should be, for example, sensitive). Thus QE will need something to check against. As a good example of what I mean have a look at referential document for module classification [1] - although for RBAC we would like to see something more "machine-friendly" > This should be something like listing of resources classified by default as sensitive/application/... > [1] https://docspace.corp.redhat.com/docs/DOC-105009 -- 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-1865) NPE might occur when a null object is returned from the aesh Console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1865?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1865: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=996164 > NPE might occur when a null object is returned from the aesh Console > -------------------------------------------------------------------- > > Key: WFLY-1865 > URL: https://issues.jboss.org/browse/WFLY-1865 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha3 > Reporter: Ståle Pedersen > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Beta1 > > > In cli/src/main/java/org/jboss/as/cli/impl/Console.java > 177 - return console.read(prompt).getBuffer(); > 178 + ConsoleOutput output = console.read(prompt); > 179 + return output != null ? output.getBuffer() : null; -- 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-1865) NPE might occur when a null object is returned from the aesh Console

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-1865?page=com.atlassian.jira.plugin.... ] Ivo Studensky resolved WFLY-1865. --------------------------------- Resolution: Done The related PR has been merged. > NPE might occur when a null object is returned from the aesh Console > -------------------------------------------------------------------- > > Key: WFLY-1865 > URL: https://issues.jboss.org/browse/WFLY-1865 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha3 > Reporter: Ståle Pedersen > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Beta1 > > > In cli/src/main/java/org/jboss/as/cli/impl/Console.java > 177 - return console.read(prompt).getBuffer(); > 178 + ConsoleOutput output = console.read(prompt); > 179 + return output != null ? output.getBuffer() : null; -- 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-1865) NPE might occur when a null object is returned from the aesh Console

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-1865?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-1865: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/4909 > NPE might occur when a null object is returned from the aesh Console > -------------------------------------------------------------------- > > Key: WFLY-1865 > URL: https://issues.jboss.org/browse/WFLY-1865 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha3 > Reporter: Ståle Pedersen > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Beta1 > > > In cli/src/main/java/org/jboss/as/cli/impl/Console.java > 177 - return console.read(prompt).getBuffer(); > 178 + ConsoleOutput output = console.read(prompt); > 179 + return output != null ? output.getBuffer() : null; -- 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-1560) PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1560?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1560: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 985003|https://bugzilla.redhat.com/show_bug.cgi?id=985003] > PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1560 > URL: https://issues.jboss.org/browse/WFLY-1560 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Attachments: server_log_snippet.txt > > > PartialObjectActivationJarTestCase fails if it runs after InflowFlatTestCase. It seems that the {{inflow2}} resource adapter is not fully unregistered by InflowFlatTestCase before PartialObjectActivationJarTestCase begins to start its own RA. > Here is the server log snippet (DEBUG level): > http://pastebin.test.redhat.com/147968 > Line 10 of this snippet corresponds to the invocation of {{setConfiguration("basic.xml");}} in PartialObjectActivationJarTestCase. Then, the server is apparently trying to activate {{MultipleConnectionFactory2Impl}} and {{MultipleAdminObject2Impl}} even though these are not involved in {{basic.xml}} of PartialObjectActivationJarTestCase at all. A suspicious exception is on line 19 there. > I tried to put some delay between {{remove(address);}} and {{removeModule(defaultPath);}} in {{AbstractModuleDeploymentTestCaseSetup#tearDown()}} but it did not help. I also tried to put {{@Ignore}} to both test methods in the InflowFlatTestCase which also did not help, so it is evidently related only to the RA deployment/undeployment. -- 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 August 2013