[Red Hat JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api
by Moulali Shikalwadi (Jira)
[ https://issues.redhat.com/browse/WFLY-11963?page=com.atlassian.jira.plugi... ]
Moulali Shikalwadi reassigned WFLY-11963:
-----------------------------------------
Assignee: Cheng Fang (was: Moulali Shikalwadi)
> ejb3 thread-pool thread-factory should be shown deprecated in management api
> ----------------------------------------------------------------------------
>
> Key: WFLY-11963
> URL: https://issues.redhat.com/browse/WFLY-11963
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 16.0.0.Final
> Reporter: Chao Wang
> Assignee: Cheng Fang
> Priority: Major
>
> ejb3 thread-pool thread-factory should be shown deprecated in management api
> The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used.
> {code}
> /subsystem=ejb3/thread-pool=default:read-resource-description(
> "thread-factory" => {
> "type" => STRING,
> "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback
by Luis Barreiro (Jira)
[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ]
Luis Barreiro commented on AG-154:
----------------------------------
[~wojciechkopciewicz] To be clear, if I'm understanding correctly, this is about invalid connections that are *in a transaction* ??
I believe background validation should work even in the case of a failure in rollback.
Do you set background validation (or, in alternative, max-lifetime) ??
> Connection leak when DB connection closed during transaction rollback
> ---------------------------------------------------------------------
>
> Key: AG-154
> URL: https://issues.redhat.com/browse/AG-154
> Project: Agroal
> Issue Type: Bug
> Components: narayana, pool
> Affects Versions: 1.9
> Reporter: Wojciech Kopciewicz
> Assignee: Luis Barreiro
> Priority: Critical
>
> We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB.
> It looks like Agroal is leaking connections when connection is closed (somewhere) on the server side during transaction rollback.
> The following log was observed:
> Error trying to transactionRollback local transaction: This connection has been closed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5818) executable-model test failure in test-compiler-integration VarargsTest
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5818?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5818:
--------------------------------------
Sprint: 2021 Week 04-06 (from Jan 25)
Story Points: 3
> executable-model test failure in test-compiler-integration VarargsTest
> ----------------------------------------------------------------------
>
> Key: DROOLS-5818
> URL: https://issues.redhat.com/browse/DROOLS-5818
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.46.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> org.drools.mvel.integrationtests.VarargsTest in test-compiler-integration fails with some tests when executable-model is enabled. See TODO comment in the test class. Once fixed (or the test failure is justified), we can remove the TODO comment and let the test run with executable-model.
> Currently, executable-model is disabled:
> {code:java}
> // TODO: ....
> return TestParametersUtil.getKieBaseCloudConfigurations(false);
> {code}
> If the test failure contains multiple bugs, we may split this JIRA into multiple JIRAs.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14414) Add a test for resolving expression in wsdl-uri-scheme attribute
by Jim Ma (Jira)
[ https://issues.redhat.com/browse/WFLY-14414?page=com.atlassian.jira.plugi... ]
Jim Ma updated WFLY-14414:
--------------------------
Description:
Add a test for resolving the expression in wsdl-uri-scheme :
{code:java}
<subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">
<modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
<wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
<wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
<wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
<wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
<wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>{code}
was:
Add a test for resolving the expression in wsdl-uri-scheme :
{code:java}
<subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">
<modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
<wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
<wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
<wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
<wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
<wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>{code}
> Add a test for resolving expression in wsdl-uri-scheme attribute
> ----------------------------------------------------------------
>
> Key: WFLY-14414
> URL: https://issues.redhat.com/browse/WFLY-14414
> Project: WildFly
> Issue Type: Task
> Components: Web Services
> Affects Versions: 22.0.0.Final
> Reporter: Jim Ma
> Assignee: Jim Ma
> Priority: Major
> Fix For: 23.0.0.Beta1
>
>
> Add a test for resolving the expression in wsdl-uri-scheme :
> {code:java}
> <subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">
> <modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
> <wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
> <wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
> <wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
> <wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
> <wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>{code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14414) Add a test for resolving expression in wsdl-uri-scheme attribute
by Jim Ma (Jira)
[ https://issues.redhat.com/browse/WFLY-14414?page=com.atlassian.jira.plugi... ]
Jim Ma updated WFLY-14414:
--------------------------
Description:
Add a test for resolving the expression in wsdl-uri-scheme :
{code:java}
<subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">
<modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
<wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
<wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
<wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
<wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
<wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>{code}
was:
Add a test for resolving the expression in wsdl-uri-scheme :
{{<subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">}}
{{ <modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
{{ <wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
{{ <wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
{{ <wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
{{ <wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
{{ <wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>}}
> Add a test for resolving expression in wsdl-uri-scheme attribute
> ----------------------------------------------------------------
>
> Key: WFLY-14414
> URL: https://issues.redhat.com/browse/WFLY-14414
> Project: WildFly
> Issue Type: Task
> Components: Web Services
> Affects Versions: 22.0.0.Final
> Reporter: Jim Ma
> Assignee: Jim Ma
> Priority: Major
> Fix For: 23.0.0.Beta1
>
>
> Add a test for resolving the expression in wsdl-uri-scheme :
> {code:java}
> <subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">
> <modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
> <wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
> <wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
> <wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
> <wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
> <wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>{code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14414) Add a test for resolving expression in wsdl-uri-scheme attribute
by Jim Ma (Jira)
Jim Ma created WFLY-14414:
-----------------------------
Summary: Add a test for resolving expression in wsdl-uri-scheme attribute
Key: WFLY-14414
URL: https://issues.redhat.com/browse/WFLY-14414
Project: WildFly
Issue Type: Task
Components: Web Services
Affects Versions: 22.0.0.Final
Reporter: Jim Ma
Assignee: Jim Ma
Fix For: 23.0.0.Beta1
Add a test for resolving the expression in wsdl-uri-scheme :
{{<subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${ws.statistics-enabled:false}">}}
{{ <modify-wsdl-address>${ws.modify-wsdl-address:true}</modify-wsdl-address>}}
{{ <wsdl-host>${jboss.bind.address:localhost}</wsdl-host>}}
{{ <wsdl-port>${ws.wsdl-port:9090}</wsdl-port>}}
{{ <wsdl-secure-port>${ws.wsdl-secure-port:9443}</wsdl-secure-port>}}
{{ <wsdl-uri-scheme>${ws.wsdl-uri-scheme:https}</wsdl-uri-scheme>}}
{{ <wsdl-path-rewrite-rule>s/jaxws-jbws2150-codefirst/xx\/jaxws-jbws2150-codefirst/g</wsdl-path-rewrite-rule>}}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFCORE-4970) Changing the JVM settings at host level does not put the servers in restart-required
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug... ]
Parul Sharma commented on WFCORE-4970:
--------------------------------------
Hello, [~yersan] as per code analysis jvmAttributes is not flagged as RESTART_JVM neither the CI test is failing. If we want to fix this then we need to introduce RESTART_JVM into jvmAttributes.
> Changing the JVM settings at host level does not put the servers in restart-required
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4970
> URL: https://issues.redhat.com/browse/WFCORE-4970
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 12.0.0.Beta2
> Reporter: Yeray Borges Santana
> Assignee: Parul Sharma
> Priority: Major
>
> Operations like the following one should put the servers in restart required to indicate the user changes will be applied after restarting the servers:
> {noformat}
> [domain@localhost:9990 /] /host=master/jvm=default:write-attribute(name=heap-size, value=256m)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months