October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4611) It is impossible to use infinity values

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4611: ------------------------------------ Summary: It is impossible to use infinity values Key: DROOLS-4611 URL: https://issues.jboss.org/browse/DROOLS-4611 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Anna Dupliak Assignee: Daniele Zonca It is impossible to use infinity values. *workaround If one expect some infinity value as a result -> they could compare it with the "1/0" expression -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4610) Update HACEP docs for openshift 4.x

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4610: ------------------------------------------ Summary: Update HACEP docs for openshift 4.x Key: DROOLS-4610 URL: https://issues.jboss.org/browse/DROOLS-4610 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-963) OCP 4.2 provisioning fails with Error creating OpenStack container object

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-963?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-963. --------------------------------- Resolution: Done Cleaned containers and created new tasks to prevent this issue from happening again. > OCP 4.2 provisioning fails with Error creating OpenStack container object > ------------------------------------------------------------------------- > > Key: SWSQE-963 > URL: https://issues.jboss.org/browse/SWSQE-963 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Blocker > Labels: infrastructure > > Full exception: > level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Still creating... [1m0s elapsed]" > level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Creation complete after 1m7s [id=440a6c32-ef73-4bbf-9ea9-1cdade8314d0]" > level=error > level=error msg="Error: Error creating OpenStack container object: Expected HTTP response code [] when accessing [PUT https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13808/v1/AUTH_0d9514d7d...], but got 413 instead" > level=error msg="Upload exceeds quota." > level=error > level=error msg=" on ../../../../../../../tmp/openshift-install-535787086/bootstrap/main.tf line 49, in resource \"openstack_objectstorage_object_v1\" \"ignition\":" > level=error msg=" 49: resource \"openstack_objectstorage_object_v1\" \"ignition\" {" > level=error > level=error > level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-965) OCP 4.2 image registry is consuming space in Swift which is causing provisioning problems

by Filip Brychta (Jira)

Filip Brychta created SWSQE-965: ----------------------------------- Summary: OCP 4.2 image registry is consuming space in Swift which is causing provisioning problems Key: SWSQE-965 URL: https://issues.jboss.org/browse/SWSQE-965 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Image registry created on OCP 4.2 cluster is consuming space in Swift which is needed for new cluster installations. We need to find some other option. It caused https://issues.jboss.org/browse/SWSQE-963 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12643) Memory leak in FlashScope - expired elements are not cleared

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12643?page=com.atlassian.jira.plugin... ] Bartosz Spyrko updated WFLY-12643: ---------------------------------- Git Pull Request: https://github.com/jboss/mojarra/pull/45, https://github.com/eclipse-ee4j/mojarra/pull/4633/commits (was: https://github.com/jboss/mojarra/pull/42, https://github.com/eclipse-ee4j/mojarra/pull/4633/commits) > Memory leak in FlashScope - expired elements are not cleared > ------------------------------------------------------------ > > Key: WFLY-12643 > URL: https://issues.jboss.org/browse/WFLY-12643 > Project: WildFly > Issue Type: Bug > Components: JSF > Environment: * JBoss EAP 7.2.3 (also JBoss EAP 7.1.6 that is the latest version in 7.1.x is affected by this issue) > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Critical > > Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed. > If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon. > {code:java} > @Model > public class Action { > private static final int oneHundredMB = 1024 * 1024 * 100; > public String next() { > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.putNow("huge", new byte[oneHundredMB]); > return "index.xhtml?faces-redirect=true"; > } > } > {code} > When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated. > {noformat} > Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap > ----------------------------------------------------------------------------------------------------------------------------------------- > java.lang.Thread @ 0xeea24380 default task-1 Thread | 1 | 120 | 64 | 20,800 > '- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608 | 1 | 40 | 64 | 64 > '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630| 1 | 64 | 64 | 314,574,048 > ----------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1886) Switch to the JBoss / Jakarta Fork for JACC

by Martin Mazanek (Jira)

[ https://issues.jboss.org/browse/ELY-1886?page=com.atlassian.jira.plugin.s... ] Martin Mazanek reassigned ELY-1886: ----------------------------------- Assignee: Martin Mazanek > Switch to the JBoss / Jakarta Fork for JACC > ------------------------------------------- > > Key: ELY-1886 > URL: https://issues.jboss.org/browse/ELY-1886 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: EE > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Priority: Blocker > Fix For: 1.11.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1887) Switch to the JBoss / Jakarta fork for JASPI

by Martin Mazanek (Jira)

[ https://issues.jboss.org/browse/ELY-1887?page=com.atlassian.jira.plugin.s... ] Martin Mazanek reassigned ELY-1887: ----------------------------------- Assignee: Martin Mazanek > Switch to the JBoss / Jakarta fork for JASPI > -------------------------------------------- > > Key: ELY-1887 > URL: https://issues.jboss.org/browse/ELY-1887 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: EE > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Priority: Blocker > Fix For: 1.11.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-964) Check why the OCP 4.2 installation does not remove created Containers

by Filip Brychta (Jira)

Filip Brychta created SWSQE-964: ----------------------------------- Summary: Check why the OCP 4.2 installation does not remove created Containers Key: SWSQE-964 URL: https://issues.jboss.org/browse/SWSQE-964 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta The problem caused https://issues.jboss.org/browse/SWSQE-963 We need to find out why those object are not cleaned automatically and clean them manually regularly as a tmp workaroun. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2390) New NO-based transports

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/JGRP-2390?page=com.atlassian.jira.plugin.... ] Diego Lovison commented on JGRP-2390: ------------------------------------- [~belaban] If you would like to run a benchmark in our PerfLab using RadarGun, please let us know. Also, It will be nice if you could create a wrapper that allows us to change the implementation later because of [Project Loom|https://github.com/openjdk/loom]. Reference: https://static.rainfocus.com/oracle/oow19/sess/1562603002511001K7yM/PF/DE... > New NO-based transports > ----------------------- > > Key: JGRP-2390 > URL: https://issues.jboss.org/browse/JGRP-2390 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Based on one-nio (https://github.com/odnoklassniki/one-nio) or Netty (https://github.com/netty/netty/pull/9509) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12643) Memory leak in FlashScope - expired elements are not cleared

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12643?page=com.atlassian.jira.plugin... ] Bartosz Spyrko moved JBEAP-17741 to WFLY-12643: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12643 (was: JBEAP-17741) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Affects Version/s: (was: 7.2.3.GA) QE Test Coverage: (was: +) Fix Version/s: (was: 7.2.5.GA) > Memory leak in FlashScope - expired elements are not cleared > ------------------------------------------------------------ > > Key: WFLY-12643 > URL: https://issues.jboss.org/browse/WFLY-12643 > Project: WildFly > Issue Type: Bug > Components: JSF > Environment: * JBoss EAP 7.2.3 (also JBoss EAP 7.1.6 that is the latest version in 7.1.x is affected by this issue) > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Critical > > Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed. > If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon. > {code:java} > @Model > public class Action { > private static final int oneHundredMB = 1024 * 1024 * 100; > public String next() { > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.putNow("huge", new byte[oneHundredMB]); > return "index.xhtml?faces-redirect=true"; > } > } > {code} > When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated. > {noformat} > Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap > ----------------------------------------------------------------------------------------------------------------------------------------- > java.lang.Thread @ 0xeea24380 default task-1 Thread | 1 | 120 | 64 | 20,800 > '- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608 | 1 | 40 | 64 | 64 > '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630| 1 | 64 | 64 | 314,574,048 > ----------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 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 2019