Jboss 3.2.2 memory leak with jetty/mysql

[jesper6tv]

I migrated from JBoss 3.2.1(jetty) to JBoss 3.2.2(jetty) on IBMJava2SDK-1.4.1-0.0 on RedHat 7.3 with MySQL 3.28.58 and connector: mysql-connector-java-3.0.9-stable.

mysql-ds.xml:

<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/mydb</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name></user-name>

<connection-property name="autoReconnect">true</connection-property>
<min-pool-size>50</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>10000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
</local-tx-datasource>


With light load on web application the memory climbs steadily to ~600MB within 24 hours and crashes shortly after. I have no idea what is causing this. There was no memory leak on JBoss 3.2.1 with same configuration.

Any reports on memory leak?
Is it the jbdc-connector, jetty...?
Any hints on how can I find out whats the problem?

Thanks
Jesper

[jesper6tv]

I will try to se if JBoss 3.2.3RC1 has same problem

Jesper

[bjornbak]

We have experienced the problems with JBoss 3.2.2_Jetty.

We use the all configuration, which do you use?

We use an oracle database.

I've tried to shift to JBoss_Tomcat but it hangs on every request = insane long response times..

/Christian

[jesper6tv]

I use the default configuration.

Which oracle-driver do you use. I saw else where that OCI-driver has problems, and it is better to use thin driver.

Any way, I am going to try with 3.2.3RC1 today, which has a newer jetty inside, and let you know how it went.

Jesper

[jesper6tv]

With some tests on JBoss 3.2.3RC1 it seems the memory usage does not increase in same pace.

I still don't know what was the problem in 3.2.2.

I'll return after some more tests.

Jesper

[jesper6tv]

Back again after som tests.

It seems that the leak is caused by a combination of jboss 3.2.2 >, on IBM 1.4.1 SR2 on a virtual(!) linux server Redhat 7.1.
The problem may exists outside JBoss in JVM/OS integration.

It could be in the CMP engine, which leaks under heavy load. JBoss CMP also seems to have been altered a lot from 3.2.1 -> 3.2.2.

I will test BEA JRockit 1.4.1 to see if it integrates better with the OS.

-Jesper