March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2398: ----------------------------------- Sprint: 2018 Week 11-12 > [DMN Designer] Change of function discards width of parent column > ----------------------------------------------------------------- > > Key: DROOLS-2398 > URL: https://issues.jboss.org/browse/DROOLS-2398 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.7.0.Final > > > Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2398: -------------------------------- Steps to Reproduce: # Create new dmn diagram # Add a decision node # Open the decision node # Specify the top level entry as a Context # Then add two rows into the Context # Specify first row as a Decision table ## Add one input and one output to the Decision table # Specify second row as a Function ## Change Function to PMML or Java # Notice the width of parent column was decreased so that the decision table above is not visible appropriately was: # Create new dmn diagram # Add a decision node # Open the decision node # Specify the top level entry as a Context # Then add two rows into the Context # Specify first row as a Decision table ## Add one input and one output to the Decision table # Specify second row as a Function # Change Function to PMML or Java # Notice the width of parent column was decreased so that the decision table above is not visible appropriately > [DMN Designer] Change of function discards width of parent column > ----------------------------------------------------------------- > > Key: DROOLS-2398 > URL: https://issues.jboss.org/browse/DROOLS-2398 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.7.0.Final > > > Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2398: ----------------------------------- Summary: [DMN Designer] Change of function discards width of parent column Key: DROOLS-2398 URL: https://issues.jboss.org/browse/DROOLS-2398 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.7.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor Fix For: 7.7.0.Final Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10009) Introduce a maximum-timeout management model attribute

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10009?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10009: ----------------------------------- [~zhfeng] [~jason.greene] I think this shold really be a feature request, be cloned to the EAP7 project and follow the process at https://docs.google.com/document/d/1ps1jEcTNNJCqJjr340xvWYTD3R4VUk93udjdC... > Introduce a maximum-timeout management model attribute > ------------------------------------------------------ > > Key: WFLY-10009 > URL: https://issues.jboss.org/browse/WFLY-10009 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > > some resources may fail with a timeout value of Integer.MAX_VALUE for various reasons, so a lower "maximum" (such as one year) might be better. The purpose of the suggestion of the maximum timeout attribute would be to make this value configurable (also in the event where someone programmatically sets a timeout which might be problematic), -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2272) [DMN Editor] Move Editor controls inline

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2272?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2272. ------------------------------------ Resolution: Done > [DMN Editor] Move Editor controls inline > ---------------------------------------- > > Key: DROOLS-2272 > URL: https://issues.jboss.org/browse/DROOLS-2272 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > Expression Editors have a row of controls to add row, column, change Hit Policy etc. > These all need moving "inline" into the editor itself. -The content of the new context menu will be driven by the cell in the Expression grid that was (single) clicked. Double click continues to edit the cell.- > *New requirements* > * Context menu (single right-click) to provide the ability to cut/copy/paste/insert (row/column)/delete (row/column)/delete cell value > * Double -Single- left-click to edit a cells content (this could be an {{TextBox}} or a {{ListBox}} or a more sophisticated editor). > * Context menu entries are reflected in the state of the toolbar (menubar, whatever) in the workbench. > This means the "Undefined Expression selector" ([DROOLS-2296|https://issues.jboss.org/browse/DROOLS-2296]), "Context Editor" ([DROOLS-2297|https://issues.jboss.org/browse/DROOLS-2297]) and "Relation Editor" ([DROOLS-2299|https://issues.jboss.org/browse/DROOLS-2299]) will need refactoring. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2368) Remove HasExpressionEditorControls

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2368?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2368: -------------------------------- Description: When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. h2. Acceptance criteria: # Inline context menu can be invoked (/) -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation # Old control widgets are not present more (/) -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation was: When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. h2. Acceptance criteria: # Inline context menu can be invoked: -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation # Old control widgets are not present more -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation > Remove HasExpressionEditorControls > ---------------------------------- > > Key: DROOLS-2368 > URL: https://issues.jboss.org/browse/DROOLS-2368 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. > h2. Acceptance criteria: > # Inline context menu can be invoked (/) > -- Lit. expression > -- Context > -- Decision table > -- Relation > -- Function > -- Invocation > # Old control widgets are not present more (/) > -- Lit. expression > -- Context > -- Decision table > -- Relation > -- Function > -- Invocation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2368) Remove HasExpressionEditorControls

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2368?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2368: -------------------------------- Description: When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. h2. Acceptance criteria: # Inline context menu can be invoked: -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation # Old control widgets are not present more -- Lit. expression -- Context -- Decision table -- Relation -- Function -- Invocation was:When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. > Remove HasExpressionEditorControls > ---------------------------------- > > Key: DROOLS-2368 > URL: https://issues.jboss.org/browse/DROOLS-2368 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted. > h2. Acceptance criteria: > # Inline context menu can be invoked: > -- Lit. expression > -- Context > -- Decision table > -- Relation > -- Function > -- Invocation > # Old control widgets are not present more > -- Lit. expression > -- Context > -- Decision table > -- Relation > -- Function > -- Invocation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10043) [Artemis 2.x Upgrade] Last value queues do not work

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFLY-10043?page=com.atlassian.jira.plugin... ] Martin Styk commented on WFLY-10043: ------------------------------------ Both checks are unsuccessful, the first executed check fails the test. Calling operation {{count-messages}} on queue returns 10, but only one message is expected. If I comment out the broker side check, consumer still gets 10 messages instead of the single one. > [Artemis 2.x Upgrade] Last value queues do not work > --------------------------------------------------- > > Key: WFLY-10043 > URL: https://issues.jboss.org/browse/WFLY-10043 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq > > Last value queues are not working as expected. > # Set {{last-value-queue="true"}} for an address settings {{#}} > # Send 10 messages with {{message.setStringProperty("_AMQ_LVQ_NAME", "myProperty");}} > # Receiver receives 10 messages. (it is expected to receive the single message) > This looks like broker related regression against Artemis 1.5. > Wildfly: {{https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix}} (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10045) [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false

