December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6727) Transaction resource definition missing validator for default timeout

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6727?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6727: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Transaction resource definition missing validator for default timeout > --------------------------------------------------------------------- > > Key: WFLY-6727 > URL: https://issues.jboss.org/browse/WFLY-6727 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.Final > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Minor > Fix For: 11.0.0.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > {{TransactionSubsystemRootResourceDefinition}} is missing a validator for {{default-timeout}}. This affects web console when something bigger than a 32-bit integer is entered. I see no specification but I'm assuming (0,MAX_INT) is the expected range. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6402: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > EJBs accessible too early (spec violation) > ------------------------------------------ > > Key: WFLY-6402 > URL: https://issues.jboss.org/browse/WFLY-6402 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Fedor Gavrilov > Labels: downstream_dependency > Fix For: 11.0.0.Final > > Attachments: auto-test-reproducer.zip > > > {code} > EJB 3.1 spec, section 4.8.1: > "If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application. > {code} > Wildlfy does not implement this correctly, and allows calls to other EJBs before a @Startup @Singleton finishes its @PostConstruct call. > This Jira ticket handles two PR's on WFLY: > https://github.com/wildfly/wildfly/pull/8824 (that is already merged) > and https://github.com/wildfly/wildfly/pull/8989 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6142) [Migration] StuckThreadDetectionValve is not automatically migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6142?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6142: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > [Migration] StuckThreadDetectionValve is not automatically migrated > ------------------------------------------------------------------- > > Key: WFLY-6142 > URL: https://issues.jboss.org/browse/WFLY-6142 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 11.0.0.Final > > > {{org.apache.catalina.valves.StuckThreadDetectionValve}} is not automatically migrated even though there exists equivalent handler in EAP7 ({{io.undertow.server.handlers.StuckThreadDetectionHandler}}). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7097) The constant-role-mapper is not able to handle role name with space in it

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-7097?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-7097: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > The constant-role-mapper is not able to handle role name with space in it > ------------------------------------------------------------------------- > > Key: WFLY-7097 > URL: https://issues.jboss.org/browse/WFLY-7097 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Final > > > Adding a role with a space in the name results in 2 roles (for parts of the name) added. The problem is visible after server reload. E.g. adding role "JBoss Admin" results in 2 roles assigned "JBoss" and "Admin" > *Expected behavior* > Spaces in role name must be supported and correctly handled. E.g. After adding "JBoss Admin" and server reload "JBoss Admin" is assigned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8176) CS tool, --salt and --iteration parameters unintentionally required

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8176?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8176: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > CS tool, --salt and --iteration parameters unintentionally required > ------------------------------------------------------------------- > > Key: WFLY-8176 > URL: https://issues.jboss.org/browse/WFLY-8176 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Peter Skopek > Priority: Blocker > Labels: credential-store > Fix For: 11.0.0.Final > > > Any command have to contain --salt and --iteration parameters to be sucessfull, otherwise NPE occures. However this parameters are necesarry only in margin case > {code} > [mchoma@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary > Exception in thread "main" java.lang.NullPointerException > at java.util.regex.Matcher.getTextLength(Matcher.java:1283) > at java.util.regex.Matcher.reset(Matcher.java:309) > at java.util.regex.Matcher.<init>(Matcher.java:229) > at java.util.regex.Pattern.matcher(Pattern.java:1093) > at java.util.Formatter.parse(Formatter.java:2547) > at java.util.Formatter.format(Formatter.java:2501) > at java.io.PrintStream.format(PrintStream.java:970) > at java.io.PrintStream.printf(PrintStream.java:871) > at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:58) > {code} > with these parameters command success > {code} > [mchoma@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt 12345678 --iteration 230 > Alias "myalias" has been successfully stored > Credential store command summary: > -------------------------------------- > /subsystem=elytron/credential-store=test:add(uri="cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="MASK-uNWeyrmbByBEjgZM1FAPQW==;12345678;230"}) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8983) ReplicatedJournal class - disabled trace logging

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8983?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8983: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > ReplicatedJournal class - disabled trace logging > ------------------------------------------------ > > Key: WFLY-8983 > URL: https://issues.jboss.org/browse/WFLY-8983 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 11.0.0.Final > > > There is disabled logging of {{ReplicatedJournal}} due to hardcoded value: > {code} > private static final boolean trace = false; > {code} > Every trace log can never be logged: > {code} > if (ReplicatedJournal.trace) { > ReplicatedJournal.trace("Append record id = " + id + " recordType = " + recordType); > } > {code} > This is not ideal for investivatigation purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6177) WF 10 documentation references CDI 1.0 spec

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6177?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6177: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > WF 10 documentation references CDI 1.0 spec > ------------------------------------------- > > Key: WFLY-6177 > URL: https://issues.jboss.org/browse/WFLY-6177 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Tomas Remes > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 11.0.0.Final > > > It is referenced at https://docs.jboss.org/author/display/WFLY10/CDI+Reference. In fact WF 10 includes CDI 1.2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6620: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5499) Channel end notification received, closing channel ... should be logged at debug in EjbLogger

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5499?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-5499: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Channel end notification received, closing channel ... should be logged at debug in EjbLogger > --------------------------------------------------------------------------------------------- > > Key: WFLY-5499 > URL: https://issues.jboss.org/browse/WFLY-5499 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Takayuki Konishi > Fix For: 11.0.0.Final > > > Remote naming is logging this at ERROR, though it seems normal and no adverse effects are apparent, we should log it at debug instead of error. > {code} > ERROR [org.jboss.as.ejb3] (Remoting "master@ap02:server-apip" task-2) JBAS014141: Channel end notification received, closing channel Channel ID 6b8f00d7 (inbound) of Remoting connection 36e4f81b to /192.168.1.10:64354 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3978) PicketLink Subsystem EAP 6.4 Issues

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3978?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3978: ----------------------------- Fix Version/s: 11.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > PicketLink Subsystem EAP 6.4 Issues > ----------------------------------- > > Key: WFLY-3978 > URL: https://issues.jboss.org/browse/WFLY-3978 > Project: WildFly > Issue Type: Task > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 December 2017