• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: New Tomcat 6 Deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New Tomcat 6 Deployment


  • Subject: Re: New Tomcat 6 Deployment
  • From: Ramsey Gurley <email@hidden>
  • Date: Wed, 30 May 2012 08:43:27 -0700

Given the way the pool is implemented, it is not fixable AFAICT.  The EC is only connected to one OSC to run cleanup.  So snapshots get inserted into all OSCs, but only get removed from one. The bigger the pool, the bigger the leak.

Persistent session storage with multiple stateless instances should give the same effect without the leak though :-)

On May 30, 2012, at 8:31 AM, John Huss wrote:

Does that mean you have a fix coming?   :-)

On Wed, May 30, 2012 at 10:16 AM, Ramsey Gurley <email@hidden> wrote:

On May 30, 2012, at 7:13 AM, John Huss wrote:

I would go with wotaskd/monitor.  You can more easily run multiple instances; each instance gives you another database connection.

Alternatively, you can set the property:

     er.extensions.ERXObjectStoreCoordinatorPool.maxCoordinators=3

And this will give you a pool of database connections (and EOF stacks).  It will use more memory though.  Also, I have a suspicion that this can cause deadlocks occasionally, but nothing confirmed.

John


I can confirm that the ERXObjectStoreCoordinatorPool will leak snapshots until the app falls over :-)


On Wed, May 30, 2012 at 9:04 AM, Ron Lift <email@hidden> wrote:

I have been doing some more research and I am beginning to think this post describes the cause of the issue

 

http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-jdbc-driver-has-been-forcibly-unregistered

 

Has anyone deployed and application to production with either Tomcat 6 or 7 with these messages? If so, did they have any issues?

 

We are using out of the box EOF, the article talks about the need for connection pooling. I have read the Cayenne supports connection pooling.  Does EOF?

 

Or maybe we switch to monitor for deployment on RHEL6.  I read the articles and considering it. Anyone done this?



On Tue, May 29, 2012 at 3:30 PM, D Tim Cummings <email@hidden> wrote:
I have noticed these messages too and would like to know if there is anything that can be done about them

Tim



On 29/05/2012, at 23:31, Ron Lift <email@hidden> wrote:

At work we are migrating from RHEL 5 to RHEL 6 and also upgrading to Tomcat 6. When I deploy the current application that is running on Tomcat 5.5 to tomcat 6, I see the following messages in the catalina.out when I either deploy the app, start/ stop the app or the tomcat instance.  I do not have these messages in my tomcat 5.5 log files. Is there some setting that I am missing?  Any help will be greatly appreciated

Eclipse 3.6.1 , WOLips 3.6. MSSQL 2008R2 Database.

 

The last 2 messages repeat multiple times

 
 

May 29, 2012 8:59:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/CoopApp] registered the JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

 

May 29, 2012 8:59:00 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [/CoopApp] created a ThreadLocal with key of type [er.extensions.eof.ERXEC$1] (value [er.extensions.eof.ERXEC$1@1083964f]) and a value of type [java.util.Vector] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

 

May 29, 2012 8:59:00 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [/CoopApp] created a ThreadLocal with key of type [er.extensions.foundation.ERXThreadStorage.ERXThreadStorageCloneableThreadLocal] (value [er.extensions.foundation.ERXThreadStorage$ERXThreadStorageCloneableThreadLocal@2f012501]) and a value of type [java.util.HashMap] (value [{}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

 

Ron Lift

C-E

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)

This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)

This email sent to email@hidden



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: New Tomcat 6 Deployment
      • From: John Huss <email@hidden>
References: 
 >New Tomcat 6 Deployment (From: Ron Lift <email@hidden>)
 >Re: New Tomcat 6 Deployment (From: D Tim Cummings <email@hidden>)
 >Re: New Tomcat 6 Deployment (From: Ron Lift <email@hidden>)
 >Re: New Tomcat 6 Deployment (From: John Huss <email@hidden>)
 >Re: New Tomcat 6 Deployment (From: Ramsey Gurley <email@hidden>)
 >Re: New Tomcat 6 Deployment (From: John Huss <email@hidden>)

  • Prev by Date: Re: New Tomcat 6 Deployment
  • Next by Date: Re: New Tomcat 6 Deployment
  • Previous by thread: Re: New Tomcat 6 Deployment
  • Next by thread: Re: New Tomcat 6 Deployment
  • Index(es):
    • Date
    • Thread