by Martin Styk (JIRA)

Martin Styk created WFLY-10045: ---------------------------------- Summary: [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false Key: WFLY-10045 URL: https://issues.jboss.org/browse/WFLY-10045 Project: WildFly Issue Type: Bug Components: JMS Reporter: Martin Styk Assignee: Jeff Mesnil Priority: Blocker Having a MDB configured as follows: {code} @MessageDriven(name = "mdb", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue ="InQueue"), @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), }) {code} MDB is not able to receive messages from InQueue. Server logs: {noformat} 09:53:29,128 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. 09:53:29,188 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "Mdb.jar" (runtime-name : "Mdb.jar") 09:53:29,306 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.7.Final 09:53:29,364 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/InQueue 09:53:31,366 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@2bd07716 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 09:53:31,368 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. 09:53:33,480 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. 09:53:35,092 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout. {noformat} In {{ActiveMQActivation.setup()}}, call to {{setupDestination()}} is made. Destiantion InQueue is instantiated there. However, during the {{ActiveMQMessageHandler.setup()}} call. consumer can not be created for this destination and exception {{AMQ119017: Queue InQueue does not exist}} is being thrown. {code:title=ActiveMQActivation.setup()} protected synchronized void setup() throws Exception { logger.debug("Setting up " + spec); setupCF(); setupDestination(); Exception firstException = null; for (int i = 0; i < spec.getMaxSession(); i++) { ClientSessionFactory cf = null; ClientSession session = null; try { cf = factory.getServerLocator().createSessionFactory(); session = setupSession(cf); ActiveMQMessageHandler handler = new ActiveMQMessageHandler(factory, this, ra.getTM(), (ClientSessionInternal) session, cf, i); handler.setup(); handlers.add(handler); } catch (Exception e) { ... } } ... } {code} This is regression against Artemis 1.5. Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) Artemis: upstream master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10044) enable_bundling property causes boot to fail

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-10044: ------------------------------------- Summary: enable_bundling property causes boot to fail Key: WFLY-10044 URL: https://issues.jboss.org/browse/WFLY-10044 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 12.0.0.Final Reporter: Miroslav Novak Assignee: Paul Ferraro Priority: Critical When configuring JGroups udp stack then it no longer takes property {{enable_bundling}}: {code} <stack name="udp"> <transport type="UDP" shared="false" socket-binding="jgroups-udp"> <property name="enable_bundling"> false </property> </transport> <protocol type="PING"/> <protocol type="MERGE3"/> <protocol type="FD_SOCK"/> <protocol type="FD_ALL"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK2"/> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG3"/> <protocol type="TUNNEL"> <property name="gossip_router_hosts"> 0.0.0.0[12001] </property> </protocol> </stack> {code} If it's used then server does not boot and logs error: {code} 10:15:24,324 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.activemq-cluster: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.activemq-cluster: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling] at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:103) at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99) [wildfly-clustering-service-12.0.0.Final.jar:12.0.0.Final] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling] at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:119) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:102) at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:101) ... 7 more Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling] at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:852) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final] at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:114) ... 9 more Caused by: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling] at org.jgroups.stack.Protocol.setProperties(Protocol.java:144) at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.lambda$createProtocol$0(AbstractProtocolConfigurationBuilder.java:108) at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:850) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final] ... 10 more {code} This is change and backward compatibility issue against EAP 7.1/WF11. -- 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