August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2795) [DMN Designer] Data-types: Grid: DecisionTable

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2795?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2795: ----------------------------------- Sprint: 2018 Week 36-38 (was: 2018 Week 30-32) > [DMN Designer] Data-types: Grid: DecisionTable > ---------------------------------------------- > > Key: DROOLS-2795 > URL: https://issues.jboss.org/browse/DROOLS-2795 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > *_Decision Table_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns > - (x) {{InputClause}} columns header should show Input Data Type > - (x) {{InputClause}} columns should support changing the Input Data Type > - (x) {{OutputClause}} columns header should show Output Data Type > - (x) {{OutputClause}} columns should support changing the Output Data Type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-28) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

by Francesco Nigro (JIRA)

[ https://issues.jboss.org/browse/WFWIP-28?page=com.atlassian.jira.plugin.s... ] Francesco Nigro commented on WFWIP-28: -------------------------------------- [~mnovak] I think that it could depend by several factors: Netty (newer version) default configuration changes/behaviours, NIO that is now performing per-thread pooling (it could put more pressure on compaction), etc etc The point is that if something in the broker has changed to make it more resource hungry is not trivial to find the reason: just consider how the GC work... The new versions of the broker perform much less minor garbage collector pause than 1.x that means that the native memory have much less chances to be cleaned up (a minor GC will clean up native memory and file descriptors/sockets), leading to higher peak of resource utilisations. Having less pauses is a pure optimisation that turn to put more pressure on native resources, but I can't consider that an "issue" per se. > [Artemis 2.x upgrade] Unexptected crash of server in SOAK test > -------------------------------------------------------------- > > Key: WFWIP-28 > URL: https://issues.jboss.org/browse/WFWIP-28 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Francesco Nigro > Priority: Blocker > Labels: feature-branch-blocker > Attachments: sosreport-rvaisdebug.asd-20180807101658.tar.xz > > > After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. > Test Scenario: > * Start 2 servers > * Client sends messages to input queue. Messages then go through: > * One server to another through MDB reading and sending them from remote container through resource adapter > * Messages are forwarded from one server to another over JMS bridge and back over Core bridge > * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client > * Messages are read from the destination with stateless EJB and sent back to clients > * Client reads the messages after the pass through all the soak modules. > Pass Criteria: In the last step receiver consumes all messages sent by producer. > Actual Result: > After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. > 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)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2870) [DMN Designer] Can not build project with multiple models

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2870?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2870: ----------------------------------- Sprint: 2018 Week 30-32 > [DMN Designer] Can not build project with multiple models > --------------------------------------------------------- > > Key: DROOLS-2870 > URL: https://issues.jboss.org/browse/DROOLS-2870 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-08-09 10-20-16.png > > > If the project contains multiple dmn models, it can not be built. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-94) [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery

by Roman Vais (JIRA)

[ https://issues.jboss.org/browse/WFWIP-94?page=com.atlassian.jira.plugin.s... ] Roman Vais closed WFWIP-94. --------------------------- Resolution: Duplicate Issue I wanted to duplicate this for ENTMQBR project ... > [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery > ----------------------------------------------------------------------------------------------- > > Key: WFWIP-94 > URL: https://issues.jboss.org/browse/WFWIP-94 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Roman Vais > Assignee: Martyn Taylor > Priority: Blocker > > When 3rd party tool send multicast messages to Artemis which is configured with UDP Disovery and JGroups Discovery, Artemis creates a huge byte array at receiving the unexpected multicast message. So, it results in heap memory exhaustion, full GC and OutOfMemoryError in the worst case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-94) [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery

by Roman Vais (JIRA)

Roman Vais created WFWIP-94: ------------------------------- Summary: [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery Key: WFWIP-94 URL: https://issues.jboss.org/browse/WFWIP-94 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Roman Vais Assignee: Martyn Taylor Priority: Blocker When 3rd party tool send multicast messages to Artemis which is configured with UDP Disovery and JGroups Discovery, Artemis creates a huge byte array at receiving the unexpected multicast message. So, it results in heap memory exhaustion, full GC and OutOfMemoryError in the worst case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-91) [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery

by Roman Vais (JIRA)

[ https://issues.jboss.org/browse/WFWIP-91?page=com.atlassian.jira.plugin.s... ] Roman Vais commented on WFWIP-91: --------------------------------- AMQ 7.2.0 CR5 fails, but upstream master where above mentioned PR was merged yesterday it is fixed ... > [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery > ----------------------------------------------------------------------------------------------- > > Key: WFWIP-91 > URL: https://issues.jboss.org/browse/WFWIP-91 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > When 3rd party tool send multicast messages to Artemis which is configured with UDP Disovery and JGroups Discovery, Artemis creates a huge byte array at receiving the unexpected multicast message. So, it results in heap memory exhaustion, full GC and OutOfMemoryError in the worst case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-377) Research Openshift Flexy Installer As OSOOS Replacement

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-377?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-377: ------------------------------------ [https://mojo.redhat.com/docs/DOC-1173234|https://mojo.redhat.com/docs/DOC...] > Research Openshift Flexy Installer As OSOOS Replacement > ------------------------------------------------------- > > Key: SWSQE-377 > URL: https://issues.jboss.org/browse/SWSQE-377 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > OSOOS will be decommissioned at some point. The Openshift flexy installer is 'said' to be able to install onto Openstack. Thus this task is to research OS Flexy installer to determine if it can be used as an OSOOS replacement. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-83) [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-83?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-83: ---------------------------------- I have comment on the ARTEMIS issue that caused the regression as I disagree with it: https://issues.apache.org/jira/browse/ARTEMIS-1206?focusedCommentId=16574... > [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection > -------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-83 > URL: https://issues.jboss.org/browse/WFWIP-83 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > There is regression TCK 7 when running WF/EAP with Artemis 2.x resource adapter against AMQ 7.2.0.GA. WF/EAP with Artemis 2.x is last build from [2018-08-06]: > https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-... > There are approximately 200 failures with exception: > {code} > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) 08-03-2018 09:55:10: SVR-ERROR: javax.jms.InvalidClientIDException: clientID=cts was already set into another connection > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.validateClientID(ActiveMQConnection.java:266) > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:681) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:849) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXATopicConnection(ActiveMQConnectionFactory.java:387) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:745) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.<init>(ActiveMQRAManagedConnection.java:161) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(Semaphor > eConcurrentLinkedDequeManagedConnectionPool.java:1326) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinke > dDequeManagedConnectionPool.java:499) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604) > [javatest.batch] ESC[0mESC[0m09:55:10,606 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:751) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.validateUser(ActiveMQRAConnectionFactoryImpl.java:475) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.createTopicConnection(ActiveMQRAConnectionFactoryImpl.java:217) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.testInitForT(TransactionTests.java:354) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.Test06(TransactionTests.java:634) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at java.lang.reflect.Method.invoke(Method.java:498) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.EETest.run(EETest.java:550) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.tests.common.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:70) > {code} > Note that TCK 7 is passing when trying with current Wildfly master (Artemis 1.5.5.012). > Link to TCK 7 job: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-377) Research Openshift Flexy Installer As OSOOS Replacement

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-377: ---------------------------------- Summary: Research Openshift Flexy Installer As OSOOS Replacement Key: SWSQE-377 URL: https://issues.jboss.org/browse/SWSQE-377 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley OSOOS will be decommissioned at some point. The Openshift flexy installer is 'said' to be able to install onto Openstack. Thus this task is to research OS Flexy installer to determine if it can be used as an OSOOS replacement. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-219) Resesarch Openshift Flexy Installer

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-219: --------------------------------------- Summary: Resesarch Openshift Flexy Installer Key: HAWKULARQE-219 URL: https://issues.jboss.org/browse/HAWKULARQE-219 Project: Hawkular QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley OSOOS will be decommissioned at some point. The Openshift flexy installer is 'said' to be able to install onto Openstack. Thus this task is to research OS Flexy installer to determine if it can be used as an OSOOS replacement. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018