July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2707: ----------------------------------------- PR: https://github.com/srambach/BxMS-frontend/pull/71 > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2696) MVP Dialog to name test and define bindings (UX)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ] Liz Clayton resolved DROOLS-2696. --------------------------------- Resolution: Done OK, per Danielle > MVP Dialog to name test and define bindings (UX) > ------------------------------------------------ > > Key: DROOLS-2696 > URL: https://issues.jboss.org/browse/DROOLS-2696 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Add-simple1.png, Add-simple1b.png > > > As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-69) IndexOutOfBoundsException in JDBC HA scenario

by Miroslav Novak (JIRA)

Miroslav Novak created WFWIP-69: ----------------------------------- Summary: IndexOutOfBoundsException in JDBC HA scenario Key: WFWIP-69 URL: https://issues.jboss.org/browse/WFWIP-69 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Miroslav Novak Assignee: Martyn Taylor Priority: Blocker PR: https://github.com/wildfly/wildfly/pull/11355 *Scenario:* * There are two Wildfly servers each containing two Artemis brokers * Artemis brokers creates two live-backup pairs. Each Wildfly instance contains one live and one backup * Second server has MDB which resends messages from InQueue to OutQueue * The second server is stopped and restarted After the second server is restarted, everything works correctly for a while. Failback performs successfully, MDB resends messages. However after some time the server starts to print many errors \[1\]. It looks like some messages where corrupted during failover/failback and cannot be delivered. The reproducer always hits the issue. The issue is not relevant to particular database, I hit it with Oracle12c and DB2 11.1. I also tried to reduce amount of messages and their size, but I still hit the issue. So it is not related to paging or large messages. \[1\] {code} 15:20:50,010 ERROR [org.apache.activemq.artemis.ra] (Thread-7 (ActiveMQ-client-global-threads)) AMQ154004: Failed to deliver message: java.lang.IndexOutOfBoundsException at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:93) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:73) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:295) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-56) IndexOutOfBoundsException in JDBC HA scenario

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-56?page=com.atlassian.jira.plugin.s... ] Miroslav Novak updated WFWIP-56: -------------------------------- Labels: feature-branch-blocker (was: ) > IndexOutOfBoundsException in JDBC HA scenario > --------------------------------------------- > > Key: WFWIP-56 > URL: https://issues.jboss.org/browse/WFWIP-56 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > Labels: feature-branch-blocker > > PR: https://github.com/wildfly/wildfly/pull/11355 > *Scenario:* > * There are two Wildfly servers each containing two Artemis brokers > * Artemis brokers creates two live-backup pairs. Each Wildfly instance contains one live and one backup > * Second server has MDB which resends messages from InQueue to OutQueue > * The second server is stopped and restarted > After the second server is restarted, everything works correctly for a while. Failback performs successfully, MDB resends messages. However after some time the server starts to print many errors \[1\]. It looks like some messages where corrupted during failover/failback and cannot be delivered. > The reproducer always hits the issue. The issue is not relevant to particular database, I hit it with Oracle12c and DB2 11.1. I also tried to reduce amount of messages and their size, but I still hit the issue. So it is not related to paging or large messages. > \[1\] > {code} > 15:20:50,010 ERROR [org.apache.activemq.artemis.ra] (Thread-7 (ActiveMQ-client-global-threads)) AMQ154004: Failed to deliver message: java.lang.IndexOutOfBoundsException > at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:93) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:73) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:295) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Miroslav Novak updated WFWIP-65: -------------------------------- Labels: feature-branch-blocker (was: ) > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-68) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Miroslav Novak (JIRA)

Miroslav Novak created WFWIP-68: ----------------------------------- Summary: [Artemis 2.x upgrade] Artemis RA connections disconnected after failover Key: WFWIP-68 URL: https://issues.jboss.org/browse/WFWIP-68 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Miroslav Novak Assignee: Martyn Taylor Priority: Blocker Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) Test scenario: * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. * When all messages are sent, deploy message driven bean on Node 3. * MDB sends messages form InQueue to OutQueue. * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. * Receive messages from OutQueue from live server. Results: After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10721) service.bat script add support for environment variables

by Florent Amaridon (JIRA)

Florent Amaridon created WFLY-10721: --------------------------------------- Summary: service.bat script add support for environment variables Key: WFLY-10721 URL: https://issues.jboss.org/browse/WFLY-10721 Project: WildFly Issue Type: Feature Request Affects Versions: 13.0.0.Final, 12.0.0.Final Environment: All windows OS Reporter: Florent Amaridon Assignee: Jason Greene Priority: Minor Fix For: 14.0.0.CR1 Hello, I'm using wildly as my application server. To provide customizable configuration I want to use STANDALONE_CONF environement variable. This works fine with stanalone.bat but when I try to install wildfly as a service I can't set this environment variable to service.bat. I wrote an unpdate to service.bat to handle environment variables. Can I make a pull request on github? Best regards -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3969) ALIAS_FILTER in Elytron trustmanager ignored when crl used

by Jan Kalina (JIRA)

Jan Kalina created WFCORE-3969: ---------------------------------- Summary: ALIAS_FILTER in Elytron trustmanager ignored when crl used Key: WFCORE-3969 URL: https://issues.jboss.org/browse/WFCORE-3969 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 6.0.0.Alpha2 Reporter: Jan Kalina Assignee: Jan Kalina -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3968) Upgrade CLI to use aesh 1.7 and aesh-readline 1.10

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3968: -------------------------------------------- Summary: Upgrade CLI to use aesh 1.7 and aesh-readline 1.10 Key: WFCORE-3968 URL: https://issues.jboss.org/browse/WFCORE-3968 Project: WildFly Core Issue Type: Component Upgrade Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Required by installer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-67) IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x

by Martin Styk (JIRA)

Martin Styk created WFWIP-67: -------------------------------- Summary: IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x Key: WFWIP-67 URL: https://issues.jboss.org/browse/WFWIP-67 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Martin Styk Assignee: Martyn Taylor Priority: Blocker *Scenario:* Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them. MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B. Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6. # Client sends messages to InQueue on node A # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B # During processing of messages nodes A and C are killed # Client reads messages from OutQueue on node B. *Issue* At the end of the test, client is not able to read message {code} java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606)) at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405) at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392) at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872) at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880) at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649) at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183) at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171) at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158) at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69) at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.getMessage(ActiveMQMessageConsumer.java:224) at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132) at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151) at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 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 July 2018