Hi, seems not to be solved. During JBoss startup OJB seems not to report the ConnectionFactoryClass I turned debugging on to
# Logger for PersistenceBrokerImpl class org.apache.ojb.broker.singlevm.PersistenceBrokerImpl.LogLevel=DEBUG # Logger for PersistenceBrokerFactory class org.apache.ojb.broker.PersistenceBrokerFactory.LogLevel=DEBUG # Logger for PersistenceBrokerClient org.apache.ojb.broker.server.PersistenceBrokerClient.LogLevel=DEBUG but could not find any usefull information for my connection pooling problem. Where can I look at? cheers, Guido ----- Original Message ----- From: "Armin Waibel" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Monday, February 24, 2003 4:20 PM Subject: Fw: OJB Connection pooling problem inside JBOSS > > ----- Original Message ----- > From: "Armin Waibel" <[EMAIL PROTECTED]> > To: "Guido Beutler" <[EMAIL PROTECTED]> > Sent: Monday, February 24, 2003 4:14 PM > Subject: Re: OJB Connection pooling problem inside JBOSS > > > > Hi again, > > > > ----- Original Message ----- > > From: "Guido Beutler" <[EMAIL PROTECTED]> > > To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" > > <[EMAIL PROTECTED]> > > Sent: Monday, February 24, 2003 3:27 PM > > Subject: Re: OJB Connection pooling problem inside JBOSS > > > > > > > Hi, > > > > > > no I did not set this. I'm testing it with true in a few minutes. > > > Whats the difference? > > If set 'true' OJB try to close the JCA connection handle as > > soon as possible. > > > > > I run into the problem exacty at the number of configured > connections. > > Strange, because looked up Datasources never will be pooled. > > Maybe coincidence? Or configuration problems and OJB don't really > > use the set ConnectionFactory > > --> Check config files and logs when OJB start. > > > > regards, > > Armin > > > > > > > > cheers, > > > > > > Guido > > > > > > ----- Original Message ----- > > > From: "Armin Waibel" <[EMAIL PROTECTED]> > > > To: "OJB Users List" <[EMAIL PROTECTED]> > > > Sent: Monday, February 24, 2003 3:26 PM > > > Subject: Re: OJB Connection pooling problem inside JBOSS > > > > > > > > > > Hi Guido, > > > > > > > > do you set 'eager-release=true' in jdbc-connection-descriptor > > > > when running within jboss? > > > > > > > > regards, > > > > Armin > > > > > > > > ----- Original Message ----- > > > > From: "Guido Beutler" <[EMAIL PROTECTED]> > > > > To: "OJB Users List" <[EMAIL PROTECTED]> > > > > Sent: Monday, February 24, 2003 3:08 PM > > > > Subject: OJB Connection pooling problem inside JBOSS > > > > > > > > > > > > > Hi, > > > > > > > > > > I'm using OJB inside a stateless session bean. After some time > my > > > > > application thows: > > > > > > > > > > 15:01:43,979 ERROR [STDERR] Caused by: > > > > javax.resource.ResourceException: No > > > > > ManagedConnections Available! > > > > > 15:01:43,979 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getCo > > > > nnec > > > > > tion(InternalManagedConnectionPool.java:127) > > > > > 15:01:43,980 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool > > > > .get > > > > > Connection(JBossManagedConnectionPool.java:323) > > > > > 15:01:43,981 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedCo > > > > nnec > > > > > tion(BaseConnectionManager2.java:467) > > > > > 15:01:43,982 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManaged > > > > Conn > > > > > ection(LocalTxConnectionManager.java:221) > > > > > 15:01:43,983 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnect(Ba > > > > seCo > > > > > nnectionManager2.java:588) > > > > > 15:01:43,983 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.CachedConnectionManager.reconnect(C > > > > ache > > > > > dConnectionManager.java:344) > > > > > 15:01:43,984 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.CachedConnectionManager.pushMetaAwa > > > > reOb > > > > > ject(CachedConnectionManager.java:140) > > > > > 15:01:43,985 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke( > > > > Cach > > > > > edConnectionInterceptor.java:183) > > > > > 15:01:43,986 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Statele > > > > ssSe > > > > > ssionInstanceInterceptor.java:77) > > > > > 15:01:43,987 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > > > > ptor > > > > > .java:107) > > > > > 15:01:43,987 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > > > > CMT. > > > > > java:178) > > > > > 15:01:43,988 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > > > > > 15:01:43,989 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > > > > a:13 > > > > > 0) > > > > > 15:01:43,990 ERROR [STDERR] at > > > > > > > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204) > > > > > 15:01:43,990 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer > > > > .jav > > > > > a:313) > > > > > 15:01:43,991 ERROR [STDERR] at > > > > > org.jboss.ejb.Container.invoke(Container.java:712) > > > > > 15:01:43,992 ERROR [STDERR] at > > > > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > > > > 15:01:43,993 ERROR [STDERR] at > > > > > > > org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) > > > > > 15:01:43,994 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1 > > > > 02) > > > > > 15:01:43,994 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav > > > > a:77 > > > > > ) > > > > > 15:01:43,995 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80) > > > > > 15:01:43,996 ERROR [STDERR] at > > > > > > > > > > > > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionI > > > > nter > > > > > ceptor.java:111) > > > > > 15:01:43,997 ERROR [STDERR] at > > > > > org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) > > > > > > > > > > I set : > > > > > > > > > > > > > > > > > > > > > > ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFacto > > > > ryMa > > > > > nagedImpl > > > > > maxConnectionsInPool=21 > > > > > > > > > > The 21 is identical with my setting at the jboss data source. > I'm > > > > running a > > > > > test application in a single user mode so it should be easy > > > > > to stay within 21 connections. I'm calling remove on the session > > bean > > > > every > > > > > time. > > > > > I think I got a missconfiguration somewhere at the OJB/JBoss > > > > enviroment. > > > > > Currently I'm checking if I run into my problem exact after 21 > > calls. > > > > > Could somebody help? > > > > > > > > > > Thanks, cheers, > > > > > > > > > > Guido > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
