July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10688: --------------------------------------- [~kabirkhan] Erich is on PTO. This is not a blocker for beta as however this must get fixed to WF14. > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF14 > Fix For: 14.0.0.CR1 > > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-10688: ---------------------------------- Labels: blocker-WF14 (was: ) > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF14 > Fix For: 14.0.0.CR1 > > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFLY-10688 at 7/18/18 9:32 AM: ---------------------------------------------------------------- [~kabirkhan] Erich is on PTO. This is not a blocker for beta however this must get fixed to WF14. was (Author: mnovak): [~kabirkhan] Erich is on PTO. This is not a blocker for beta as however this must get fixed to WF14. > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF14 > Fix For: 14.0.0.CR1 > > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Workbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2751?page=com.atlassian.jira.plugi... ] Alessandro Lazarotti commented on DROOLS-2751: ---------------------------------------------- [~mfusco] this is the issue that we talked about. > Workbench does not show correct message for DecisionTables with variables out of range > -------------------------------------------------------------------------------------- > > Key: DROOLS-2751 > URL: https://issues.jboss.org/browse/DROOLS-2751 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor > Affects Versions: 7.8.0.Final > Reporter: Alessandro Lazarotti > Assignee: Toni Rikkola > Attachments: 1-decision-table.png, 2-dt-source.png, 3-workbench-message.png > > > When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: > "Deficient row. > Affected rows:1 > "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." > "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." > The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. > See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Workbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2751?page=com.atlassian.jira.plugi... ] Alessandro Lazarotti updated DROOLS-2751: ----------------------------------------- Attachment: 1-decision-table.png > Workbench does not show correct message for DecisionTables with variables out of range > -------------------------------------------------------------------------------------- > > Key: DROOLS-2751 > URL: https://issues.jboss.org/browse/DROOLS-2751 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor > Affects Versions: 7.8.0.Final > Reporter: Alessandro Lazarotti > Assignee: Toni Rikkola > Attachments: 1-decision-table.png, 2-dt-source.png, 3-workbench-message.png > > > When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: > "Deficient row. > Affected rows:1 > "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." > "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." > The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. > See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Workbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2751?page=com.atlassian.jira.plugi... ] Alessandro Lazarotti updated DROOLS-2751: ----------------------------------------- Attachment: 2-dt-source.png > Workbench does not show correct message for DecisionTables with variables out of range > -------------------------------------------------------------------------------------- > > Key: DROOLS-2751 > URL: https://issues.jboss.org/browse/DROOLS-2751 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor > Affects Versions: 7.8.0.Final > Reporter: Alessandro Lazarotti > Assignee: Toni Rikkola > Attachments: 1-decision-table.png, 2-dt-source.png, 3-workbench-message.png > > > When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: > "Deficient row. > Affected rows:1 > "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." > "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." > The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. > See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Workbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2751?page=com.atlassian.jira.plugi... ] Alessandro Lazarotti updated DROOLS-2751: ----------------------------------------- Attachment: 3-workbench-message.png > Workbench does not show correct message for DecisionTables with variables out of range > -------------------------------------------------------------------------------------- > > Key: DROOLS-2751 > URL: https://issues.jboss.org/browse/DROOLS-2751 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor > Affects Versions: 7.8.0.Final > Reporter: Alessandro Lazarotti > Assignee: Toni Rikkola > Attachments: 1-decision-table.png, 2-dt-source.png, 3-workbench-message.png > > > When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: > "Deficient row. > Affected rows:1 > "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." > "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." > The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. > See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Worbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

Alessandro Lazarotti created DROOLS-2751: -------------------------------------------- Summary: Worbench does not show correct message for DecisionTables with variables out of range Key: DROOLS-2751 URL: https://issues.jboss.org/browse/DROOLS-2751 Project: Drools Issue Type: Bug Components: decision tables, Guided Decision Table Editor Affects Versions: 7.8.0.Final Reporter: Alessandro Lazarotti Assignee: Toni Rikkola When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: "Deficient row. Affected rows:1 "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2751) Workbench does not show correct message for DecisionTables with variables out of range

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2751?page=com.atlassian.jira.plugi... ] Alessandro Lazarotti updated DROOLS-2751: ----------------------------------------- Summary: Workbench does not show correct message for DecisionTables with variables out of range (was: Worbench does not show correct message for DecisionTables with variables out of range) > Workbench does not show correct message for DecisionTables with variables out of range > -------------------------------------------------------------------------------------- > > Key: DROOLS-2751 > URL: https://issues.jboss.org/browse/DROOLS-2751 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor > Affects Versions: 7.8.0.Final > Reporter: Alessandro Lazarotti > Assignee: Toni Rikkola > > When it is defined a Decision Table with rows don't covering all possible ranges, the message reported by workbench isn't clear, in fact it is a wrong message: > "Deficient row. > Affected rows:1 > "Deficient rule has *actions which conflict with another rule* and conditions that do not overlap with the other rule." > "Since *the deficient rule can fire at the same time as an another rule*, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove the deficient rule or make the conditions more strict." > The message above seems generic for cases that two rules can fire while it is expect them to be exclusive, but it is confuse for rows out-of-range. > See attachments. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-63) ConfigProperty injection for Provider<CustomClass> is not working

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-63: -------------------------------------- Summary: ConfigProperty injection for Provider<CustomClass> is not working Key: WFWIP-63 URL: https://issues.jboss.org/browse/WFWIP-63 Project: WildFly WIP Issue Type: Bug Components: MP Config Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Priority: Critical ConfigProperty injection for Provider<CustomClass> is not working Using https://github.com/rsvoboda/rsvoboda-playground/tree/master/microprofile-... application. This is working on OpenLiberty, but not on WF server. TBH I don't see reason why this shouldn't be working on WF too. First I thought it's problem in convertor not being picked up properly, but the problem seems to be triggered by https://github.com/rsvoboda/rsvoboda-playground/blob/master/microprofile-... WF throws following error when accessing http://localhost:8080/microprofile-config/config/properties {code} Caused by: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001334: Unsatisfied dependencies for type Email with qualifiers @ConfigProperty at org.jboss.weld.bean.builtin.InstanceImpl.checkBeanResolved(InstanceImpl.java:241) at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:113) at org.experiments.rsvoboda.system.SystemConfig.getEmail(SystemConfig.java:26) {code} When I change the code to avoid javax.inject.Provider usage, things start to work as expected. {code} --- src/main/java/org/experiments/rsvoboda/system/SystemConfig.java (date 1531917469000) +++ src/main/java/org/experiments/rsvoboda/system/SystemConfig.java (date 1531917469000) @@ -15,7 +15,7 @@ @Inject @ConfigProperty(name = "io_openliberty_guides_email") - private Provider<Email> email; + private Email email; public boolean isInMaintenance() { @@ -23,7 +23,7 @@ } public Email getEmail() { - return email.get(); + return email; } } {code} When trying the example please follow https://github.com/rsvoboda/rsvoboda-playground/blob/master/microprofile-... CustomConfigSource has to be adjusted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 July 2018