August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4489) Thorntail http enpoint broken

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4489?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4489. ---------------------------------------- Resolution: Done > Thorntail http enpoint broken > ----------------------------- > > Key: DROOLS-4489 > URL: https://issues.jboss.org/browse/DROOLS-4489 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Stetson Robinson updated DROOLS-1280: ------------------------------------- Description: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. [From [~stetson.robinson]] Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." Attached the state machine diagrams from Mark for future ref, if needed. was: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. [From [~stetson.robinson]] Confirmed with Mark and Mario that the state machine diagram does not belong in the docs. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Stetson Robinson > Priority: Minor > Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png > > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. > [From [~stetson.robinson]] > Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." > Attached the state machine diagrams from Mark for future ref, if needed. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Stetson Robinson updated DROOLS-1280: ------------------------------------- Attachment: fireLoop.png fireUntilHalt and fireAllRules.png restHandler.png waitAndEnter.png > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Stetson Robinson > Priority: Minor > Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png > > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. > [From [~stetson.robinson]] > Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." > Attached the state machine diagrams from Mark for future ref, if needed. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4491) [DMN Designer] Boxed expressions - Decision Table - Input clause - Show Data Type fields automatically

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4491: --------------------------------------- Summary: [DMN Designer] Boxed expressions - Decision Table - Input clause - Show Data Type fields automatically Key: DROOLS-4491 URL: https://issues.jboss.org/browse/DROOLS-4491 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes When users select a "Structured" Data Type in a Decision Table input clause, the Data Type fields should be automatically shown as "sub-cells". ⚠️ Notice: Before starting this issue, check about a possible limitation for the number of automatically created columns. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Stetson Robinson updated DROOLS-1280: ------------------------------------- Description: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. [From [~stetson.robinson]] Confirmed with Mark and Mario that the state machine diagram does not belong in the docs. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." was: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Flow charts and state diagrams Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. [From [~stetson.robinson]] Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Stetson Robinson > Priority: Minor > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. > [From [~stetson.robinson]] > Confirmed with Mark and Mario that the state machine diagram does not belong in the docs. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Stetson Robinson updated DROOLS-1280: ------------------------------------- Description: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Flow charts and state diagrams Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. [From [~stetson.robinson]] Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." was: Spin-off remaining linked documentation work from [DROOLS-1272] for: Include docs on state machine and thread safety Flow charts and state diagrams Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Stetson Robinson > Priority: Minor > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Flow charts and state diagrams > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. > [From [~stetson.robinson]] > Note from Mark in chat: > "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety." -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1868) Fix the infinite reconnect attempts test case for udp syslog audit logging

by Justin Cook (Jira)

