July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster

by Richard Achmatowicz (Jira)

[ https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin... ] Richard Achmatowicz updated WFLY-11833: --------------------------------------- Attachment: test-debug-log.txt > Stateful Session Bean affinity URI instead of cluster > ----------------------------------------------------- > > Key: WFLY-11833 > URL: https://issues.jboss.org/browse/WFLY-11833 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 16.0.0.Final > Environment: WildFly cluster having SFSB deployed. > Reporter: Joerg Baesner > Assignee: Richard Achmatowicz > Priority: Major > Labels: downstream_dependency > Attachments: stateful-timeout.zip, test-debug-log.txt > > > Deployed is an application with the following setup: > * Containing a SFSB (_with passivationCapable="true"_) > * A SLSB exposing a _remote_ method to a standalone client returning an instance of the SFSB > Scenario: > A standalone client is invoking the _remote_ method on the Stateless Session Bean and a new instance of the Stateful Session Bean is returned. > The issue is that the affinity of the returned Stateful Session Bean is URI instead of Cluster. > See the attached Gradle reproducer application -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4341) Text Annotation SVG and glyph needs revision

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4341: ----------------------------------------- Summary: Text Annotation SVG and glyph needs revision Key: DROOLS-4341 URL: https://issues.jboss.org/browse/DROOLS-4341 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.24.0.Final Reporter: Elizabeth Clayton Assignee: Michael Anstis Attachments: DMN-text-annotation.png, DMN12-Specification.png The SVG and glyph used for {{TextAnnotations}} needs revision. The horizontal lines are too long. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-829) Prepare for Middleware Infra Upgrade

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-829?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-829. --------------------------------- Resolution: Done Plan is ready in attached document > Prepare for Middleware Infra Upgrade > ------------------------------------ > > Key: SWSQE-829 > URL: https://issues.jboss.org/browse/SWSQE-829 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > There is outage scheduled for MW Lab. We need to prepare plan for that. > More info: > Hi, > You are receiving this email as a stakeholder of the Middleware lab environment which will be impacted by the following lab work. > We are working on a project to upgrade the old Cisco networking infrastructure in the labs to new Juniper hardware. > This work will impact all Middleware systems which are in Westford Lab 3. That is, anything with an IP address starting with 10.16.x.x, things with 10.19.x.x addresses will not be impacted. > A spreadsheet listing the systems including all hardware can be found here: https://docs.google.com/spreadsheets/d/1lSB0cAfX2Jvp0iCJn4gsuArw8mlyqZnG4... > Note that this may not show all virtual systems. > The main work will be done in two parts: > First, we will swap out switches for all the system listed on the "Row E" tab of the spreadsheet. This is scheduled to be done on Monday, August 12th and Tuesday the 13th. > After that we will swap out switches for everything else listed on "Row D" and "Row C". This is scheduled to be done on Tuesday, August 20th and Wednesday the 21st. > Please expect the noted systems to be unavailable during these days. > These dates were scheduled to try to accommodate product releases, though it looks like a couple things were pushed back so it shouldn't be a problem. > In preparation for this we will also need to migrate the routing instance for all the affected networks. This will be a much shorter maintenance, no more than an hour should be needed. > I was advised that this should just be done outside of BRQ working hours, so will probably be done on a Friday evening or over the weekend. I will update when we have a solid timeframe for that. > Additionally, there are a few systems that will need to get moved to the middleware network, and some things which should be physically moved. I will send a separate email to people regarding those. > Most things, however, will not be getting new addresses and will simply be inaccessible for the duration of the work. > Following each maintenance window the systems should be back online and otherwise unaffected. However, if you do encounter any problems please feel free to respond directly to this email. > If you experience issues outside of business hours please refer to the escalation procedures found here: https://mojo.redhat.com/docs/DOC-1049381 > Let me know if you have any questions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-833) Make code coverage working with new pipeline

by Filip Brychta (Jira)

Filip Brychta created SWSQE-833: ----------------------------------- Summary: Make code coverage working with new pipeline Key: SWSQE-833 URL: https://issues.jboss.org/browse/SWSQE-833 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Code coverage requires different approach with new pipeline, we need to update it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-833) Make code coverage working with new pipeline

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-833?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-833: -------------------------------- Labels: infrastructure (was: ) > Make code coverage working with new pipeline > -------------------------------------------- > > Key: SWSQE-833 > URL: https://issues.jboss.org/browse/SWSQE-833 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Code coverage requires different approach with new pipeline, we need to update it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-11121) CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed

by Alessio Giovanni Baroni (Jira)

