While I'm not that familiar with the specifics of the pool, settings in OJB.properties are usually system-wide, settings in the repository.xml (jdbc-connection-descriptor or sub-element to be precise) only for the database described by this connection descriptor, and in some cases there are even settings specific fo class-descriptors. Of these the class-descriptor settings are used when present, or if not, then the jdbc-connection-descriptor settings if present, and if these aren't there either, then the settings from OJB.properties.
Tom On 7/6/05, OJB Dev <[EMAIL PROTECTED]> wrote: > Hello, > I am using OJB 1.0.3 and was wondering why it seems that the pool settings > have two different places to set the same settings. Would like to know which > one takes precedence, if any, and what is the proper/preferred method to > use. > > -- ojb.properties -- > #--------------------------------------------------------------------------- > ------------- > # PersistenceBroker pool > #--------------------------------------------------------------------------- > ------------- > # PersistenceBroker pool configuration > # This pool uses the jakarta-commons-pool api. > # There you can find things described in detail. > # > # maximum number of brokers that can be borrowed from the > # pool at one time. When non-positive, there is no limit. > maxActive=21 > > > -- repository.xml -- > <connection-pool > maxActive="21" > /> > -------------------- > > As well as the other properties such as > "whenExhaustedAction","maxIdle","maxWait", etc. > > Thanks for any information, > > Rick Gavin > Senior Systems Architect / Software Engineer > VIDYAH Inc. > > > > > --------------------------------------------------------------------- > 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]
