September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2100) Timer: don't submit non-blocking tasks to the thread pool

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2100?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2100: -------------------------------- Instead of subclassing {{Runnable}} with something like {{BlockableRunnable}}, an additional parameter {{can_block}} will be added to methods {{execute()}}, {{schedule()}}, {{scheduleWithFixedDelay()}}, {{scheduleAtFixedRate()}} and {{scheduleRecurringTask()}}. Extending {{Runnable}} would not allow for simple lambdas to be used, but instead inner classes would have to be created. > Timer: don't submit non-blocking tasks to the thread pool > --------------------------------------------------------- > > Key: JGRP-2100 > URL: https://issues.jboss.org/browse/JGRP-2100 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > Currently, {{TimeScheduler3}} has a runner thread which continually takes tasks from a {{DelayQueue}} and submits them to the thread pool. > If a task is non-blocking, this is not necessary; instead the task can be run on the runner's thread. This will reduce the number of thread created in the thread pool. > Investigate whether it is possible to mark tasks as blocking or non-blocking. Example: an {{AgeOutCache}} task is always non-blocking. A {{UNICAST3}} or {{NAKACK2}} retransmission task is (potentially) blocking if {{TCP}} is used as transport and non-blocking if for example {{UDP}} or {{TCP_NIO2}} are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1770) Wildfly 10.1.0.FINAL does not start as a windows service

