----- Original Message ----- From: "Martin Crawford" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, January 17, 2003 11:55 PM Subject: RE: Parameters for connection-pooling
> Thanks, this is good for the username and password. What about other JDBC > settings such as the URL or Driver? Are there ways to programmatically set > the URL or Driver? yes, no problem with current CVS (next release). JdbcConnectionDescriptor myJdbc = new J....(); myJdbc.setDriver(...); .... MetadataManager.connectionRepository.addDescriptor(myJdbc); regards, Armin > > Martin > > -----Original Message----- > From: Armin Waibel [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 10:38 AM > To: OJB Users List > Subject: Re: Parameters for connection-pooling > > > I checked both pool configurations, all seems > to work as designed (CVS, thus I think 0.98 too). > > regards, > Armin > ----- Original Message ----- > From: "Armin Waibel" <[EMAIL PROTECTED]> > To: "OJB Users List" <[EMAIL PROTECTED]> > Sent: Friday, January 17, 2003 3:47 PM > Subject: Re: Parameters for connection-pooling > > > > Hi Oliver, > > > > there are to different pools in OJB: > > - a PersistenceBroker pool, all properties could > > be set in OJB.properties (version 0.98) > > - a connection pool, max active connection could set in > > OJB.properties or in connection-pool tag in repository > > file > > > > In CVS we made some improvements handling this > > stuff, also we add a test case to check all properties > > in connection-pool. I will check the property setting > > for the PB pool too - add this on my todo list ;-) > > > > HTH, > > Armin > > > > ----- Original Message ----- > > From: "Paulus Oliver" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, January 17, 2003 10:54 AM > > Subject: Parameters for connection-pooling > > > > > > Hi, > > > > I encountered a problem with OJB 0.9.8 during modifying the parameters > > for > > the connection pooling within my application. > > I put the following parameters in the repository.xml file for the > > connection-descriptor: > > <connection-pool > > minEvictableIdleTimeMillis="120000" > > timeBetweenEvictionRunsMillis="120000" > > whenExhaustedAction="0" > > maxIdle="-1" > > maxActive="-1" > > maxWait="5000" > > numTestsPerEvictionRun="20" > > testWhileIdle="false" > > testOnReturn="false" > > testOnBorrow="true" > > /> > > And I also put the same parameters to the ojb.properties file. I got > the > > following output: > > > > ---------------------------------------------------------------------- > -- > > ---- > > ------------- > > > > run: > > [java] SollstellungData: bkz=0 rechBetrag=0 F�lligkeit=Fri Jan 17 > > 10:26:22 > > CET 2003hkz=null hhj=null aostNr=null aostErw=null kapitel=null > > titel=null > > zusat > > z=null budgetNr=null e1=null e2=null e3=null[] > > > > > > [java] OOPs > > [java] [DEFAULT] ERROR: > 0. Value was -1 > > [java] > > [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] > > INFO: > > Create PersistenceBroker instance pool, pool configuration was > > {whenExhaustedAc > > tion=0, maxIdle=-1, maxActive=15, maxWait=5000, > > numTestsPerEvictionRun=10, > > testW > > hileIdle=false, testOnReturn=false, > > timeBetweenEvictionRunsMillis=120000, > > minEvi > > ctableIdleIimeMillis=600000, testOnBorrow=false} > > [java] > [org.apache.ojb.broker.util.sequence.SequenceManagerFactory] > > INFO: U > > se sequence manager class: class > > org.apache.ojb.broker.util.sequence.SequenceMan > > agerHiLoImpl > > [java] > > [org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl] > > INFO > > : Create connection pool for JdbcDescriptorKey -1541372445 > > [java] > > [org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl] > > INFO > > : Create new connection pool for > > org.apache.ojb.broker.metadata.JdbcConnectionDe > > scriptor, > > [java] used descriptor: JdbcConnectionDescriptor > > [java] DBMS:MsSQLServer > > [java] DRIVER: com.microsoft.jdbc.sqlserver.SQLServerDriver > > [java] PROTOCOL: jdbc > > [java] SUBPROTOCOL: microsoft:sqlserver > > [java] DBALIAS: > > file://b3b357n3:1433;DatabaseName=JMBS;SelectMethod=cursor; > > [java] USERNAME: sa > > [java] PASSWORD: sa > > [java] EAGER RELEASE: false > > [java] pool configuration was: {whenExhaustedAction=0, > maxIdle=-1, > > maxActiv > > e=21, maxWait=5000, numTestsPerEvictionRun=20, testWhileIdle=false, > > testOnReturn > > =false, timeBetweenEvictionRunsMillis=120000, > > minEvictableIdleIimeMillis=120000, > > testOnBorrow=true} > > [java] hkz= hhj= aostNr= aostErw= kapitel= titel= zusatz= > budgetNr= > > e1= > > e2= > > e3= > > > > > > ---------------------------------------------------------------------- > -- > > ---- > > --------------------- > > > > The debug outputs for the connection pooling from > > [org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl] are > > different > > from [org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl]. > > The > > parameters from the ojb.properties file are not taken properly. And in > > my > > case the application is only working fine with the parameters from the > > connection-pool element within the repository.xml file. > > Has someone else already encountered the same problem? > > > > > > Regards, > > > > Oliver Paulus > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
