October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3038) [DMN Designer] Added type can not be resolved

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3038: ----------------------------------- Attachment: DROOLS-3038.dmn > [DMN Designer] Added type can not be resolved > --------------------------------------------- > > Key: DROOLS-3038 > URL: https://issues.jboss.org/browse/DROOLS-3038 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Blocker > Labels: drools-tools > Attachments: DROOLS-3038.dmn, Screenshot from 2018-09-26 12-57-20.png, Screenshot from 2018-09-26 12-58-02.png, Screenshot from 2018-09-26 12-58-12.png > > > {{12:53:34,884 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 3) Unable to resolve type reference 'tNum' on node 'Decision-1'}} is error shown to user after reopening DMN model with used new defined item definition. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10469) Dropped message did not match the computed checksum

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10469?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10469: --------------------------------------- [~tommaso-borgato] Should this be closed? > Dropped message did not match the computed checksum > --------------------------------------------------- > > Key: WFLY-10469 > URL: https://issues.jboss.org/browse/WFLY-10469 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Romain Pelisse > Assignee: Paul Ferraro > Priority: Major > > We saw this error during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) (21 occurences). > The error started to occur on *server* > {code} > 04:42:59,767 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-20,ee,perf21) perf21: exception occurred decrypting message > [JBossINF] 04:42:59,768 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: dropped message from perf20 as the message's checksum (3775292975120264796) did not match the computed checksum (2347657351) > [JBossINF] 04:42:59,768 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: unrecognized cipher; discarding message from perf20 > {code} > together with decrypting WARN messages 2 seconds after new cluster view was received: > {code} > 04:42:57,878 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-6,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf19|4] (3) [perf19, perf21, perf20] > {code} > Link to server log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov... > Client did not log any error at that time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10469) Dropped message did not match the computed checksum

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10469?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-10469: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Dropped message did not match the computed checksum > --------------------------------------------------- > > Key: WFLY-10469 > URL: https://issues.jboss.org/browse/WFLY-10469 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Romain Pelisse > Assignee: Radoslav Husar > Priority: Major > > We saw this error during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) (21 occurences). > The error started to occur on *server* > {code} > 04:42:59,767 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-20,ee,perf21) perf21: exception occurred decrypting message > [JBossINF] 04:42:59,768 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: dropped message from perf20 as the message's checksum (3775292975120264796) did not match the computed checksum (2347657351) > [JBossINF] 04:42:59,768 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: unrecognized cipher; discarding message from perf20 > {code} > together with decrypting WARN messages 2 seconds after new cluster view was received: > {code} > 04:42:57,878 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-6,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf19|4] (3) [perf19, perf21, perf20] > {code} > Link to server log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov... > Client did not log any error at that time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-462) Update Istio Upstream Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-462?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-462. ------------------------------------------- Resolution: Done > Update Istio Upstream Job > ------------------------- > > Key: SWSQE-462 > URL: https://issues.jboss.org/browse/SWSQE-462 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Istio Upstream job is fixed on Istio 1.0.2 version. > That needs to be updated in order to permit using another versions of istio -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3170) Remove scrolling bar from right panel

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3170: ---------------------------------------- Summary: Remove scrolling bar from right panel Key: DROOLS-3170 URL: https://issues.jboss.org/browse/DROOLS-3170 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Remove scrolling bar from Right panel -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3162) Resolve Table (grid) width for Scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3162?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3162: ------------------------------------- Parent: DROOLS-3154 Issue Type: Sub-task (was: Enhancement) > Resolve Table (grid) width for Scenario > --------------------------------------- > > Key: DROOLS-3162 > URL: https://issues.jboss.org/browse/DROOLS-3162 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Ivo Bek > Priority: Major > Labels: UX-CSS > > Table does not extend to the full width of the canvas area, which in the default view creates a gap between the table and the right panel. This could affect usability as the visual association and proximity between the selected cell and the input area (in the right panel) is reduced. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3169?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3169: ------------------------------------- [~manstis] Based on my understanding of the discussion today, folks preferred the following options in this order: # Merge the cells into a single Results value cell. # If not possible, make gray default read-only. Does that sound about right [~tirelli] ^^ In addition, I believe that [~tirelli] said that the "Results" row doesn’t need a “label.” > [DMN Designer] Last Context Entry differentiation > ------------------------------------------------- > > Key: DROOLS-3169 > URL: https://issues.jboss.org/browse/DROOLS-3169 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-22 17-35-07.png > > > The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change. > We should improve this in one of the following ways: > - Keep name *Default*, change font to italics and use grey background color > - Merge the *Default* and *Value* cells of last entry and remove the name *Default* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11190) SAR jboss-service MBean start with @Postconstruct annotation called twice.

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11190?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-11190. ------------------------------------- Resolution: Won't Fix This is a fair enough point but I don't foresee anything being done about this. An application written this way is mixing two different component models. Adjusting the two subsystems so they are somehow aware of each other and coordinate is likely to be complex and a source of bugs. > SAR jboss-service MBean start with @Postconstruct annotation called twice. > -------------------------------------------------------------------------- > > Key: WFLY-11190 > URL: https://issues.jboss.org/browse/WFLY-11190 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Wozza Xing > Assignee: Jason Greene > Priority: Minor > > Start and stop are "magic" method names for jboss services. > As a result the method is invoked twice. > I would expect the object has already started, so why call it again. > This is the same for Predestroy and stop() method. > In WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting > @PostConstruct > public void start() { > logger.info(this.hashCode() + "configuration for " + this.getBaseDir() + " " + System.getProperties().getProperty("jboss.server.config.dir")); > } > Output is > (ServerService Thread Pool -- 69) 2034435521 configuration for /opt/wildfly/standalone/configuration /opt/wildfly/standalone/configuration > (ServerService Thread Pool -- 69) 2034435521 configuration for /opt/wildfly/standalone/configuration /opt/wildfly/standalone/configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11190) SAR jboss-service MBean start with @Postconstruct annotation called twice.

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11190?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11190: ------------------------------------ Estimated Difficulty: High (was: Low) > SAR jboss-service MBean start with @Postconstruct annotation called twice. > -------------------------------------------------------------------------- > > Key: WFLY-11190 > URL: https://issues.jboss.org/browse/WFLY-11190 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Wozza Xing > Assignee: Jason Greene > Priority: Minor > > Start and stop are "magic" method names for jboss services. > As a result the method is invoked twice. > I would expect the object has already started, so why call it again. > This is the same for Predestroy and stop() method. > In WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting > @PostConstruct > public void start() { > logger.info(this.hashCode() + "configuration for " + this.getBaseDir() + " " + System.getProperties().getProperty("jboss.server.config.dir")); > } > Output is > (ServerService Thread Pool -- 69) 2034435521 configuration for /opt/wildfly/standalone/configuration /opt/wildfly/standalone/configuration > (ServerService Thread Pool -- 69) 2034435521 configuration for /opt/wildfly/standalone/configuration /opt/wildfly/standalone/configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3169?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3169: ---------------------------------------- Hehe, ok I understand. Neither is a simple change (the underlying grid widget does not support merged cells or different background colour on rows). Since neither fix is minor I defer to [~tirelli] and [~uxdlc] as to which they'd prefer to see implemented. > [DMN Designer] Last Context Entry differentiation > ------------------------------------------------- > > Key: DROOLS-3169 > URL: https://issues.jboss.org/browse/DROOLS-3169 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-22 17-35-07.png > > > The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change. > We should improve this in one of the following ways: > - Keep name *Default*, change font to italics and use grey background color > - Merge the *Default* and *Value* cells of last entry and remove the name *Default* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018