September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7101) Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct

by Dietrich Schmidt (JIRA)

[ https://issues.jboss.org/browse/WFLY-7101?page=com.atlassian.jira.plugin.... ] Dietrich Schmidt commented on WFLY-7101: ---------------------------------------- EJB spec 4.8.1 does not apply to this bug, please re-investigate. Singleton bean A (=ServerImpl) with @startup calls in its @Postconstruct method a method in singleton bean B (=TestReaderImpl) - this works fine. Now in this @PostConstruct several Threads are created with a ManagedExcecutorService - these threads start normally, but if the call a method iin singleton bean B, they are blocked. This must not happen and is a bug. > Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct > -------------------------------------------------------------- > > Key: WFLY-7101 > URL: https://issues.jboss.org/browse/WFLY-7101 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final > Environment: Wildfly 10.1.0 running under Windows 10 with Java 1.8.0_91 > Reporter: Dietrich Schmidt > Assignee: Jason Greene > Attachments: Verklemmung.zip > > > Wildfly 8.2.0 and 10.0.0 work fine with a Singleton Bean, which has a @Postconstruct method and in this method several threads are created with the ManagedExecutorService. These threads call a method in another Singleton EJB, which has been injected. > This call is blocked in Wildfly 10.1.0 until the Prostconstruct thread has ended. > I assume that the behaviour of Wildfly 8.2.0 + 10.0.0 is correct and the behaviour of Wildfly 10.1.0 is a bug. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1310) Expired fact with activationCount > 0 are not evicted from objectstore

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1310: -------------------------------------- Summary: Expired fact with activationCount > 0 are not evicted from objectstore Key: DROOLS-1310 URL: https://issues.jboss.org/browse/DROOLS-1310 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.CR2 Reporter: Matteo Mortari Assignee: Mario Fusco Priority: Minor Expired fact with activationCount > 0 are not evicted from objectstore: intended behavior for serialization purposes, but for instance side-effects when used in an activation-group scenario where the rules are not 100% dual. Sized-down reproducer will be submitted at a later time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1309) Rules compilation failure depending on condition ordering

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1309: ------------------------------------- Summary: Rules compilation failure depending on condition ordering Key: DROOLS-1309 URL: https://issues.jboss.org/browse/DROOLS-1309 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.4.0.Final Reporter: Martin Weiler Assignee: Mario Fusco When creating rules in guided editor, we are running into validation errors depending on the order of the conditions. The problem is that the order of the conditions is important: {noformat} when COND_X COND_Y => works when COND_Y COND_X => fails java.lang.AssertionError: [10,18]: [ERR 101] Line 10:18 no viable alternative at input 'Number' in rule "ATO_Negative_AU_Test" [0,0]: Parser returned a null Package {noformat} Test cases showing the compilation failures (@Test testOrder1 vs testOrder2) can be found here: https://gist.github.com/martinweiler/e684a0e75a2c9f4de4dee5a13affb8b0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7190) Group related resources in Elytron subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7190?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7190: ----------------------------------- Forum Reference: http://lists.jboss.org/pipermail/wildfly-dev/2016-September/005487.html > Group related resources in Elytron subsystem > -------------------------------------------- > > Key: WFLY-7190 > URL: https://issues.jboss.org/browse/WFLY-7190 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Domain model of subsystem is too flat. Every resource (realms, mappers, factories ...) is located at the base level of Elytron subsystem. Then it is hard to orientate in subsystem since it does not have deeper structure. > Suggestion: > It can be structuralized similar as PicketBox subsystem. There could be some subresources like realms, domains etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7190) Group related resources in Elytron subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7190?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7190: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Group related resources in Elytron subsystem > -------------------------------------------- > > Key: WFLY-7190 > URL: https://issues.jboss.org/browse/WFLY-7190 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Domain model of subsystem is too flat. Every resource (realms, mappers, factories ...) is located at the base level of Elytron subsystem. Then it is hard to orientate in subsystem since it does not have deeper structure. > Suggestion: > It can be structuralized similar as PicketBox subsystem. There could be some subresources like realms, domains etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7190) Group related resources in Elytron subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7190?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7190: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Group related resources in Elytron subsystem > -------------------------------------------- > > Key: WFLY-7190 > URL: https://issues.jboss.org/browse/WFLY-7190 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > Domain model of subsystem is too flat. Every resource (realms, mappers, factories ...) is located at the base level of Elytron subsystem. Then it is hard to orientate in subsystem since it does not have deeper structure. > Suggestion: > It can be structuralized similar as PicketBox subsystem. There could be some subresources like realms, domains etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7229) WFLYCLWEBUT0001 for server-side invalidated sessions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7229?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-7229: ---------------------------------------- Did you mean to call this a Feature Request instead of a Bug? > WFLYCLWEBUT0001 for server-side invalidated sessions > ---------------------------------------------------- > > Key: WFLY-7229 > URL: https://issues.jboss.org/browse/WFLY-7229 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Happens whenever <distributable/> is used in web.xml, both in standalone and domain modes. > Reporter: Michał Nowakowski > Assignee: Stuart Douglas > Attachments: stacktrace_01.txt, stacktrace_02.txt, stacktrace_03.txt, testPortlet.tar.gz > > > Attached is a simple webapp (pardon the name) with a single servlet "/main", that does the following: > - a session is assigned (or created, if none existed before) > - its details are printed and the browser is told to refresh after 20 seconds > - before the browser refreshes, the session is invalidated server-side by separate thread. > Expected behaviour is, that WF should give the user a new session. That's indeed how it works in standalone mode and without <distributable/> in web.xml. But in domain mode, OR with <distributable/> added (and, possibly, full-ha profile chosen), I get errors: > - The first stacktrace happens when the thread invalidates the session. > - The second stacktrace happens, when the browser refreshes. The user sees "Error 500". > - The, after a minute or so, I get the last one. It then repeats periodically. > We can't upgrade from 10.0 because of this - and we know we need an upgrade because of fixes in Infinispan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1826) Tab completion don't return inner attributes

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1826?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1826: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1835 > Tab completion don't return inner attributes > -------------------------------------------- > > Key: WFCORE-1826 > URL: https://issues.jboss.org/browse/WFCORE-1826 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > *Description of problem:* > Tab completion returns wrong values > *How reproducible:* > Always > *Steps to Reproduce:* > {noformat} > /extension=org.wildfly.extension.elytron:add > /subsystem=elytron:add > reload > /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{permissions=[{class-name="org.wildfly.security.auth.permission.LoginPermission"}],<TAB> > {noformat} > *Actual results:* > {noformat} > /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{permissions=[{class-name="org.wildfly.security.auth.permission.LoginPermission"}],{ > {noformat} > *Expected results:* > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{permissions=[{class-name="org.wildfly.security.auth.permission.LoginPermission"}], > principals roles > [standalone@localhost:9990 /] /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{permissions=[{class-name="org.wildfly.security.auth.permission.LoginPermission"}], > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1825) Tab completion throws IllegalArgumentException after two '{' characters and '=' character

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1825?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1825: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1835 > Tab completion throws IllegalArgumentException after two '{' characters and '=' character > ----------------------------------------------------------------------------------------- > > Key: WFCORE-1825 > URL: https://issues.jboss.org/browse/WFCORE-1825 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > *Description of problem:* > This issue is similar like JBEAP-6043. Tab completion throws IllegalArgumentException after two '\{' characters and '=' character. Or tab completition returns unlimited count of ')' characters. > *How reproducible:* > Always > ---- > *1. Steps to Reproduce:* > {noformat} > Get fresh EAP. > ./standalone.sh & > ./jboss-cli.sh -c > /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{roles=[{role<TAB><TAB><TAB><TAB><TAB><TAB><TAB><TAB><TAB><TAB> > {noformat} > *1. Actual results:* > {noformat} > /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{roles=[{role)))))))))) > {noformat} > ---- > *2. Steps to Reproduce:* > {noformat} > ./standalone.sh -c standalone-elytron.xml & > ./jboss-cli.sh -c > /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{roles=[{role=<TAB> > {noformat} > *2. Actual results:* > * java.lang.IllegalArgumentException > * Details: > {noformat} > [mkopecky@dhcp-10-40-5-171 bin]$ ./jboss-cli.sh -c > [standalone@localhost:9990 /] /subsystem=elytron/simple-permission-mapper=login-permission-mapper2:add(permission-mappings=[{roles=[{role=Exception in thread "Aesh Process Loop 30318020" java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getChild(ModelValue.java:115) > at org.jboss.dmr.ModelNode.get(ModelNode.java:861) > at org.jboss.as.cli.impl.ValueTypeCompleter$ValueTypeCallbackHandler.getCandidates(ValueTypeCompleter.java:475) > at org.jboss.as.cli.impl.ValueTypeCompleter.complete(ValueTypeCompleter.java:321) > at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:254) > at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:74) > at org.jboss.as.cli.CommandCompleter.doComplete(CommandCompleter.java:137) > at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:64) > at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:143) > at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:155) > at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:427) > at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:165) > at org.jboss.aesh.console.Console.processInternalOperation(Console.java:773) > at org.jboss.aesh.console.Console.execute(Console.java:733) > at org.jboss.aesh.console.Console.access$900(Console.java:73) > at org.jboss.aesh.console.Console$6.run(Console.java:642) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > [mkopecky@dhcp-10-40-5-171 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7228) Improve wording in logging message for key WFLYWELD0013

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7228?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7228: -------------------------------------- Issue Type: Bug (was: Enhancement) Component/s: CDI / Weld Assignee: Stuart Douglas (was: Jason Greene) I added the component and changed this to 'Bug' which is a simpler issue type to deal with downstream. The repetition of 'deployment' is enough to make this a bug even though it's not the main point. > Improve wording in logging message for key WFLYWELD0013 > ------------------------------------------------------- > > Key: WFLY-7228 > URL: https://issues.jboss.org/browse/WFLY-7228 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Gunnar Morling > Assignee: Stuart Douglas > Priority: Minor > > I'm seeing this message: > {quote} > WFLYWELD0013: Deployment deployment "demo.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations) > {quote} > Apart from the repeated "deployment", the double negation makes it confusing, I reckon it should say something like that: > {quote} > WFLYWELD0013: Deployment "demo.war" contains CDI annotations but is not a bean archive (Found no beans.xml nor a class with bean defining annotations) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016