April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8613) Create test case for Elytron Aggregate Realm

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8613: ---------------------------------- Summary: Create test case for Elytron Aggregate Realm Key: WFLY-8613 URL: https://issues.jboss.org/browse/WFLY-8613 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondrej Lukas Create test case for Elytron Aggregate Realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8612) Create test case for Elytron Ldap Realm

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8612?page=com.atlassian.jira.plugin.... ] Ondrej Lukas reassigned WFLY-8612: ---------------------------------- Assignee: Ondrej Lukas > Create test case for Elytron Ldap Realm > --------------------------------------- > > Key: WFLY-8612 > URL: https://issues.jboss.org/browse/WFLY-8612 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > > Create basic test case for Elytron Ldap Realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8612) Create test case for Elytron Ldap Realm

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8612: ---------------------------------- Summary: Create test case for Elytron Ldap Realm Key: WFLY-8612 URL: https://issues.jboss.org/browse/WFLY-8612 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondrej Lukas Create basic test case for Elytron Ldap Realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8611) Create test cases for Elytron Role Decoders

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8611?page=com.atlassian.jira.plugin.... ] Ondrej Lukas reassigned WFLY-8611: ---------------------------------- Assignee: Ondrej Lukas > Create test cases for Elytron Role Decoders > ------------------------------------------- > > Key: WFLY-8611 > URL: https://issues.jboss.org/browse/WFLY-8611 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > > Create test cases for following Elytron Role Decoders: > * simple-role-decoder -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8611) Create test cases for Elytron Role Decoders

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8611: ---------------------------------- Summary: Create test cases for Elytron Role Decoders Key: WFLY-8611 URL: https://issues.jboss.org/browse/WFLY-8611 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondrej Lukas Create test cases for following Elytron Role Decoders: * simple-role-decoder -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-1330: ------------------------------------------- It seems that the ContenRepositoryCleaner might be executing after the shutdown, keeping the ExecutorService running. We need to properly 'lock' the ContentRepository once its service is stopped. > Deployment error after reboot [WFLYSRV0137] > ------------------------------------------- > > Key: WFCORE-1330 > URL: https://issues.jboss.org/browse/WFCORE-1330 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.2.Final > Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65 > Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance. > Reporter: Tobi Tobias > Assignee: ehsavoie Hugonnet > Priority: Critical > Attachments: server.log, server.log > > > I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE). > After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred. > But if I restart the server now, I get following error message: > 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart." > 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot. > The only way to fix the configuration is to manually remove the deployments from the standalone.xml. > But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-1330: -------------------------------------- Forum Reference: https://developer.jboss.org/message/970763, https://developer.jboss.org/thread/269789 (was: https://developer.jboss.org/message/956219#956219) > Deployment error after reboot [WFLYSRV0137] > ------------------------------------------- > > Key: WFCORE-1330 > URL: https://issues.jboss.org/browse/WFCORE-1330 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.2.Final > Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65 > Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance. > Reporter: Tobi Tobias > Assignee: ehsavoie Hugonnet > Priority: Critical > Attachments: server.log, server.log > > > I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE). > After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred. > But if I restart the server now, I get following error message: > 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart." > 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot. > The only way to fix the configuration is to manually remove the deployments from the standalone.xml. > But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1225) Add options to specify the salience range of rules in a Decision Table Sheet

by Osamu Kuniyasu (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1225?page=com.atlassian.jira.plugi... ] Osamu Kuniyasu commented on DROOLS-1225: ---------------------------------------- Hi, Mario, Yes, correct. > Add options to specify the salience range of rules in a Decision Table Sheet > ---------------------------------------------------------------------------- > > Key: DROOLS-1225 > URL: https://issues.jboss.org/browse/DROOLS-1225 > Project: Drools > Issue Type: Feature Request > Components: decision tables > Affects Versions: 6.4.0.Final > Environment: any > Reporter: Osamu Kuniyasu > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > When we set Sequential=true in RuleSet properties. > The salience of the generated rules are started from 65518 and down one by one. > When we mix several Decision Table Sheets and DRL rules in a Ruleflow-Group (Agenda-Group), We could not make these rules' salience order, because each Decision Table Sheet has fixed to start from 65518. > A (limited) workaround is to have separated Ruleflow-Groups, > But this way does not solve the situation to back to the higher priority rules as it's previous Ruleflow-Group. > To solve The request is that add two options into RuleSet properties. like, > SequentialMaxPriority 10000 > SequentialMinPriority 1000 > By this optional properties, we can control the range of the salience of rules in the Decision Table Sheet. and it is possible safely to mix multiple Decision Table Sheets in a Ruleflow-Group. > The SequentialMaxPriority is used to set the start value of the salience instead of 65518. > The SequentialMinPriority is used to check if this minimum salience value is not violated in the Decision Table Compiler. (if it's violated, compilation error occurs.) > Best Regards, > Osamu Kuniyasu -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1225) Add options to specify the salience range of rules in a Decision Table Sheet

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1225?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1225: ------------------------------------- Hi [~kuniyasu], if I'm understanding correctly what you're asking here is adding those new SequentialMaxPriority and SequentialMinPriority optional fields in the "RuleSet" section of the XLS for each sheet and setting the salience of the generated rules accordingly. Can you confirm? > Add options to specify the salience range of rules in a Decision Table Sheet > ---------------------------------------------------------------------------- > > Key: DROOLS-1225 > URL: https://issues.jboss.org/browse/DROOLS-1225 > Project: Drools > Issue Type: Feature Request > Components: decision tables > Affects Versions: 6.4.0.Final > Environment: any > Reporter: Osamu Kuniyasu > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > When we set Sequential=true in RuleSet properties. > The salience of the generated rules are started from 65518 and down one by one. > When we mix several Decision Table Sheets and DRL rules in a Ruleflow-Group (Agenda-Group), We could not make these rules' salience order, because each Decision Table Sheet has fixed to start from 65518. > A (limited) workaround is to have separated Ruleflow-Groups, > But this way does not solve the situation to back to the higher priority rules as it's previous Ruleflow-Group. > To solve The request is that add two options into RuleSet properties. like, > SequentialMaxPriority 10000 > SequentialMinPriority 1000 > By this optional properties, we can control the range of the salience of rules in the Decision Table Sheet. and it is possible safely to mix multiple Decision Table Sheets in a Ruleflow-Group. > The SequentialMaxPriority is used to set the start value of the salience instead of 65518. > The SequentialMinPriority is used to check if this minimum salience value is not violated in the Decision Table Compiler. (if it's violated, compilation error occurs.) > Best Regards, > Osamu Kuniyasu -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8610) Incorrect time unit in description of attribute slow-consumer-check-period

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-8610?page=com.atlassian.jira.plugin.... ] Ingo Weiss moved JBEAP-10461 to WFLY-8610: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8610 (was: JBEAP-10461) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: (was: 7.1.0.DR14) > Incorrect time unit in description of attribute slow-consumer-check-period > -------------------------------------------------------------------------- > > Key: WFLY-8610 > URL: https://issues.jboss.org/browse/WFLY-8610 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Ingo Weiss > Assignee: Ingo Weiss > > Slow consumer check period is configured in seconds. However, description of attribute {{slow-consumer-check-period}} says it is configured in minutes. > {noformat}/subsystem=messaging-activemq/server=default/address-setting=#:read-resource-description{noformat} > {panel} > .... > "slow-consumer-check-period" => { > "type" => LONG, > "description" => "How often to check for slow consumers on a particular queue.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => 5L, > {color:#d04437}"unit" => "MINUTES",{color} > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > .... > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017