We had this problem
Using the ConnectionPoolDataSource improved it
Just note that the data source remains DataSource in the code
P please consider the environment - do you really need to print this
email?
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Friday, October 09, 2009 8:17 PM
To: users_at_glassfish.dev.java.net
Subject: Getting java.sql.SQLException: Error in allocating a
connection.
Dear All,
I have an application(EAR) which was deployed in SunOne 8.1_02 app
server. after 30 to 40 concurrent users logged into the application I am
getting the below error.
[#|2009-10-09T14:2758.933+0530|WARNING|sun-appserver-ee8.1_02|javax.ente
rprise.system.stream.err|_ThreadID=49;|
java.sql.SQLException: Error in allocating a connection. Cause: In-use
connections equal max-pool-size and expired max-wait-time. can not
allocate more connections.
at com.sun.gjc.spi.DataSource.getnConnection(DataSource.java:93)
App Server : SunOne8,1_02 /
OS : Sun Solaris
database: Oracle 9i/10g
If anyone have idea on this, kindly reply with your valuable inputs.
Thanks in Advance.
Regards,
Suresh Kumar
[Message sent by forum member 'dv320002205' (sureshkumardv_at_gmail.com)]
http://forums.java.net/jive/thread.jspa?messageID=367448
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net