Within the connection-pool element you set the size of the
connection-pool, in the OJB.properties file you set the size of the
PB-pool (this is not the same). Thus you need both settings. It's
obvious that the PB-pool size should always greater or equals to the
connection-pool size.
regards,
Armi
Dennis Bekkering wrote:
Armin,
You are right. I run a test with latest from SVN (OJB_1_0_RELEASE
branch) with whenExhaustedAction=2 and it works as expected.
Wrong OJB.properties file in your classpath?
regards,
Armin
I actually dont use OJB.properties but repository-database.xml for pool
Armin,
You are right. I run a test with latest from SVN (OJB_1_0_RELEASE
branch) with whenExhaustedAction=2 and it works as expected.
Wrong OJB.properties file in your classpath?
regards,
Armin
I actually dont use OJB.properties but repository-database.xml for pool
settings. The OJB.poperti
Dennis Bekkering wrote:
Hello Armin,
If you run stress tests on OJB please make sure that the maximal active
PB instances setting and the maximal active connections setting in
ConnectionFactory (see repository file connection-pool
http://db.apache.org/ojb/docu/guides/repository.html#connectio
Hello Armin,
If you run stress tests on OJB please make sure that the maximal active
PB instances setting and the maximal active connections setting in
ConnectionFactory (see repository file connection-pool
http://db.apache.org/ojb/docu/guides/repository.html#connection-pool-N10251
) is higher
277)
at com.myvision.business.GenericDelegate.getSingleTon(
GenericDelegate.java:284)
at com.myvision.business.MyVisionSettingsDelegate.getMyVisionSettings(
MyVisionSettingsDelegate.java:35)
at com.myvision.util.ExceptionUTILS$1.run(ExceptionUTILS.java:30)
Caused by: java.util.NoSuchElementExcep
com.myvision.business.GenericDelegate.getSingleTon(
GenericDelegate.java:284)
at com.myvision.business.MyVisionSettingsDelegate.getMyVisionSettings(
MyVisionSettingsDelegate.java:35)
at com.myvision.util.ExceptionUTILS$1.run(ExceptionUTILS.java:30)
Caused by: java.util.NoSuchElementException
at
Hi,
Thanks OJB, it is a great tool. We are using OJB version .99 connecting
to MS SQL Server in a web based project.
From time to time We recieve the following exception:
java.util.NoSuchElementException
at org.apache.ojb.broker.accesslayer.RsIterator.next(Unknown Source)
at