by Arthur Borsboom (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1770?page=com.atlassian.jira.plugi... ] Arthur Borsboom commented on WFCORE-1770: ----------------------------------------- Hi Tom, I see you have closed this bug report without a comment. Does this mean that this is fixed? When I download this file: http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip the file wildfly-10.1.0.Final/docs/contrib/scripts/service/service.bat still contains these two lines {code:title=wildfly-10.1.0.Final/docs/contrib/scripts/service/service.bat|borderStyle=solid} rem NO quotes around the description here ! set DESCRIPTION="WildFly Application Server" {code} which should be {code:title=wildfly-10.1.0.Final/docs/contrib/scripts/service/service.bat|borderStyle=solid} set DESCRIPTION=WildFly Application Server {code} > Wildfly 10.1.0.FINAL does not start as a windows service > -------------------------------------------------------- > > Key: WFCORE-1770 > URL: https://issues.jboss.org/browse/WFCORE-1770 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Arthur Borsboom > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 3.0.0.Alpha6 > > > The service.bat batch file to install Wildfly as a WIndows Service (still) contains a small error, preventing the service being added correctly. > This bug has been reported before and also has been reported as fixed. However the bug is still there. > WFCORE-1719 > The funny thing is that the batch file even describes in a REM statement that the line "SET DESCRIPTION" should not contain quotes. So, the fix is described, but just not applied. :) > Please remove the quotes in the next release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-6402: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1319040, https://bugzilla.redhat.com/show_bug.cgi?id=1350355, https://bugzilla.redhat.com/show_bug.cgi?id=1310908, https://bugzilla.redhat.com/show_bug.cgi?id=1359884 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1319040, https://bugzilla.redhat.com/show_bug.cgi?id=1350355, https://bugzilla.redhat.com/show_bug.cgi?id=1310908) > 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 > 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 (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7071) Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-7071?page=com.atlassian.jira.plugin.... ] Harald Pehl commented on WFLY-7071: ----------------------------------- Agreed. We should add some kind of client side validation for default-realms of security domains. I filed HAL-1179 to track this. > Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7071 > URL: https://issues.jboss.org/browse/WFLY-7071 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > Values of write-attribute operation for default-realm of Elytron security-domain are not checked. It means that CLI allows users to set application server to wrong state. The same happens if realm, which is considered as default-realm, is removed from used security-domain realms. CLI should deny write attribute operation with wrong value (in the same way as it works for another security-domain attributes). > After reload, server is not started and following logs occur in console: > {code} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 25) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "ApplicationDomain") > ]) - failure description: "WFLYELY00013: The default_realm 'WrongRealm' is not in the list or realms referenced by this domain." > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem elytron boot operations" > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem elytron boot operations\"" > FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7065) Wrong description of logical-role-mapper in model

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7065?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7065: -------------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Wrong description of logical-role-mapper in model > ------------------------------------------------- > > Key: WFLY-7065 > URL: https://issues.jboss.org/browse/WFLY-7065 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > > In output of > {noformat} > /subsystem=elytron:read-resource-description(recursive=true) > {noformat} > , there is wrong description of logical-role-mapper _A role mapper definition where a constant set of roles is always returned._ , what is probably copied from constant-role-mapper. > In XSD, there is more proper description _A RoleMapper definition for a RoleMapper that performs a logical operation using two refereced RoleMappers._ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7066) Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7066?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7066: -------------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model > ----------------------------------------------------------------------------------- > > Key: WFLY-7066 > URL: https://issues.jboss.org/browse/WFLY-7066 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > > In output of {noformat}/subsystem=elytron:read-resource-description(recursive=true){noformat} , there is wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper _"Definition of a custom RealmMapper"_ , what is probably copied from custom-realm-mapper. > In XSD, there is more proper > * mapped-regex-realm-mapper: _"A RealmMapper implementaion that first uses a regular expression to extract the realm name, this is then converted using the configured mapping of realm names."_ > * simple-regex-realm-mapper: _"A simple RealmMapper definition that attempts to extract the realm name using the capture group from the regular expression, if that does not provide a match then the delegate RealmMapper is used instead."_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7071) Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7071?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7071: ---------------------------------------- [~harald.pehl] / [~claudio4j] In this case the default-realm attribute in the security domain is required to reference one of the referenced security realms, we need some checking in our subsystem to ensure the selected realm is already referenced but as this is slightly outside capabilities and requirements I think worth flagging in case anything else is needed to make it easier to maintain integrity from admin clients. > Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7071 > URL: https://issues.jboss.org/browse/WFLY-7071 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > Values of write-attribute operation for default-realm of Elytron security-domain are not checked. It means that CLI allows users to set application server to wrong state. The same happens if realm, which is considered as default-realm, is removed from used security-domain realms. CLI should deny write attribute operation with wrong value (in the same way as it works for another security-domain attributes). > After reload, server is not started and following logs occur in console: > {code} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 25) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "ApplicationDomain") > ]) - failure description: "WFLYELY00013: The default_realm 'WrongRealm' is not in the list or realms referenced by this domain." > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem elytron boot operations" > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem elytron boot operations\"" > FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7071) Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7071?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7071: -------------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Changing default-realm of Elytron security-domain through CLI can put the server configuration to wrong state > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7071 > URL: https://issues.jboss.org/browse/WFLY-7071 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > Values of write-attribute operation for default-realm of Elytron security-domain are not checked. It means that CLI allows users to set application server to wrong state. The same happens if realm, which is considered as default-realm, is removed from used security-domain realms. CLI should deny write attribute operation with wrong value (in the same way as it works for another security-domain attributes). > After reload, server is not started and following logs occur in console: > {code} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 25) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "ApplicationDomain") > ]) - failure description: "WFLYELY00013: The default_realm 'WrongRealm' is not in the list or realms referenced by this domain." > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem elytron boot operations" > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem elytron boot operations\"" > FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1770) Wildfly 10.1.0.FINAL does not start as a windows service

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1770?page=com.atlassian.jira.plugi... ] Tomaz Cerar closed WFCORE-1770. ------------------------------- Fix Version/s: 3.0.0.Alpha6 Assignee: Tomaz Cerar (was: Jason Greene) Resolution: Duplicate Issue fixed in WFCORE-1719 > Wildfly 10.1.0.FINAL does not start as a windows service > -------------------------------------------------------- > > Key: WFCORE-1770 > URL: https://issues.jboss.org/browse/WFCORE-1770 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Arthur Borsboom > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 3.0.0.Alpha6 > > > The service.bat batch file to install Wildfly as a WIndows Service (still) contains a small error, preventing the service being added correctly. > This bug has been reported before and also has been reported as fixed. However the bug is still there. > WFCORE-1719 > The funny thing is that the batch file even describes in a REM statement that the line "SET DESCRIPTION" should not contain quotes. So, the fix is described, but just not applied. :) > Please remove the quotes in the next release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1770) Wildfly 10.1.0.FINAL does not start as a windows service

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1770?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1770: -------------------------------- Description: The service.bat batch file to install Wildfly as a WIndows Service (still) contains a small error, preventing the service being added correctly. This bug has been reported before and also has been reported as fixed. However the bug is still there. WFCORE-1719 The funny thing is that the batch file even describes in a REM statement that the line "SET DESCRIPTION" should not contain quotes. So, the fix is described, but just not applied. :) Please remove the quotes in the next release. was: The service.bat batch file to install Wildfly as a WIndows Service (still) contains a small error, preventing the service being added correctly. This bug has been reported before and also has been reported as fixed. However the bug is still there. https://issues.jboss.org/browse/WFCORE-1719 The funny thing is that the batch file even describes in a REM statement that the line "SET DESCRIPTION" should not contain quotes. So, the fix is described, but just not applied. :) Please remove the quotes in the next release. > Wildfly 10.1.0.FINAL does not start as a windows service > -------------------------------------------------------- > > Key: WFCORE-1770 > URL: https://issues.jboss.org/browse/WFCORE-1770 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Arthur Borsboom > Assignee: Jason Greene > Priority: Minor > Fix For: 3.0.0.Alpha6 > > > The service.bat batch file to install Wildfly as a WIndows Service (still) contains a small error, preventing the service being added correctly. > This bug has been reported before and also has been reported as fixed. However the bug is still there. > WFCORE-1719 > The funny thing is that the batch file even describes in a REM statement that the line "SET DESCRIPTION" should not contain quotes. So, the fix is described, but just not applied. :) > Please remove the quotes in the next release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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