[ https://issues.jboss.org/browse/TEIID-4815?page=com.atlassian.jira.plugin... ] Rafael Coutinho edited comment on TEIID-4815 at 3/21/17 6:13 PM: ----------------------------------------------------------------- We got a heap dump and found out that this class was consuming 87% of the server memory: SemaphoreArrayListManagedConnectionPool That was managing an Oracle Datasource connection. And searching the web I found this report: https://access.redhat.com/solutions/742913 So we added that flag (maxCachedBufferSize) and have tested. It looks like the memory can get released. Here is how our datasource is configured: {{ <datasource jndi-name="java:/ORACLE_DS" pool-name="ORACLE_DS" enabled="true"> <connection-url>jdbc:oracle:thin:@oracleserver:1010:dev</connection-url> <driver>ojdbc6-11g.jar</driver> <pool> <max-pool-size>30</max-pool-size> </pool> <security> <user-name>**</user-name> <password>***</password> </security> <validation> <check-valid-connection-sql>select 1 from dual</check-valid-connection-sql> <validate-on-match>true</validate-on-match> <background-validation>true</background-validation> <background-validation-millis>10000</background-validation-millis> </validation> </datasource> }} Any other suggestions on configuring oracle datasources? was (Author: rafael.coutinho): We got a heap dump and found out that this class was consuming 87% of the server memory: SemaphoreArrayListManagedConnectionPool That was managing an Oracle Datasource connection. And searching the web I found this report: https://access.redhat.com/solutions/742913 So we added that flag (maxCachedBufferSize) and have tested. It looks like the memory can get released. Here is how our datasource is configured: {{<datasource jndi-name="java:/ORACLE_DS" pool-name="ORACLE_DS" enabled="true"> <connection-url>jdbc:oracle:thin:@oracleserver:1010:dev</connection-url> <driver>ojdbc6-11g.jar</driver> <pool> <max-pool-size>30</max-pool-size> </pool> <security> <user-name>**</user-name> <password>***</password> </security> <validation> <check-valid-connection-sql>select 1 from dual</check-valid-connection-sql> <validate-on-match>true</validate-on-match> <background-validation>true</background-validation> <background-validation-millis>10000</background-validation-millis> </validation> </datasource>}} Any other suggestions on configuring oracle datasources? -- This message was sent by Atlassian JIRA (v7.2.3#72005)