[ https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin... ] Alessio Giovanni Baroni commented on WFLY-11121: ------------------------------------------------ The commit 5beb3281351d4640eff4d5979f65c21612c0f26d (actual master HEAD) with Oracle Java 1.8 212 and OpenJDK 11.0.3 presente this defect. > CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed > -------------------------------------------------------------------------------------- > > Key: WFLY-11121 > URL: https://issues.jboss.org/browse/WFLY-11121 > Project: WildFly > Issue Type: Bug > Reporter: Rostislav Svoboda > Assignee: Oleksiy Lubyanskyy > Priority: Blocker > Labels: Java11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Compilation of Master linux JDK 11 job fails - forked embedded process has failed. > https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11 > {code} > [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin: > 2.0.0.Final:generate-feature-specs (feature-spec-build) on project wildfly-servlet-galleon-pack: > Feature spec generator failed: Forked embedded process has failed -> [Help 1] > {code} > My local machine runs are passing for me, using {{java version "11" 2018-09-25 (build 11+28)}} > This fail can be related to VMs setup on TeamCity, another option can be galleon related issue. > CCing also [~aloubyansky] > We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4340) Contains can not be used for String with the Expression editor

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4340?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHDM-1024 to DROOLS-4340: -------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4340 (was: RHDM-1024) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW QE Status: NEW > Contains can not be used for String with the Expression editor > -------------------------------------------------------------- > > Key: DROOLS-4340 > URL: https://issues.jboss.org/browse/DROOLS-4340 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools > > Use the expression editor and check for example person.name.contains("ABC"). > Save, close the editor and reopen. "contains("ABC")" does not show up in the editor. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4339) Avoid implicit conversion while accumulating, type is always one returned from the function

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4339?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4339: --------------------------------- Sprint: 2019 Week 29-31 > Avoid implicit conversion while accumulating, type is always one returned from the function > ------------------------------------------------------------------------------------------- > > Key: DROOLS-4339 > URL: https://issues.jboss.org/browse/DROOLS-4339 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4339) Avoid implicit conversion while accumulating, type is always one returned from the function

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4339: ------------------------------------ Summary: Avoid implicit conversion while accumulating, type is always one returned from the function Key: DROOLS-4339 URL: https://issues.jboss.org/browse/DROOLS-4339 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4338) DMN DT Analysis normalize redundant overlaps skip no-interval

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4338: -------------------------------------- Summary: DMN DT Analysis normalize redundant overlaps skip no-interval Key: DROOLS-4338 URL: https://issues.jboss.org/browse/DROOLS-4338 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: image-2019-07-18-10-45-22-044.png, image-2019-07-18-10-45-52-165.png In a case such as !image-2019-07-18-10-45-22-044.png|thumbnail! BEFORE: !image-2019-07-18-10-45-52-165.png|thumbnail! EXPECTED {code:java} Message [id=0, level=WARNING, path=null, line=17, column=-1 text=DMN: Overlap detected: Overlap values: [ <60, >=30 ] for rules: [3, 1] (DMN id: _eb02106a-cee1-47f5-a9d9-3160c5ac868b, DMN Validation, Decision Table Analysis, Overlap Analysis) ] Message [id=0, level=WARNING, path=null, line=17, column=-1 text=DMN: Overlap detected: Overlap values: [ >=60, <30 ] for rules: [2, 3] (DMN id: _eb02106a-cee1-47f5-a9d9-3160c5ac868b, DMN Validation, Decision Table Analysis, Overlap Analysis) ] Message [id=0, level=WARNING, path=null, line=17, column=-1 text=DMN: Overlap detected: Overlap values: [ >=60, >=30 ] for rules: [2, 3, 1] (DMN id: _eb02106a-cee1-47f5-a9d9-3160c5ac868b, DMN Validation, Decision Table Analysis, Overlap Analysis) ] Message [id=0, level=WARNING, path=null, line=17, column=-1 text=DMN: First Normal Form Violation: hit policy Rule Order is a violation of First Normal Form; consider changing for example to Output Order or Collect (DMN id: _eb02106a-cee1-47f5-a9d9-3160c5ac868b, DMN Validation, Decision Table Analysis, First Normal Form Violation) ] ... 10:42:35.190 [main] DEBUG o.k.d.v.d.AbstractDTAnalysisTest.debugAnalysis:95 - Overlaps: Overlap values [ -Inf .. 60 ) [ 30 .. +Inf ] for rules: [3, 1] Overlap values [ 60 .. +Inf ] [ -Inf .. 30 ) for rules: [2, 3] Overlap values [ 60 .. +Inf ] [ 30 .. +Inf ] for rules: [2, 3, 1] {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 2019