August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2898) Create kie-wb-common-command-api module to reuse/refactor Stunner command classes

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2898?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2898: ---------------------------------- Story Points: 2 > Create kie-wb-common-command-api module to reuse/refactor Stunner command classes > --------------------------------------------------------------------------------- > > Key: DROOLS-2898 > URL: https://issues.jboss.org/browse/DROOLS-2898 > Project: Drools > Issue Type: Task > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Labels: ScenarioSimulationTeam > > Create kie-wb-common-command-api module to reuse/refactor Stunner command classes. > Notes and ideas about what and how to reuse that code are in this document > https://docs.google.com/document/d/1f76sz7vvZthwzqzE49-OW3N8gHJgiGRbDB5Cm... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-201) SysLogHandler doesn't log null or empty message

by Vladyslav Baidak (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-201?page=com.atlassian.jira.plugin... ] Vladyslav Baidak updated LOGMGR-201: ------------------------------------ Description: For cases when message is *null* or *empty*, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish_ method) I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler: {code:java} 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException at java.util.Optional.orElseThrow(Optional.java:290) at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28) at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) {code} As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published was: For cases when message is *null* or empty, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish _method) I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler: {code:java} 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException at java.util.Optional.orElseThrow(Optional.java:290) at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28) at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) {code} As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published > SysLogHandler doesn't log null or empty message > ----------------------------------------------- > > Key: LOGMGR-201 > URL: https://issues.jboss.org/browse/LOGMGR-201 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 2.1.4.Final > Reporter: Vladyslav Baidak > Fix For: 2.1.5.Final > > > For cases when message is *null* or *empty*, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish_ method) > I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler: > {code:java} > 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException > at java.util.Optional.orElseThrow(Optional.java:290) > at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36) > at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43) > at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49) > at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28) > at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > {code} > As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-201) SysLogHandler doesn't log null or empty message

by Vladyslav Baidak (JIRA)

Vladyslav Baidak created LOGMGR-201: --------------------------------------- Summary: SysLogHandler doesn't log null or empty message Key: LOGMGR-201 URL: https://issues.jboss.org/browse/LOGMGR-201 Project: JBoss Log Manager Issue Type: Bug Components: core Affects Versions: 2.1.4.Final Reporter: Vladyslav Baidak Fix For: 2.1.5.Final For cases when message is *null* or empty, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish _method) I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler: {code:java} 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException at java.util.Optional.orElseThrow(Optional.java:290) at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49) at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28) at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) {code} As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10899) Run MP Health TCK as part of TS execution

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-10899: ---------------------------------------- Summary: Run MP Health TCK as part of TS execution Key: WFLY-10899 URL: https://issues.jboss.org/browse/WFLY-10899 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Run MP Health TCK as part of main TS execution. Introduce new module in {{testsuite/integration}} TCK run including server boot and shutdown is ~14s -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2908) Guided Score Card can't works in 7.9.0.Final and 7.10.0.Final

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2908?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2908: -------------------------------------- Assignee: Lance Leverich (was: Michael Anstis) > Guided Score Card can't works in 7.9.0.Final and 7.10.0.Final > ------------------------------------------------------------- > > Key: DROOLS-2908 > URL: https://issues.jboss.org/browse/DROOLS-2908 > Project: Drools > Issue Type: Bug > Components: Guided Score Card Editor, XLS Score Card Editor > Affects Versions: 7.9.0.Final, 7.10.0.Final > Reporter: yi gong > Assignee: Lance Leverich > Priority: Blocker > > Guided Score Card can't work in 7.9.0.Final and 7.10.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Erich Duda commented on WFWIP-90: --------------------------------- Thanks [~pferraro] you can find the logs in a run \[1\]. \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, Clustering > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-21) [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFWIP-21?page=com.atlassian.jira.plugin.s... ] Martin Simka commented on WFWIP-21: ----------------------------------- [~tomjenkinson] you should be able to access that page via pure http - http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/mnovak-verifier-a... > [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load > --------------------------------------------------------------------------------- > > Key: WFWIP-21 > URL: https://issues.jboss.org/browse/WFWIP-21 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Test scenario: > * Start cluster A of nodes node-1, node-3 > * Start cluster B of nodes node-2, node-4 > * Send messages to queue on node-1 > * Deploy mdbs to servers in cluster A. This mdb reads messages from local queue, sends them to remote queue on cluster B and inserts them into database > * Deploy mdbs to servers in cluster B. This mdb reads messages from local queue and inserts them into database > * Cause CPU overload (for 5 min) on server node-2 when mdbs on cluster1 and 2 are processing mesages > * Restart failed server > * Let MDBs to process remaining messages > Pass Criteria: Number of sent message is equal number of records(lines) in database and messages in > Actual Result: > Sometimes happens that one record is missing in database which means that one message was not processed be MDB in cluster 2. > This looks like broker related regression against Artemis 1.5. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis tag 2.5.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2901) Implement a recursive expression builder component

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2901?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2901: ---------------------------------- Story Points: 5 > Implement a recursive expression builder component > --------------------------------------------------- > > Key: DROOLS-2901 > URL: https://issues.jboss.org/browse/DROOLS-2901 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Add logic/behaviour to the static expression builder component: > 1. Support infinite number of nested levels > 2. Load data from DMO -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2900) Implement a static expression builder component

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2900?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2900: ---------------------------------- Story Points: 2 > Implement a static expression builder component > ----------------------------------------------- > > Key: DROOLS-2900 > URL: https://issues.jboss.org/browse/DROOLS-2900 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Implement a static expression builder component using HTML/CSS proposed in this ticket DROOLS-2784 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2868) Use final HTML/CSS on right panel

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2868?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2868: ---------------------------------- Story Points: 3 > Use final HTML/CSS on right panel > ---------------------------------- > > Key: DROOLS-2868 > URL: https://issues.jboss.org/browse/DROOLS-2868 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Update HTML/CSS of right panel to use the final design -- 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