Borrow broker from pool failed

I have been getting this error message intermittently. Would this message result from running out of connections, like I failed to close the broker in some function? Servlet.service() for servlet action threw exception org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed,

Re: Tomcat 5, JNDI, Perm Gen Memory leak

Rick Roman wrote: I am only using the PB API too. Danilo Tommasina wrote: hi again, this is quite an old version of tomcat, we were not having trouble for sure since tomcat 5.5.9, no idea how it was with earlier versions. anyways, if this is not the problem, it could be still OJB that causes

Re: OJB Startup

I use a servlet to load some global values. This accesses a couple of tables and has the effect of initializing OJB, although that was not the intention. The servlet is invoked when Tomcat starts up using load-on-startup servlet attribute in web.xml servlet

Re: Tomcat 5, JNDI, Perm Gen Memory leak

by the quartz scheduler for example. As soon as I can, I'll try to update to 1.0.4 and test out the memory leak problem. cheers Danilo Rick Roman wrote: OK I'm really on version 1.0.4 now and all of these methods run without error. Unfortunately, none of them have any effect on the memory leak

Re: Tomcat 5, JNDI, Perm Gen Memory leak

I am only using the PB API too. Danilo Tommasina wrote: hi again, this is quite an old version of tomcat, we were not having trouble for sure since tomcat 5.5.9, no idea how it was with earlier versions. anyways, if this is not the problem, it could be still OJB that causes the leak. My

Re: Tomcat 5, JNDI, Perm Gen Memory leak

more accurtately, failure to clean up resources). Anyone have any ideas or has anyone ever actually been able to avoid this problem or am I just stuck with it? Armin Waibel wrote: Hi Rick, Rick Roman wrote: Sorry to be dense but can you send me the link to cvs for revision 1.4.2.2

Re: Tomcat 5, JNDI, Perm Gen Memory leak

, Rick Roman wrote: I upgraded to the new db-ojb-1.0.4 which has the method PersistenceBrokerFactoryFactory.instance().shutdown(); This results in exception: [ERROR] mffweb] - Exception sending context destroyed event to listener instance of class org.mff.web.listener.CleanupListener

Error creating PersistentField v1.0.4

In switching to 1.0.4 an error parsing repository.xml has popped up. At first I thought this was a problem with repository_internal but it turns out that I get this error on the first class-descriptor encountered, no matter what it is. If I switch back to 1.0.3, I don't see this problem. Any

Re: Error creating PersistentField v1.0.4

Thanks, that did the trick. I didn't read anything about updating the repository.dtd or OJB.properties in the release announcement. Is there some other place I should be looking for upgrade guidance? Carlos Chávez wrote: Rick Roman wrote: In switching to 1.0.4 an error parsing

Re: Tomcat 5, JNDI, Perm Gen Memory leak

(); PersistenceBrokerFactory.releaseAllInstances(); ConnectionFactoryFactory.getInstance().createConnectionFactory().releaseAllResources(); PersistenceBrokerThreadMapping.shutdown(); PersistenceBrokerFactoryFactory.instance().shutdown(); PersistenceBrokerFactory.shutdown(); Rick Roman wrote: You were correct. I had a ghost

OJB_HL_SEQ

After upgrading to ojb-1.0.4 I am getting an error: [org.apache.ojb.broker.metadata.RepositoryXmlHandler] ERROR: Exception while read metadata Error creating PersistentField: org.apache.ojb.broker.util.sequence.HighLowSequence, name org.apache.ojb.broker.metadata.MetadataException: Error

Re: Tomcat 5, JNDI, Perm Gen Memory leak

(); PersistenceBrokerThreadMapping.shutdown(); MetadataManager.getInstance().removeAllProfiles(); although I am confused about which of these is called for. Can you tell me the appropriate cleanup calls for this version? Armin Waibel wrote: Hi Rick, Rick Roman wrote: Sorry to be dense but can you send me

Re: Tomcat 5, JNDI, Perm Gen Memory leak

Rick Roman wrote: Update: From other threads, I have tried using a contextDestroy listener to run: PersistenceBroker broker = PersistenceBrokerFactory.defaultPersistenceBroker(); broker.clearCache(); broker.close(); PersistenceBrokerFactory.releaseAllInstances

Re: Tomcat 5, JNDI, Perm Gen Memory leak

PROTECTED] ThreadLocal} instances in OJB source and the reuse of threads * by the container (e.g. servlet- or ejb-container). */ public void shutdown(); Rick Roman wrote: Hi Ilkka, shutdown() does not appear to be a method of PersistenceBrokerFactoryFactory.instance(). Is there a patch

Tomcat 5, JNDI, Perm Gen Memory leak

I am using OBJ to access PostgreSQL via a JNDI datasource. My problem is that every time I reload my application context, I get a big jump in Tomcat Perm Gen memory. After a several reloads, tomcat eventually crashes with an out of memory error. I believe this has to do with my OBJ

Re: Tomcat 5, JNDI, Perm Gen Memory leak

().createConnectionFactory().releaseAllResources(); PersistenceBrokerThreadMapping.shutdown(); MetadataManager.getInstance().removeAllProfiles(); and the leak still persists. Rick Roman wrote: I am using OBJ to access PostgreSQL via a JNDI datasource. My problem is that every time I reload my

how do i get currval('my_sequence') ?

I am trying to retrieve the current value of a sequence. I tried setting the sequence up as a table with currval('my_sequence') as a column class-descriptor class=org.mff.web.db.MySeqDb table=my_seq field-descriptor name=currval column=currval('my_seq')

Re: how do i get currval('my_sequence') ?

/faq.html#traceProfileSQL regards, Armin Rick Roman wrote: I am trying to retrieve the current value of a sequence. I tried setting the sequence up as a table with currval('my_sequence') as a column class-descriptor class=org.mff.web.db.MySeqDb table=my_seq field-descriptor