Dear Jesper,

Thank you  for your detail explanation.

Best Regards,

Karl Gross

Dear Jesper,

I did the following according to your instructions:

1. download a AS7 nightly build: https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/artifact/build/target/jboss-as-7.x.zip

2. update ironjacamar module to 1.1.0.Beta1, use postgres 9.1-902 JDBC 4

3. add the following elements in xa-datasource defnition:

<recovery>

   <recover-plugin class-name="org.jboss.jca.core.recovery.ValidatingManagedConnectionFactoryRecoveryPlugin"/>

</recovery>

<validation>

   <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"></valid-connection-checker>

   <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"></exception-sorter>

</validation>

* In JBTM-1183 the attribute no-recovery="false" is recommended also. But I could not use it, because JBoss gave an error during booting: Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf.

Unfortunately the class com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule still used 74% of the total heap memory.

Could you please tell me, if I have done correctly? Or do you know any other issues related to this class? Thank you!

Best Regards,

Karl Gross

Dear Jesper,

thank you for your quick response. I will check it again using the nightly build directly.

A report from Eclipse MAT:

------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------

Dear Jesper,

I started my JBoss instance yestoday, simply using a nightly build. Meanwhile the retained heap for XARecoveryModule was already about 50% of the total heap size. I have no ideas how to proceed with this. The configuration of my datasource looks like:

<xa-datasource jndi-name="java:/server.ds.core" pool-name="server.ds.core-pool" enabled="true" use-java-context="true">

    <xa-datasource-property name="DatabaseName">

        server_db

    </xa-datasource-property>

    <xa-datasource-property name="User">

        user

    </xa-datasource-property>

    <xa-datasource-property name="ServerName">

        server

    </xa-datasource-property>

    <xa-datasource-property name="PortNumber">

        5432

    </xa-datasource-property>

    <xa-datasource-property name="Password">

        xxx

    </xa-datasource-property>

    <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>

    <driver>postgresql-jdbc4</driver>

    <transaction-isolation>TRANSACTION_SERIALIZABLE</transaction-isolation>

    <xa-pool>

        <min-pool-size>1</min-pool-size>

        <max-pool-size>75</max-pool-size>

        <use-strict-min>true</use-strict-min>

    </xa-pool>

    <security>

        <user-name>user</user-name>

        <password>xxx</password>

    </security>

    <recovery>

        <recover-plugin class-name="org.jboss.jca.core.recovery.ValidatingManagedConnectionFactoryRecoveryPlugin"/>

    </recovery>

    <validation>

        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"></valid-connection-checker>

        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"></exception-sorter>

        <check-valid-connection-sql>select 1</check-valid-connection-sql>

    </validation>

    <timeout>

        <idle-timeout-minutes>5</idle-timeout-minutes>

    </timeout>

    <statement>

        <track-statements>TRUE</track-statements>

    </statement>

</xa-datasource>

<drivers>

    <driver name="postgresql-jdbc4" module="org.postgresql"/>

</drivers>

The version of ironjacamar in the night build JBoss is 1.0.12. I am using postgresql-9.1-902.jdbc4.jar. Could you please tell me, if I have done something wrong in the configuration? Thank you!

Best Regards,

Karl Gross

Dear Jesper,

thank you for creating the jar file. Unfortunately exchanging the jar file has made no difference. After JBoss was running not more than two days, the heap size for XARecoveryModule reached already 400MB.

Is this problem also related to the not implemented method Connection.isValid in postgresql-9.1-902?

Because I am testing a  migrated project from JBoss 4, the memory dump is at least 600MB. It is difficult for me to provide a small dump file.

Best Regards,

Karl Gross

Dear Jesper,

I have uploaded a compressed heap dump file with the size of 21MB. You can get it from http://www.2shared.com/file/jznfgHor/datasource-memory-leak-idp-dum.html. The dump is from our JBoss instance for single sign on.

Could you please help us to analyze this dump file and find a workaround also applicable for JBoss 7.1.1?

Because even if the workaround works for JBoss nightly build, it is not enough for users who want to migrate to JBoss 7 at the moment. Moreover no timeline for the next release can be found in the JBoss AS roadmap. This uncertainty will also make lot of users hesitate to change to JBoss7.

Thank you for your help!

Best Regards,

Karl Gross

Dear Jonathan,

thank you for your reply! Because we are now almost at the end of migrating our application to JEE6, hopefully we could get a solution as soon as possible.

Best Regards,

Karl Gross