Hi,
I am developing an application, wherein I have configured derby 10.8.2.2 database as my datasource in JBOSS 6. I used
<min-pool-size>20</min-pool-size> <max-pool-size>300</max-pool-size> in my <xa-datasource> and used 400 drda threads in derby.properties file. But after some time i found that active connection count goes beyond 300 and and applicatiojn throws"Unable to get managed connection" exception
Please find below my configuration details -
<min-pool-size>20</min-pool-size>
<max-pool-size>300</max-pool-size>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>2</idle-timeout-minutes>
<check-valid-connection-sql>select 1 from SYSIBM.SYSDUMMY1</check-valid-connection-sql>
<background-validation-millis>5000</background-validation-millis>
<allocation-retry>3</allocation-retry>
<allocation-retry-wait-millis>1000</allocation-retry-wait-millis>
<no-tx-separate-pools />
<xa-resource-timeout>0</xa-resource-timeout>
Below are my derby.properties contents
derby.storage.pageCacheSize=4000
derby.storage.pageSize=4096
derby.locks.escalationThreshold=100
derby.drda.portNumber=57747
derby.drda.logConnections=true
derby.drda.maxThreads=650
derby.drda.timeSlice=2000
derby.stream.error.logSeverityLevel=0
Can anyone let me know why JBOSS failed to release steal connection? I closed my connection whever I have opend.
I am using EJB-QL.
One more quation - does EJB-QL releases connection after usage?
Please help me...I am in deep sea.
Any idea about my above queation....