November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1680) RDMA based transport

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-1680?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1680 at 11/11/19 6:43 AM: ---------------------------------------------------------- Also interesting: project Panama: http://openjdk.java.net/projects/panama/ was (Author: belaban): Aso interesting: project Panama: http://openjdk.java.net/projects/panama/ > RDMA based transport > -------------------- > > Key: JGRP-1680 > URL: https://issues.jboss.org/browse/JGRP-1680 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Investigate whether an RDMA based transport makes sense. > Advantages: > * Speed, low latency (TCP/IP is bypassed entirely) > * Low CPU usage > Disadvantages: > * JNI/C code > ** Such a transport implementation would have to live outside of the JGroups repo > ** Maintainability nightmare: the C code would also have to be ported to various OSes > *** Investigate Java based libs (IBM's jVerbs) and C based libs (Apache Portable Runtime?) > * High memory use, growing with cluster size: similarly to TCP, a 'group multicast' would involve N-1 sends. RDMA requires a Queue Pair (QP) for each destination. Each QP requires pinned memory (receive and send buffer), so each node would have to reserve (pin) N-1 memory buffers [1] > ** OTOH, we may not use many group multicasts, e.g. with Infinispan's partial replication (DIST mode) > * High cost of RDMA adapters, NICs and wiring: only a very small fraction of users would run such a transport. > [1] http://www.hpcwire.com/hpcwire/2006-08-18/a_critique_of_rdma-1.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4737) Inline accumulate with more than one variable follwed by another pattern doesn't work in executable model

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4737?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4737. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/de01a91cc28aa01e268c9e6bea33708... > Inline accumulate with more than one variable follwed by another pattern doesn't work in executable model > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4737 > URL: https://issues.jboss.org/browse/DROOLS-4737 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Push and pop expressions on context's stack are not paired correctly when processing an inline accumulate thus leading to code generation problem in the executable model when parsing a second pattern following the accumulate itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1901) Upgrade JBoss Modules to 1.9.2.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1901: ------------------------------------- Summary: Upgrade JBoss Modules to 1.9.2.Final Key: ELY-1901 URL: https://issues.jboss.org/browse/ELY-1901 Project: WildFly Elytron Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.0.CR2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11130) javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated (New Java EE 8 Security)

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11130?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-11130: ----------------------------------------- At the moment you have truncated the stack trace which is hiding a lot of useful information from me - is your deployment backed by WildFly Elytron or legacy security? > javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated (New Java EE 8 Security) > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11130 > URL: https://issues.jboss.org/browse/WFLY-11130 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.1.Final > Reporter: Instantiation Exception > Priority: Major > > I tried to use new Java EE 8 Security API and noticed that javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated. But according to JavaDoc it should return false in this situation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4739) Support Camel integration test with the executable model

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4739: ------------------------------------ Summary: Support Camel integration test with the executable model Key: DROOLS-4739 URL: https://issues.jboss.org/browse/DROOLS-4739 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni AbstractRemoteIntegrationTest in drools-jbpm-integration Still doesn't support the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 edited comment on JGRP-2375 at 11/11/19 4:59 AM: ---------------------------------------------------------- The problem was that {{Task}} (a {{Future}}) was not sortable, and so {{ConcurrentSkipListMap.findPredecessor()}} 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. was (Author: belaban): 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.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4738) Avoid double SessionContext init call during startup

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4738?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4738: --------------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) (was: 2019 Week 47-49 (from Nov 18)) > Avoid double SessionContext init call during startup > ---------------------------------------------------- > > Key: DROOLS-4738 > URL: https://issues.jboss.org/browse/DROOLS-4738 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4738) Avoid double SessionContext init call during startup

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4738: ------------------------------------------ Summary: Avoid double SessionContext init call during startup Key: DROOLS-4738 URL: https://issues.jboss.org/browse/DROOLS-4738 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4738) Avoid double SessionContext init call during startup

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4738?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4738: --------------------------------------- Sprint: 2019 Week 47-49 (from Nov 18) > Avoid double SessionContext init call during startup > ---------------------------------------------------- > > Key: DROOLS-4738 > URL: https://issues.jboss.org/browse/DROOLS-4738 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4737) Inline accumulate with more than one variable follwed by another pattern doesn't work in executable model

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4737: ----------------------------------- Summary: Inline accumulate with more than one variable follwed by another pattern doesn't work in executable model Key: DROOLS-4737 URL: https://issues.jboss.org/browse/DROOLS-4737 Project: Drools Issue Type: Bug Components: executable model Reporter: Mario Fusco Assignee: Mario Fusco Push and pop expressions on context's stack are not paired correctly when processing an inline accumulate thus leading to code generation problem in the executable model when parsing a second pattern following the accumulate itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019