[JBoss JIRA] (WFCORE-1343) [1.x] Memory leak in host controller
by Aparna Chaudhary (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1343?page=com.atlassian.jira.plugi... ]
Aparna Chaudhary commented on WFCORE-1343:
------------------------------------------
Thank you [~brian.stansberry] for your quick response.
> [1.x] Memory leak in host controller
> ------------------------------------
>
> Key: WFCORE-1343
> URL: https://issues.jboss.org/browse/WFCORE-1343
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Final
> Reporter: Aparna Chaudhary
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 1.0.2.Final
>
> Attachments: WFCORE-992-HC-Leak.PNG
>
>
> The ManagedServerProxy class in host-controller contains a memory leak. The leak can be reproduced by performing multiple requests to HTTP management API.
> {noformat}
> http://<host>:9990/management/host/host0/server/server0/core-service/platform-mbean/type/memory?include-runtime=true
> {noformat}
> Applying the fix proposed in WFCORE-992 solves the leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml
by Renann Prado (JIRA)
[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ]
Renann Prado edited comment on WFLY-6099 at 2/1/16 1:00 PM:
------------------------------------------------------------
I'll try soon and let you know. Thanks!
However I still find strange how this is working:
In *standalone.xml*:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/TestDS" pool-name="TestDS" enabled="true" use-ccm="true">
<connection-url>jdbc:mariadb://mariadbvm:3306/test_db</connection-url>
<driver-class>org.mariadb.jdbc.Driver</driver-class>
<driver>mariadb-java-client-1.3.4.jar</driver>
<security>
<user-name>root</user-name>
<password>123</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
{code}
As you can see the driver class is "wrong".
was (Author: renannp):
I'll try soon and let you know. Thanks!
However I still find strange how this is working:
In *standalone.xml*:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/TestDS" pool-name="TestDS" enabled="true" use-ccm="true">
<connection-url>jdbc:mariadb://107.155.108.92:3306/test_db</connection-url>
<driver-class>org.mariadb.jdbc.Driver</driver-class>
<driver>mariadb-java-client-1.3.4.jar</driver>
<security>
<user-name>root</user-name>
<password>123</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
{code}
As you can see the driver class is "wrong".
> JPA's persistence.xml is deployed before datasources are created through application.xml
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6099
> URL: https://issues.jboss.org/browse/WFLY-6099
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Renann Prado
> Assignee: Scott Marlow
> Attachments: server_with_mysql_driver.log
>
>
> Please refer to discussion
> https://developer.jboss.org/thread/267371
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml
by Renann Prado (JIRA)
[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ]
Renann Prado edited comment on WFLY-6099 at 2/1/16 12:55 PM:
-------------------------------------------------------------
I'll try soon and let you know. Thanks!
However I still find strange how this is working:
In *standalone.xml*:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/TestDS" pool-name="TestDS" enabled="true" use-ccm="true">
<connection-url>jdbc:mariadb://107.155.108.92:3306/test_db</connection-url>
<driver-class>org.mariadb.jdbc.Driver</driver-class>
<driver>mariadb-java-client-1.3.4.jar</driver>
<security>
<user-name>root</user-name>
<password>123</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
{code}
As you can see the driver class is "wrong".
was (Author: renannp):
I'll try soon and let you know. Thanks!
However I still find strange how this is working:
In *standalone.xml*:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/TestDS" pool-name="TestDS" enabled="true" use-ccm="true">
<connection-url>jdbc:mariadb://107.155.108.92:3306/test_db</connection-url>
<driver-class>org.mariadb.jdbc.Driver</driver-class>
<driver>mariadb-java-client-1.3.4.jar</driver>
<security>
<user-name>root</user-name>
<password>123</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
{code}
> JPA's persistence.xml is deployed before datasources are created through application.xml
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6099
> URL: https://issues.jboss.org/browse/WFLY-6099
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Renann Prado
> Assignee: Scott Marlow
> Attachments: server_with_mysql_driver.log
>
>
> Please refer to discussion
> https://developer.jboss.org/thread/267371
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml
by Renann Prado (JIRA)
[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ]
Renann Prado commented on WFLY-6099:
------------------------------------
I'll try soon and let you know. Thanks!
However I still find strange how this is working:
In *standalone.xml*:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/TestDS" pool-name="TestDS" enabled="true" use-ccm="true">
<connection-url>jdbc:mariadb://107.155.108.92:3306/test_db</connection-url>
<driver-class>org.mariadb.jdbc.Driver</driver-class>
<driver>mariadb-java-client-1.3.4.jar</driver>
<security>
<user-name>root</user-name>
<password>123</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
{code}
> JPA's persistence.xml is deployed before datasources are created through application.xml
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6099
> URL: https://issues.jboss.org/browse/WFLY-6099
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Renann Prado
> Assignee: Scott Marlow
> Attachments: server_with_mysql_driver.log
>
>
> Please refer to discussion
> https://developer.jboss.org/thread/267371
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFCORE-1343) [1.x] Memory leak in host controller
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1343?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1343:
------------------------------------------
Thank you. Currently we don't have any specific plans to do another release from the 1.x branch, unless we learn of a critical CVE problem. (This is why there is no release date associated with the 1.0.2.Final version in JIRA.) But, assuming your pull request passes CI testing, if we do a release I'll include that change.
> [1.x] Memory leak in host controller
> ------------------------------------
>
> Key: WFCORE-1343
> URL: https://issues.jboss.org/browse/WFCORE-1343
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Final
> Reporter: Aparna Chaudhary
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 1.0.2.Final
>
> Attachments: WFCORE-992-HC-Leak.PNG
>
>
> The ManagedServerProxy class in host-controller contains a memory leak. The leak can be reproduced by performing multiple requests to HTTP management API.
> {noformat}
> http://<host>:9990/management/host/host0/server/server0/core-service/platform-mbean/type/memory?include-runtime=true
> {noformat}
> Applying the fix proposed in WFCORE-992 solves the leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months