[JBoss JIRA] (SWSQE-1188) Mirroring the Kiali Catalog is not working on disconnected.
by Guilherme Baufaker Rêgo (Jira)
Guilherme Baufaker Rêgo created SWSQE-1188:
----------------------------------------------
Summary: Mirroring the Kiali Catalog is not working on disconnected.
Key: SWSQE-1188
URL: https://issues.redhat.com/browse/SWSQE-1188
Project: Kiali QE
Issue Type: Bug
Reporter: Guilherme Baufaker Rêgo
Attachments: catalog-sources-disconnected.sh
Attached the script that I used for installing catalog sources on Disconnected Clusters.
The following error is occurring
{code:java}
oc image mirror quay.io/maistra/kiali-olm-cs:${KIALI_VERSION} ${BASTION_HOST}:55555/maistra/kiali-olm-cs:${KIALI_VERSION} --registry-config auth.json
bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/
maistra/kiali-olm-cs
blobs:
quay.io/maistra/kiali-olm-cs sha256:2baa60ab307e57d54636480f288f3ee467d83c606334057cbf12da781d4ed10c
quay.io/maistra/kiali-olm-cs sha256:76d97be54a93e3fa5a85e44fcbe8fbb5b5624254f37a871597b9ef3e1c6cec51
quay.io/maistra/kiali-olm-cs sha256:772064a3a17bf5e293309a416f105d05f42a1862e789339c83fe67776a4ffe2a
quay.io/maistra/kiali-olm-cs sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4
manifests:
sha256:924b15f202eb41b6d7933d267f9dd74065cd0ab37ea94582fea1290078186da8 -> 1.12.13
stats: shared=0 unique=4 size=0B
phase 0:
bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555 maistra/kiali-olm-cs blobs=4 mounts=0 manifests=1 shared=0
info: Planning completed in 330ms
error: unable to push manifest to bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/maistra/kiali-olm-cs:1.12.13: received unexpected HTTP status: 500 Internal Server Error
info: Mirroring completed in 10ms (0B/s)
error: one or more errors occurred while uploading images
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13595) MP REST client causes classloader leak on undeploy
by Richard DiCroce (Jira)
Richard DiCroce created WFLY-13595:
--------------------------------------
Summary: MP REST client causes classloader leak on undeploy
Key: WFLY-13595
URL: https://issues.redhat.com/browse/WFLY-13595
Project: WildFly
Issue Type: Bug
Components: MP REST Client
Affects Versions: 20.0.0.Final
Reporter: Richard DiCroce
Assignee: Alessio Soldano
I have an application that uses CDI and JAX-RS but not MP REST. The MP subsystems aren't even part of the WildFly configuration. Nonetheless, the MP REST client is added to the deployment and creates a classloader leak when the application is undeployed.
See below for the paths to GC root, as determined using a heap dump analyzed by Eclipse MAT. In particular, note that org.jboss.resteasy.microprofile.client.RestClientExtension keeps a static reference to the CDI BeanManager.
Workaround: add an exclusion in jboss-deployment-structure.xml to prevent the org.jboss.resteasy.resteasy-client-microprofile module from being added to the deployment.
{noformat}
Class Name | Shallow Heap | Retained Heap
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| |
com.sg.sciq.jpa.entity.QStore @ 0xfc8913f0 | 120 | 10,704
'- store class com.sg.sciq.jpa.entity.QStore @ 0xe53d5af0 | 24 | 10,816
'- [459] java.lang.Object[5120] @ 0xe702af00 | 20,496 | 3,166,624
'- elementData java.util.Vector @ 0xe4677e88 | 32 | 3,166,656
'- classes org.jboss.modules.ModuleClassLoader @ 0xe4677208 | 88 | 3,654,184
'- moduleClassLoader org.jboss.as.weld.discovery.WeldClassFileServices @ 0xe4d09bb8 | 24 | 24
'- value java.util.HashMap$Node @ 0xe507ed10 | 32 | 32
'- [63] java.util.HashMap$Node[128] @ 0xe4df06e8 | 528 | 2,904
'- table java.util.HashMap @ 0xe4df06b8 | 48 | 2,984
'- services org.jboss.weld.bootstrap.api.helpers.SimpleServiceRegistry @ 0xe4df06a8 | 16 | 3,000
'- services org.jboss.weld.manager.BeanManagerImpl @ 0xe4df0610 | 152 | 7,848
'- manager org.jboss.weld.bean.builtin.BeanManagerProxy @ 0xe4df0c90 | 24 | 24
'- manager class org.jboss.resteasy.microprofile.client.RestClientExtension @ 0xe4df0c20 | 8 | 56
'- [0] java.lang.Object[10] @ 0xe46ec028 | 56 | 80
'- elementData java.util.Vector @ 0xe46ec008 | 32 | 112
'- classes org.jboss.modules.ModuleClassLoader @ 0xe46ebea8 | 88 | 3,240
'- moduleClassLoader org.jboss.modules.Module @ 0xe47d1348 | 56 | 30,296
'- module org.jboss.modules.ModuleLoader$FutureModule @ 0xe4a65790 | 24 | 24
'- val java.util.concurrent.ConcurrentHashMap$Node @ 0xe4a65770 | 32 | 56
'- [352] java.util.concurrent.ConcurrentHashMap$Node[512] @ 0xe08491f0 | 2,064 | 19,088
'- table java.util.concurrent.ConcurrentHashMap @ 0xe0487188 | 64 | 19,152
'- moduleMap org.jboss.modules.LocalModuleLoader @ 0xe0487150 | 56 | 22,120
|- moduleLoader org.jboss.modules.Module @ 0xe014b580 | 56 | 9,336
|- moduleLoader org.jboss.modules.Module @ 0xe017c0e0 | 56 | 58,440
|- moduleLoader org.jboss.modules.Module @ 0xe034f7c8 | 56 | 28,576
|- moduleLoader org.jboss.modules.Module @ 0xe05f8e50 | 56 | 41,160
|- moduleLoader org.jboss.modules.Module @ 0xe06db838 | 56 | 72,288
|- moduleLoader org.jboss.modules.Module @ 0xe06f42e0 | 56 | 20,720
|- moduleLoader org.jboss.modules.Module @ 0xe0741d58 | 56 | 56,712
|- moduleLoader org.jboss.modules.Module @ 0xe0979ec8 | 56 | 43,760
|- moduleLoader org.jboss.modules.Module @ 0xe04a9200 | 56 | 14,000
|- moduleLoader org.jboss.modules.Module @ 0xe05c9b30 | 56 | 8,704
|- moduleLoader org.jboss.modules.Module @ 0xe0729200 | 56 | 23,264
|- moduleLoader org.jboss.modules.Module @ 0xe0941378 | 56 | 54,360
|- moduleLoader org.jboss.modules.Module @ 0xe032e128 | 56 | 22,832
|- moduleLoader org.jboss.modules.Module @ 0xe05dbaf0 | 56 | 27,728
|- INSTANCE class org.jboss.modules.DefaultBootModuleLoaderHolder @ 0xe065cbe0| 8 | 8
|- moduleLoader org.jboss.modules.Module @ 0xe068b460 | 56 | 20,008
|- moduleLoader org.jboss.modules.Module @ 0xe0707518 | 56 | 46,848
|- moduleLoader org.jboss.modules.Module @ 0xe073b5e0 | 56 | 44,880
|- moduleLoader org.jboss.modules.Module @ 0xe0213738 | 56 | 12,040
|- moduleLoader org.jboss.modules.Module @ 0xe058c4f0 | 56 | 23,424
|- moduleLoader org.jboss.modules.Module @ 0xe02f41c8 | 56 | 30,144
|- moduleLoader org.jboss.modules.Module @ 0xe034f128 | 56 | 27,088
|- moduleLoader org.jboss.modules.Module @ 0xe0500470 | 56 | 9,912
|- moduleLoader org.jboss.modules.Module @ 0xe12ceea0 | 56 | 24,648
'- Total: 24 entries | |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5439) DMN 1.3 clean up range function
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5439:
--------------------------------------
Summary: DMN 1.3 clean up range function
Key: DROOLS-5439
URL: https://issues.redhat.com/browse/DROOLS-5439
Project: Drools
Issue Type: Task
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
To be checked, but these:
“overlapped by”
“overlapped before by”
“overlapped after by”
are to be removed
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13594) Upgrade Artemis Native to 1.0.2
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-13594:
----------------------------------------
Summary: Upgrade Artemis Native to 1.0.2
Key: WFLY-13594
URL: https://issues.redhat.com/browse/WFLY-13594
Project: WildFly
Issue Type: Component Upgrade
Components: JMS
Affects Versions: 20.0.0.Final
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Because of a fix in the kernel, libaio is now returning duplicate events
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFCORE-5012) Upgrade Jboss Threads to 2.3.5
by Yeray Borges Santana (Jira)
Yeray Borges Santana created WFCORE-5012:
--------------------------------------------
Summary: Upgrade Jboss Threads to 2.3.5
Key: WFCORE-5012
URL: https://issues.redhat.com/browse/WFCORE-5012
Project: WildFly Core
Issue Type: Component Upgrade
Components: Server
Reporter: Yeray Borges Santana
Assignee: Yeray Borges Santana
Upgrade jboss Thread to 2.3.5
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-5147:
--------------------------------------
Sprint: (was: 2020 Week 25-27 (from Jun 15))
> [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
> --------------------------------------------------------------------------
>
> Key: DROOLS-5147
> URL: https://issues.redhat.com/browse/DROOLS-5147
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UXTeam, drools-tools, kogito-tooling
> Attachments: prototype.png
>
>
> Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
> - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
> - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
> The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months