Slower JDBC after migrating from JBoss 4.2.3 to Wildfly 9

[anhh]

Hello all

My team and myself have been struggling with Wildfly for a few days now, after having (properly I think) done the migration of my application from Jboss 4.2.3 to Wildfly 9, and I'm running out on ideas as of what to adjust.

It is a J2EE application, connection to the Postgresql 9.3 is done directly through JDBC. We have added logs around the execution of the statements, and observe that pure statement executions are at least twice as slow as on Jboss 4.2.3. This is a no go for production mode !

Environment is as follows :

• Ubuntu12 32 bits (also tested on Windows8 64bits)
• Sun JDK 8u65 (also tested with Sun JDK7)
• Postgresql 9.3 with driver postgresql-9.4-1202.jdbc42.jar (also tested with jdbc41)

We also tried tuning database connection pool with these parameters with no visible effect:

<datasource jta="true" jndi-name="java:jboss/datasources/MDataSource" pool-name="MDataSource" enabled="true" spy="false" use-ccm="false" statistics-enabled="true">

    <connection-url>jdbc:postgresql://localhost:5432/DATABASE</connection-url>

    <driver-class>org.postgresql.Driver</driver-class>

    <driver>postgres</driver>

    <pool>

        <min-pool-size>2</min-pool-size>

        <max-pool-size>20</max-pool-size>

        <prefill>true</prefill>

    </pool>

    <security>

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

        <password>password</password>

    </security>

</datasource>

Did we miss something ? Is there anything else we should monitor ?

Any help would be greatly appreciated !

Thanks !

[jim_b_o]

You might benefit from:

                    <statement>

                        <prepared-statement-cache-size>32</prepared-statement-cache-size>

                        <share-prepared-statements>true</share-prepared-statements>

                    </statement>

And possibly enlistment-trace="false" although I'm not sure if that exists before WildFly 10.  But if it does, I think it's good with use-ccm="false" for those good developers who clean up their own connections.

[jim_b_o]

Maybe also test using one of the Postgres DataSources rather than the Driver.  Like you, I used to use the Driver (MS and JTDS) with JBoss 4.2.3 (don't remember why) but have switched to the Connection Pool DataSources with WildFly 10.

[anhh]

Thanks James, I'll take a look into your suggestions and let you know.