Justin Cook created ELY-1868: -------------------------------- Summary: Fix the infinite reconnect attempts test case for udp syslog audit logging Key: ELY-1868 URL: https://issues.jboss.org/browse/ELY-1868 Project: WildFly Elytron Issue Type: Bug Components: Audit, Testsuite Reporter: Justin Cook Assignee: Justin Cook The ```testFailureInfiniteReconnectAttempts``` test in ```SyslogAuditEndpointTest``` is currently not testing the functionality correctly but not making continuous attempts before being interrupted -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2375) Discovery: concurrent discovery doesn't work

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2375?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2375: -------------------------------- The problem was that {{Task}} (a {{Future}}) was not sortable, and so {{ConcurrentSkipListMap.findPredecesso()}} probably looped forever (see stack trace). I changed the {{ConcurrentSkipListSet}} to an {{ArrayList}}, as we only add elements and clear the list, so no sorted set functionality needed. > Discovery: concurrent discovery doesn't work > -------------------------------------------- > > Key: JGRP-2375 > URL: https://issues.jboss.org/browse/JGRP-2375 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.5 > > > If {{num_discovery_runs}} is greater than 1, then sometimes startup of a member blocks. > The stack trace below indicates this is an issue with comparison of {{Task}} ({{Future}}) elements in the ConcurrentSkipListSet. > Solution: replace the set with an ArrayList: there is no need to sort the futures, or avoid duplicates, as the list is only added to or cleared. > {noformat} > "main" #1 prio=5 os_prio=31 tid=0x00007ff886001800 nid=0x1c03 runnable [0x000070000f96f000] > java.lang.Thread.State: RUNNABLE > at java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:684) > at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:823) > at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979) > at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241) > at org.jgroups.protocols.Discovery.findMembers(Discovery.java:235) > at org.jgroups.protocols.Discovery.down(Discovery.java:380) > at org.jgroups.protocols.MERGE3.down(MERGE3.java:278) > at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:377) > at org.jgroups.protocols.FD_ALL.down(FD_ALL.java:235) > at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:102) > at org.jgroups.protocols.BARRIER.down(BARRIER.java:136) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:347) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:72) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FRAG2.down(FRAG2.java:141) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) > at org.jgroups.JChannel.down(JChannel.java:627) > at org.jgroups.JChannel._connect(JChannel.java:855) > at org.jgroups.JChannel.connect(JChannel.java:352) > - locked <0x000000079e04cfa0> (a org.jgroups.JChannel) > at org.jgroups.JChannel.connect(JChannel.java:343) > - locked <0x000000079e04cfa0> (a org.jgroups.JChannel) > at org.jgroups.tests.bla6.start(bla6.java:41) > at org.jgroups.tests.bla6.main(bla6.java:54) > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2375) Discovery: concurrent discovery doesn't work

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2375?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2375. ---------------------------- Resolution: Done > Discovery: concurrent discovery doesn't work > -------------------------------------------- > > Key: JGRP-2375 > URL: https://issues.jboss.org/browse/JGRP-2375 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.5 > > > If {{num_discovery_runs}} is greater than 1, then sometimes startup of a member blocks. > The stack trace below indicates this is an issue with comparison of {{Task}} ({{Future}}) elements in the ConcurrentSkipListSet. > Solution: replace the set with an ArrayList: there is no need to sort the futures, or avoid duplicates, as the list is only added to or cleared. > {noformat} > "main" #1 prio=5 os_prio=31 tid=0x00007ff886001800 nid=0x1c03 runnable [0x000070000f96f000] > java.lang.Thread.State: RUNNABLE > at java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:684) > at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:823) > at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979) > at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241) > at org.jgroups.protocols.Discovery.findMembers(Discovery.java:235) > at org.jgroups.protocols.Discovery.down(Discovery.java:380) > at org.jgroups.protocols.MERGE3.down(MERGE3.java:278) > at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:377) > at org.jgroups.protocols.FD_ALL.down(FD_ALL.java:235) > at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:102) > at org.jgroups.protocols.BARRIER.down(BARRIER.java:136) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:347) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:72) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FRAG2.down(FRAG2.java:141) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) > at org.jgroups.JChannel.down(JChannel.java:627) > at org.jgroups.JChannel._connect(JChannel.java:855) > at org.jgroups.JChannel.connect(JChannel.java:352) > - locked <0x000000079e04cfa0> (a org.jgroups.JChannel) > at org.jgroups.JChannel.connect(JChannel.java:343) > - locked <0x000000079e04cfa0> (a org.jgroups.JChannel) > at org.jgroups.tests.bla6.start(bla6.java:41) > at org.jgroups.tests.bla6.main(bla6.java:54) > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1867) Update the syslog audit endpoint to use the current reconnect attempts in the infinite case

by Justin Cook (Jira)

Justin Cook created ELY-1867: -------------------------------- Summary: Update the syslog audit endpoint to use the current reconnect attempts in the infinite case Key: ELY-1867 URL: https://issues.jboss.org/browse/ELY-1867 Project: WildFly Elytron Issue Type: Task Components: Audit Reporter: Justin Cook Assignee: Justin Cook Currently, the syslog audit endpoint does not keep track of the current amount of reconnect attempts if the infinite attempts ("-1") is specified. This task is to add this ability to the endpoint, along the ability to check what the current value is and for users to be able to see the current amount of attempts in the trace message if there is an error sending. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 August 2019