December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-3098: ------------------------------------ Assignee: tao zhu (was: Ivo Bek) > UX: Add support for data object List > ------------------------------------ > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps. > Preconditions: New feature of current implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2288: -------------------------------- [~nsawadsky] BTW: note that {{S3_PING}} has been deprecated and will be removed in 5.0. The replacement is {{NATIVE_S3_PING}} (in jgroups-extras). > S3_PING: Under certain conditions, subclusters fail to merge after network partition > ------------------------------------------------------------------------------------ > > Key: JGRP-2288 > URL: https://issues.jboss.org/browse/JGRP-2288 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.15 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.17 > > > Repro steps: > 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D. > 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true. > 3. Start up nodes in the order A, B, C, D. > 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'. > 5. On Host 1, use iptables to block all traffic going to and coming from Host 2. > sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP > sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP > 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket. > 7. Using Ctrl-C, stop node A. > 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket. > 9. Resolve the network partition: > sudo iptables -F OUTPUT > sudo iptables -F INPUT > 10. You will find that, even after many minutes, the subclusters are not merged. > I believe the reason why the subclusters are never merged is as follows: > - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with. > - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages. > I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there. > I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7795) org.jboss.sasl classes still making it into jboss-client.jar

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-7795?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7795: ----------------------------------- Priority: Major (was: Critical) > org.jboss.sasl classes still making it into jboss-client.jar > ------------------------------------------------------------ > > Key: WFLY-7795 > URL: https://issues.jboss.org/browse/WFLY-7795 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > > The dependencies should have been removed but maybe this is still coming in as a transitive dependency from elsewhere. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3329) [DMN Designer] Memory leak in DataTypeList

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3329?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3329: --------------------------------------- Issue Type: Enhancement (was: Bug) > [DMN Designer] Memory leak in DataTypeList > ------------------------------------------ > > Key: DROOLS-3329 > URL: https://issues.jboss.org/browse/DROOLS-3329 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Daniel José dos Santos > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > > In the "Manage Custom Data Types", if you add and remove an type, the type is not removed from memory in "DataTypeList" after you remove it, causing a leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3329) [DMN Designer] Memory leak in DataTypeList

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3329?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3329: --------------------------------------- Story Points: 2 > [DMN Designer] Memory leak in DataTypeList > ------------------------------------------ > > Key: DROOLS-3329 > URL: https://issues.jboss.org/browse/DROOLS-3329 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Daniel José dos Santos > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > > In the "Manage Custom Data Types", if you add and remove an type, the type is not removed from memory in "DataTypeList" after you remove it, causing a leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3329) [DMN Designer] Memory leak in DataTypeList

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3329?page=com.atlassian.jira.plugi... ] Guilherme Carreiro reassigned DROOLS-3329: ------------------------------------------ Assignee: Guilherme Carreiro (was: Daniel José dos Santos) > [DMN Designer] Memory leak in DataTypeList > ------------------------------------------ > > Key: DROOLS-3329 > URL: https://issues.jboss.org/browse/DROOLS-3329 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Daniel José dos Santos > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > > In the "Manage Custom Data Types", if you add and remove an type, the type is not removed from memory in "DataTypeList" after you remove it, causing a leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3358) Add possibility to choose between rule and DMN in scenario creation popup

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3358?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3358. ------------------------------------ > Add possibility to choose between rule and DMN in scenario creation popup > ------------------------------------------------------------------------- > > Key: DROOLS-3358 > URL: https://issues.jboss.org/browse/DROOLS-3358 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Modify the "new Scenario" creation popup to allow choosing between DRL/DMN. In case of DMN, allow the user to select an already uploaded DMN file -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3425?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3425: --------------------------------------- [~manstis] [~roger600] FYI I think this is related to Dock lifecycle in general, maybe Process Editor and DMN are involved too > Unexpected behavior of docks when multiple editors are opened > ------------------------------------------------------------- > > Key: DROOLS-3425 > URL: https://issues.jboss.org/browse/DROOLS-3425 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Klara Kufova > Assignee: Toni Rikkola > Priority: Critical > Labels: ScenarioSimulation > Attachments: screencast-11-12-18.webm > > > When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel. > See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8608) Must create local application user while create jms-bridge to remote queue

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8608?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-8608: -------------------------------------- [~mkrzempek] I think that the exception is caused by connecting and consuming messages from SourceQueue from local Artemis broker. If security is enabled then without providing username/password of some application user with CONSUME rights would cause this to happen. Could you share standalone...xml from source and target server, please? > Must create local application user while create jms-bridge to remote queue > -------------------------------------------------------------------------- > > Key: WFLY-8608 > URL: https://issues.jboss.org/browse/WFLY-8608 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Michał Krzempek > Assignee: ehsavoie Hugonnet > Priority: Minor > > There is a problem while I try to create JMS bridge from local queue to remote queue on different WildFly server. > WildFly server tries to authenticate user locally (event if user and password attributes are ommimted then user login is null) when target-context points to remote server. > {noformat} > 2017-04-20 08:11:19,456 ERROR [org.apache.activemq.artemis.core.server:170] (default I/O-4) AMQ224018: Failed to create session: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ119031: Unable to validate user: mdc] > at org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:135) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createSession(ActiveMQServerImpl.java:988) > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handleCreateSession(ActiveMQPacketHandler.java:153) > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handlePacket(ActiveMQPacketHandler.java:79) > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:630) > at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:347) > at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:329) > at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:619) > at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) > at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846) > at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435) > at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > 2017-04-20 08:11:19,546 WARN [org.apache.activemq.artemis.jms.bridge:1130] (ServerService Thread Pool -- 79) AMQ342010: Failed to connect JMS Bridge: javax.jms.JMSSecurityException: AMQ119031: Unable to validate user: mdc > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:406) > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:304) > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:285) > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:233) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1262) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:641) > at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:292) > at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:647) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:766) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:233) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:937) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1104) > at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.start(JMSBridgeImpl.java:383) > at org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService.startBridge(JMSBridgeService.java:105) > at org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$1.run(JMSBridgeService.java:76) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ119031: Unable to validate user: mdc] > ... 19 more > 2017-04-20 08:11:19,647 WARN [org.apache.activemq.artemis.jms.bridge:392] (ServerService Thread Pool -- 79) AMQ342001: Failed to start JMS Bridge > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-538) Move Kiali Tests to Kiali Repository

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-538?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-538. -------------------------------- Resolution: Done > Move Kiali Tests to Kiali Repository > ------------------------------------ > > Key: SWSQE-538 > URL: https://issues.jboss.org/browse/SWSQE-538 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 December 2018