October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3155) [DMN Designer][Edge]

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3155: ----------------------------------- Summary: [DMN Designer][Edge] Key: DROOLS-3155 URL: https://issues.jboss.org/browse/DROOLS-3155 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.14.0.Final Environment: Windows Edge, eap-7.2 Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-10-17 13-38-40.png, Screenshot from 2018-10-17 13-38-52.png List of available data types remain shown in some cases on Edge browser. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3155) [DMN Designer][Edge] Data Type Selectbox remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3155: -------------------------------- Summary: [DMN Designer][Edge] Data Type Selectbox remains shown (was: [DMN Designer][Edge]) > [DMN Designer][Edge] Data Type Selectbox remains shown > ------------------------------------------------------ > > Key: DROOLS-3155 > URL: https://issues.jboss.org/browse/DROOLS-3155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows Edge, eap-7.2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: jomarko > Attachments: Screenshot from 2018-10-17 13-38-40.png, Screenshot from 2018-10-17 13-38-52.png > > > List of available data types remain shown in some cases on Edge browser. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3049: ----------------------------------- Priority: Minor (was: Major) > [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3049 > URL: https://issues.jboss.org/browse/DROOLS-3049 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2304) ASYM_ENCRYPT: see if FragmentedMessages are handled correctly

by Bela Ban (Jira)

Bela Ban created JGRP-2304: ------------------------------ Summary: ASYM_ENCRYPT: see if FragmentedMessages are handled correctly Key: JGRP-2304 URL: https://issues.jboss.org/browse/JGRP-2304 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Check the following scenario: * FRAG4 fragments a message into 4 FragmentedMessages * Confirm that ASYM_ENCRYPT correctly encrypts only the fragments Ditto for COMPRESS -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-458) Upgrade Clusters to OpenShift 3.11

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-458?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-458: ------------------------------------ Yes, the requirement is for Istio and Kiali to be running on Openshift 3.11 > Upgrade Clusters to OpenShift 3.11 > ---------------------------------- > > Key: SWSQE-458 > URL: https://issues.jboss.org/browse/SWSQE-458 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11200) Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration

by Petr Kremensky (Jira)

Petr Kremensky created WFLY-11200: ------------------------------------- Summary: Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration Key: WFLY-11200 URL: https://issues.jboss.org/browse/WFLY-11200 Project: WildFly Issue Type: Bug Components: JMS, Security Reporter: Petr Kremensky Assignee: Jeff Mesnil Integration code of messaging-activemq sets enabledProtocols=\["TLSv1,TLSv1.1,TLSv1.2"\] property to NettyConnector lookedup by the client. This behaviour was introduced by WFLY-9096 (https://github.com/wildfly/wildfly/pull/11673/files). https://github.com/wildfly/wildfly/pull/11673/files#diff-64b7f8a3e5eb2234... {code} parameters.putIfAbsent(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, "TLSv1,TLSv1.1,TLSv1.2"); {code} https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... {code} enabledProtocols = ConfigurationHelper.getStringProperty(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, TransportConstants.DEFAULT_ENABLED_PROTOCOLS, configuration); {code} NettyConnector prefers the enabled protocols obtained from integration code to ones defined on client side - possibly forces client to use less secured protocol than client wants. https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... {code} ... String[] originalProtocols = engine.getEnabledProtocols(); ... if (enabledProtocols != null) { // true with WFLY-9096 try { engine.setEnabledProtocols(SSLSupport.parseCommaSeparatedListIntoArray(enabledProtocols)); } catch (IllegalArgumentException e) { ActiveMQClientLogger.LOGGER.invalidProtocol(SSLSupport.parseArrayIntoCommandSeparatedList(engine.getSupportedProtocols())); throw e; } } else { engine.setEnabledProtocols(originalProtocols); } ... {code} *Reproduce* {code:bash} WORKSPACE=`pwd` WILDFLY=${WORKSPACE}/wildfly TESTSUITE=${WORKSPACE}/eap-tests-hornetq SERVERS=${WORKSPACE}/servers export JBOSS_HOME_1=${SERVERS}/server1/jboss-eap export JBOSS_HOME_2=${SERVERS}/server2/jboss-eap export JBOSS_HOME_3=${SERVERS}/server3/jboss-eap export JBOSS_HOME_4=${SERVERS}/server4/jboss-eap # setup testing server cd $WORKSPACE git clone git@github.com:wildfly/wildfly.git cd $WILDFLY mvn clean install -DskipTests -pl dist -am cd dist/target zip -r /tmp/wildfly.zip wildfly-*-SNAPSHOT # setup testsuite cd $WORKSPACE git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git mkdir $SERVERS cd $SERVERS groovy -DEAP_ZIP_URL=file:///tmp/wildfly.zip ${TESTSUITE}/scripts/PrepareServers7.groovy # run the reproducer cd $TESTSUITE/jboss-hornetq-testsuite mvn clean test -Dtest=ElytronSslAuthenticationTestCase#testOneWaySslOverSSLv3Jms -pl tests-eap7 -am {code} *Test details:* *server* supports TLSv1.1 {code:xml} <server-ssl-contexts> <server-ssl-context name="server-ssl-context" protocols="TLSv1.1" need-client-auth="false" key-manager="key-manager-name_server-ssl-context"/> </server-ssl-contexts> {code} *client* is forced (byteman rule) to use the SSLv3 *Actual:* Connection is made. *Expected:* javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3149) [DMN Designer] Context top level data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3149?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3149: -------------------------------- Description: h2. Acceptance test On Edge (/), Chrome (/) and Firefox (/) - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties was: h2. Acceptance test On Edge, Chrome (/) and Firefox (/) - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties > [DMN Designer] Context top level data type > ------------------------------------------ > > Key: DROOLS-3149 > URL: https://issues.jboss.org/browse/DROOLS-3149 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3149.png > > > h2. Acceptance test > On Edge (/), Chrome (/) and Firefox (/) > - Steps to reproduce fixed > - Opposite way, clicking row doesn't show node specific properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3049: ------------------------------------- [~manstis] I can not reproduce this according your steps because when the *Data Type Dialog* is closed also *Name and Data Type* popover hides. > [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3049 > URL: https://issues.jboss.org/browse/DROOLS-3049 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3049: ------------------------------------- I mean it is shown but overlay with *Data Type Dialog* > [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3049 > URL: https://issues.jboss.org/browse/DROOLS-3049 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11

by Francesco Nigro (Jira)

[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ] Francesco Nigro commented on WFLY-11026: ---------------------------------------- [~iweiss] I have just commented upstream a possible solution (and explanation of the issue) here: https://issues.apache.org/jira/browse/ARTEMIS-2131 > Journal compacting doesn't work with JDK 11 > ------------------------------------------- > > Key: WFLY-11026 > URL: https://issues.jboss.org/browse/WFLY-11026 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Environment: {noformat} > java 11-ea 2018-09-25 > Java(TM) SE Runtime Environment 18.9 (build 11-ea+21) > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {noformat} > Reporter: Martin Styk > Assignee: Ingo Weiss > Priority: Critical > Labels: Java11, jdk10, jdk11 > > Journal compacting doesn't work with Artemis 1.5 and JDK 11 > It fails with following stack trace: > {noformat} > 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77) > at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalArgumentException: duplicate or slice > at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238) > {noformat} > This causes issues also in scenario with journal replication. > {noformat} > 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018