[Red Hat JIRA] (WFLY-14137) Typo in JWT_CAPABILITY_NAME
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-14137:
---------------------------------------
Summary: Typo in JWT_CAPABILITY_NAME
Key: WFLY-14137
URL: https://issues.redhat.com/browse/WFLY-14137
Project: WildFly
Issue Type: Bug
Components: MP JWT
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
static final String JWT_CAPABILITY_NAME = "org.wildlfly.microprofile.jwt";
The 'wildfly' has an extra 'l'.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing
by Roland Spindelbalker-Davila (Jira)
[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ]
Roland Spindelbalker-Davila commented on WFLY-14094:
----------------------------------------------------
Are you planning to create bugfix releases for the other affected versions of WildFly as well?
Or will this bug only be fixed in WildFly 22?
> Potential memory leak when using opentracing
> --------------------------------------------
>
> Key: WFLY-14094
> URL: https://issues.redhat.com/browse/WFLY-14094
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, MP OpenTracing
> Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final
> Reporter: Michel Erard
> Assignee: Matěj Novotný
> Priority: Major
> Labels: downstream_dependency
> Fix For: 22.0.0.Beta1
>
> Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png
>
>
> Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak.
> Here I did a little sample project to simulate the issue:
> [https://github.com/erard22/wildfly-memory-leak]
> Requests handeled by this class
> {code:java}
> @ApplicationScoped
> @Traced
> public class HelloWorldService {
> public String sayHello() {
> return "Hello World!";
> }
> } {code}
> leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap.
> !bad_heapdump.png!
> Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing
by Roland Spindelbalker-Davila (Jira)
[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ]
Roland Spindelbalker-Davila edited comment on WFLY-14094 at 12/1/20 5:47 AM:
-----------------------------------------------------------------------------
Are you planning to create bugfix releases for the other affected versions of WildFly as well, or will this bug only be fixed in WildFly 22?
was (Author: roland.spindelbalker-davila):
Are you planning to create bugfix releases for the other affected versions of WildFly as well?
Or will this bug only be fixed in WildFly 22?
> Potential memory leak when using opentracing
> --------------------------------------------
>
> Key: WFLY-14094
> URL: https://issues.redhat.com/browse/WFLY-14094
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, MP OpenTracing
> Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final
> Reporter: Michel Erard
> Assignee: Matěj Novotný
> Priority: Major
> Labels: downstream_dependency
> Fix For: 22.0.0.Beta1
>
> Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png
>
>
> Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak.
> Here I did a little sample project to simulate the issue:
> [https://github.com/erard22/wildfly-memory-leak]
> Requests handeled by this class
> {code:java}
> @ApplicationScoped
> @Traced
> public class HelloWorldService {
> public String sayHello() {
> return "Hello World!";
> }
> } {code}
> leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap.
> !bad_heapdump.png!
> Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (SWSQE-1253) Remove 'bookinfo' namespace from SMMR when cleaning
by Hayk Hovsepyan (Jira)
Hayk Hovsepyan created SWSQE-1253:
-------------------------------------
Summary: Remove 'bookinfo' namespace from SMMR when cleaning
Key: SWSQE-1253
URL: https://issues.redhat.com/browse/SWSQE-1253
Project: Kiali QE
Issue Type: Task
Reporter: Hayk Hovsepyan
When running install-bookinfo job and selecting IS_MAISTRA and CLEAN_ENVIRONMENT flags, it should remove the bookinfo namespace from ServiceMeshMemberRole.
Otherwise it throws error when adding duplicate namespace in SMMR.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14093) Deprecate XTS subsystem
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-14093?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka updated WFLY-14093:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/13758
> Deprecate XTS subsystem
> -----------------------
>
> Key: WFLY-14093
> URL: https://issues.redhat.com/browse/WFLY-14093
> Project: WildFly
> Issue Type: Task
> Components: XTS
> Affects Versions: 22.0.0.Alpha1
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Major
>
> XTS spec does not develop for a long time and other technologies are better of use nowadays.
> The deprecation does not mean removing or changing the functionality, but rather a step to gather information how users utilize this functionality and of course as an announcement that this move is planned from our side.
> We should deprecate WS-AT, WS-BA and xtsbridge and finally compensations as it depends on the XTS code and JAX-WS abilities.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months