March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2404) Remove TestStatusListener from drools-compiler tests

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2404: ------------------------------------- Summary: Remove TestStatusListener from drools-compiler tests Key: DROOLS-2404 URL: https://issues.jboss.org/browse/DROOLS-2404 Project: Drools Issue Type: Bug Components: build, core engine Affects Versions: 7.6.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi We currently use our custom TestStatusListener for logging when tests start and finish. This listener is synchronized and writes to a single file, which could cause slower test execution. This listener should be bound to a Maven profile, so it can be enabled when needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2394: ---------------------------------------- The "Back to" link shows the name of the Decision on the graph. Some top-level Expression editors also show the same name in their grid (Context, Decision Table "output" column, Function, Invocation and Literal Expression). When such grid headers are updated the "Back to" link should also change - as it represents the same entity. Furthermore the name of the Node in the graph should also be updated - this is not happening either - as this too represents the same entity. Both changes ("Back to" link and Node name in graph) should respond to undo/redo along with the grid header change. > [DMN Designer] Rename of output changes back to link > ---------------------------------------------------- > > Key: DROOLS-2394 > URL: https://issues.jboss.org/browse/DROOLS-2394 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Attachments: Screenshot from 2018-03-16 12-14-13.png > > > Renaming output of decision table changes the {{back to}} link. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3701) CLI multi-page output cannot be quit by capital Q

by Erich Duda (JIRA)

Erich Duda created WFCORE-3701: ---------------------------------- Summary: CLI multi-page output cannot be quit by capital Q Key: WFCORE-3701 URL: https://issues.jboss.org/browse/WFCORE-3701 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 5.0.0.Alpha1 Reporter: Erich Duda Assignee: Jean-Francois Denise If you type capital Q to quit the multi-page output it does nothing. For example users may have Caps lock turned on. I compared the behavior with linux commands more and less and they both react to capital Q. You can reproduce this issue using following commands: {code} ./bin/jboss-cli.sh [disconnected /] embed-server [standalone@embedded /] /subsystem=elytron:read-resource-description(recursive=true) # type capital Q {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10054) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10054?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10054: ------------------------------- Summary: [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names (was: [Artemis 2.x Upgrade] Client is not able to instantiate destinations by core names) > [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names > ----------------------------------------------------------------------------- > > Key: WFLY-10054 > URL: https://issues.jboss.org/browse/WFLY-10054 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq > > Having queue defined as follows > {code:xml} > <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/> > {code} > Client is instantiating it directly using its name. > {code:title=Client} > HashMap<String, Object> map = new HashMap<String, Object>(); > map.put("host", hostName); > map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true); > map.put("port", httpPort); > TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map); > try { > ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration); > Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue"); > connection = cf.createConnection(); > session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > MessageProducer producer = session.createProducer(orderQueue); > connection.start(); > ... > {code} > Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception > {code} > javax.jms.InvalidDestinationException: Destination InQueue does not exist > at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326) > {code} > This is regression against EAP 7.1.0 > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3700) Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3700?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-3700. ------------------------------ Resolution: Done See comment on https://issues.jboss.org/browse/JBEAP-14386 ([~jamezp] will add soon), for why we don't want this > Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22 > ---------------------------------------------- > > Key: WFCORE-3700 > URL: https://issues.jboss.org/browse/WFCORE-3700 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: Panagiotis Sotiropoulos > Assignee: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3700) Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3700?page=com.atlassian.jira.plugi... ] Kabir Khan reopened WFCORE-3700: -------------------------------- > Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22 > ---------------------------------------------- > > Key: WFCORE-3700 > URL: https://issues.jboss.org/browse/WFCORE-3700 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: Panagiotis Sotiropoulos > Assignee: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3700) Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3700?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-3700. ------------------------------ Resolution: Rejected > Upgrade slf4j to 1.7.22.jbossorg-1 from 1.7.22 > ---------------------------------------------- > > Key: WFCORE-3700 > URL: https://issues.jboss.org/browse/WFCORE-3700 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: Panagiotis Sotiropoulos > Assignee: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3699) Upgrade slf4j from 1.7.22.redhat-1 to 1.7.22.redhat-2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3699?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-3699. ------------------------------ Resolution: Rejected See comment on https://issues.jboss.org/browse/JBEAP-14386 ([~jamezp] will add soon), for why we don't want this > Upgrade slf4j from 1.7.22.redhat-1 to 1.7.22.redhat-2 > ----------------------------------------------------- > > Key: WFCORE-3699 > URL: https://issues.jboss.org/browse/WFCORE-3699 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: Panagiotis Sotiropoulos > Assignee: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10054) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by core names

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFLY-10054?page=com.atlassian.jira.plugin... ] Martin Styk updated WFLY-10054: ------------------------------- Steps to Reproduce: {noformat} git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=<CURRENT_DIST_URL> PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=ArtemisClientsTestCase#testArtemisProducer -Deap7.org.jboss.qa.hornetq.apps.clients.version=<CLIENT_VERSION> | tee log {noformat} > [Artemis 2.x Upgrade] Client is not able to instantiate destinations by core names > ---------------------------------------------------------------------------------- > > Key: WFLY-10054 > URL: https://issues.jboss.org/browse/WFLY-10054 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq > > Having queue defined as follows > {code:xml} > <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/> > {code} > Client is instantiating it directly using its name. > {code:title=Client} > HashMap<String, Object> map = new HashMap<String, Object>(); > map.put("host", hostName); > map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true); > map.put("port", httpPort); > TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map); > try { > ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration); > Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue"); > connection = cf.createConnection(); > session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > MessageProducer producer = session.createProducer(orderQueue); > connection.start(); > ... > {code} > Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception > {code} > javax.jms.InvalidDestinationException: Destination InQueue does not exist > at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326) > {code} > This is regression against EAP 7.1.0 > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10054) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by core names

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10054?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10054: ------------------------------- Labels: activemq (was: ) > [Artemis 2.x Upgrade] Client is not able to instantiate destinations by core names > ---------------------------------------------------------------------------------- > > Key: WFLY-10054 > URL: https://issues.jboss.org/browse/WFLY-10054 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq > > Having queue defined as follows > {code:xml} > <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/> > {code} > Client is instantiating it directly using its name. > {code:title=Client} > HashMap<String, Object> map = new HashMap<String, Object>(); > map.put("host", hostName); > map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true); > map.put("port", httpPort); > TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map); > try { > ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration); > Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue"); > connection = cf.createConnection(); > session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > MessageProducer producer = session.createProducer(orderQueue); > connection.start(); > ... > {code} > Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception > {code} > javax.jms.InvalidDestinationException: Destination InQueue does not exist > at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326) > {code} > This is regression against EAP 7.1.0 > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018