Hi,
Christopher Cheng wrote:
I want to monitor that too! What's the class name and how do we use it?
In OJB 1.0.x we don't have a monitoring service. To add monitoring hooks
you have to extend the existing classes to add your own extensions.
For OJB 1.1 we need some kind of "monitoring-api". I add a feature
request in jira. Any suggestions how to implement monitoring support are
welcome.
http://issues.apache.org/jira/browse/OJB-57
regards,
Armin
-----Original Message-----
From: Martin Kalen [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 3:31 PM
To: OJB Users List
Subject: Re: Broker pool size
Leeuwen, E.W.A. (Ed) van wrote:
We have some problems with the broker pool. We would like to be able
to log the "current number outstanding" for each pool. Is there any
(easy) way to do this?
AFAIK the monitoring hooks are only present in OJB 1.1 in CVS HEAD.
Armin would be the one to have all the details (since he wrote it). ;)
If you don't want your broker pool to ever be exhausted just set
whenExhaustedAction=2 (ie grow) in OJB.properties.
Also note that even if you set an unlimited number of PersistenceBrokers for
the broker pool, your database Connection limit for each jcdAlias can still
limit the number of concurrent DB-operations that OJB can perform.
(This is tuned in your repository_database.xml at the connect-pool level per
jcdAlias.)
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
