October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11212) Do not register jdbc-driver's datasource-class-info as metric

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11212?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-11212: ------------------------------- Component/s: JCA > Do not register jdbc-driver's datasource-class-info as metric > ------------------------------------------------------------- > > Key: WFLY-11212 > URL: https://issues.jboss.org/browse/WFLY-11212 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 14.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Alpha1 > > > jdbc-driver resource registers 1 attribute as metric: > * datasource-class-info > {code} > /subsystem=datasources/jdbc-driver=h2:read-attribute(name=datasource-class-info) > { > "outcome" => "success", > "result" => [{"org.h2.jdbcx.JdbcDataSource" => { > "URL" => "java.lang.String", > "description" => "java.lang.String", > "loginTimeout" => "int", > "password" => "java.lang.String", > "url" => "java.lang.String", > "user" => "java.lang.String" > }}] > } > {code} > This attribute is not an actual metric (that may change due to server activity). > It should be registered as runtime read-only attributes instead. > This change only impacts metadata and does not require resource transformation. > Additionally, I've checked with HAL team that this change has no impact on HAL UI (that does not distinguish between read-only runtime attribute and metric). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11212) Do not register jdbc-driver's datasource-class-info as metric

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11212: ---------------------------------- Summary: Do not register jdbc-driver's datasource-class-info as metric Key: WFLY-11212 URL: https://issues.jboss.org/browse/WFLY-11212 Project: WildFly Issue Type: Bug Affects Versions: 14.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 15.0.0.Alpha1 jdbc-driver resource registers 1 attribute as metric: * datasource-class-info {code} /subsystem=datasources/jdbc-driver=h2:read-attribute(name=datasource-class-info) { "outcome" => "success", "result" => [{"org.h2.jdbcx.JdbcDataSource" => { "URL" => "java.lang.String", "description" => "java.lang.String", "loginTimeout" => "int", "password" => "java.lang.String", "url" => "java.lang.String", "user" => "java.lang.String" }}] } {code} This attribute is not an actual metric (that may change due to server activity). It should be registered as runtime read-only attributes instead. This change only impacts metadata and does not require resource transformation. Additionally, I've checked with HAL team that this change has no impact on HAL UI (that does not distinguish between read-only runtime attribute and metric). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4173) Do not register socket-binding bound attributes as metrics

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4173: ----------------------------------- Summary: Do not register socket-binding bound attributes as metrics Key: WFCORE-4173 URL: https://issues.jboss.org/browse/WFCORE-4173 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 7.0.0.Alpha2 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Socket-binding resource registers 3 attributes as metric: * bound * bound-port * bound-address None of these attributes are actual metric (that may change due to server activity). They should be registered as runtime read-only attributes instead. This change only impacts metadata and does not require resource transformation. Additionally, I've checked with HAL team that this change has no impact on HAL UI (that does not distinguish between read-only runtime attribute and metric). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11211) inter-app quickstart can not be deployed

by Sultan Zhantemirov (Jira)

Sultan Zhantemirov created WFLY-11211: ----------------------------------------- Summary: inter-app quickstart can not be deployed Key: WFLY-11211 URL: https://issues.jboss.org/browse/WFLY-11211 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Sultan Zhantemirov Assignee: Eduardo Martins When deploying we have un-resolved dependency. I am using jboss EAP quickstarts and wildfly 15.0.0.Alpha1-SNAPSHOT 16:45:57,040 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 3.0.5 (Final) 16:45:57,454 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] } 16:45:57,457 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11210) inter-app can't be deployed

by Sultan Zhantemirov (Jira)

[ https://issues.jboss.org/browse/WFLY-11210?page=com.atlassian.jira.plugin... ] Sultan Zhantemirov moved JBEAP-15683 to WFLY-11210: --------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11210 (was: JBEAP-15683) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) > inter-app can't be deployed > --------------------------- > > Key: WFLY-11210 > URL: https://issues.jboss.org/browse/WFLY-11210 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Jean-Francois Denise > Assignee: Eduardo Martins > Priority: Major > > When deploying we have un-resolved dependency. > I am using jboss EAP quickstarts and wildfly 15.0.0.Alpha1-SNAPSHOT > 16:45:57,040 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 3.0.5 (Final) > 16:45:57,454 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] > } > 16:45:57,457 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] > } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11113?page=com.atlassian.jira.plugin... ] Jan Blizňák edited comment on WFLY-11113 at 10/18/18 6:41 AM: -------------------------------------------------------------- [~asoldano] given that "com.github.relaxng" module is private and new dependency is completly different project, can't we rename the module too? was (Author: jbliznak): [~asoldano] given "com.github.relaxng" module was private and new dependency is completly different project, can't we rename the module too? > Update to JAXB 2.3.1 > -------------------- > > Key: WFLY-11113 > URL: https://issues.jboss.org/browse/WFLY-11113 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Labels: Java11 > Fix For: 15.0.0.Alpha1 > > > The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) > Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 > Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... > Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. > \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 > \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 > \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11113?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11113: ------------------------------------ [~asoldano] given "com.github.relaxng" module was private and new dependency is completly different project, can't we rename the module too? > Update to JAXB 2.3.1 > -------------------- > > Key: WFLY-11113 > URL: https://issues.jboss.org/browse/WFLY-11113 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Labels: Java11 > Fix For: 15.0.0.Alpha1 > > > The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) > Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 > Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... > Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. > \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 > \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 > \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-10997: ----------------------------------------- Assignee: Bartosz Baranowski (was: Tomasz Adamski) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10997 > URL: https://issues.jboss.org/browse/WFLY-10997 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10531: ------------------------------- Fix Version/s: 15.0.0.Alpha1 > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Alpha1 > > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-10531: ------------------------------------ +1, I'll review the PR and make sure it makes it into WildFly 15. [~jondruse] thanks for looking at it. > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Alpha1 > > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 2018