[JBoss JIRA] (WFCORE-4850) Updating mockserver. Exclusion of dependency from xom.io7m
by Panagiotis Sotiropoulos (Jira)
Panagiotis Sotiropoulos created WFCORE-4850:
-----------------------------------------------
Summary: Updating mockserver. Exclusion of dependency from xom.io7m
Key: WFCORE-4850
URL: https://issues.redhat.com/browse/WFCORE-4850
Project: WildFly Core
Issue Type: Task
Reporter: Panagiotis Sotiropoulos
Assignee: Panagiotis Sotiropoulos
Updating mockserver in order to update netty-codec-http version used. Exclusion of dependency from xom.io7m (in order to exclude netty-codec-http version used)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBJCA-1402) Failure to set query timeout for validation may result in long blocks of the pool
by Flavia Rainone (Jira)
[ https://issues.redhat.com/browse/JBJCA-1402?page=com.atlassian.jira.plugi... ]
Flavia Rainone reassigned JBJCA-1402:
-------------------------------------
Assignee: Flavia Rainone
> Failure to set query timeout for validation may result in long blocks of the pool
> ---------------------------------------------------------------------------------
>
> Key: JBJCA-1402
> URL: https://issues.redhat.com/browse/JBJCA-1402
> Project: IronJacamar
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 1.4.10
> Reporter: Stephen Fikes
> Assignee: Flavia Rainone
> Priority: Major
>
> Validation queries run [without any explicit query timeout|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.1...]. If the validation query blocks (as it will with most drivers when a connection is invalid/stale), this can block the entire pool in certain cases (e.g. {{background-validation}} locks the pool during validation). Even with {{validate-on-match}}, the failure to enforce a short timeout can significantly impact time to get a connection if one or more failed connections are found in the pool.
> Setting a driver level query timeout is not a suitable workaround because this impacts normal queries that may be expected to run for significant periods. The timeout for normal queries needs to be different from what is tolerated for validation queries (which should respond nearly instantaneously or else the connection is likely broken).
> Minimally, an explicit query timeout should be supplied.
> It might also be useful if a pool property or perhaps a system property could support a configurable timeout period (e.g. to account for potential latency in some systems). The Apache Tomcat pool supports something of this nature with the [validationQueryTimeout|https://tomcat.apache.org/tomcat-9.0-doc/jdbc-pool...] property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13095) Create 'microprofile' integration test module
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13095:
---------------------------------
Summary: Create 'microprofile' integration test module
Key: WFLY-13095
URL: https://issues.redhat.com/browse/WFLY-13095
Project: WildFly
Issue Type: Task
Components: MP Config, MP Fault Tolerance, MP Health, MP Metrics, MP OpenAPI, MP OpenTracing
Reporter: Ingo Weiss
Assignee: Radoslav Husar
Fix For: 19.0.0.Beta1
We need a place where to stick microprofile integration tests which run against a server provisioned with all microprofile integration modules. Moreover, since these modules are not in the default server configuration, we will use galleon to provision the server with fault-tolerance, jwt, openapi, etc galleon layers.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13094) MicroProfile capability names are mangled "org.wildlfy..."
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13094:
---------------------------------
Summary: MicroProfile capability names are mangled "org.wildlfy..."
Key: WFLY-13094
URL: https://issues.redhat.com/browse/WFLY-13094
Project: WildFly
Issue Type: Bug
Components: MP Config, MP Health, MP Metrics
Reporter: Ingo Weiss
Assignee: Radoslav Husar
Fix For: 19.0.0.Beta1
Namely:
{code}
org.wildlfy.microprofile.config
org.wildlfy.microprofile.health.reporter
org.wildlfy.extension.microprofile.metrics.wildfly-collector
{code}
Lets fix these up before we properly support this since WF 19.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months