Hi Ron, the SDO code never touches ConfigurationCache directly, and the EMF JavaDoc says it is an internal API [1]. I guess this is one to raise with EMF. A google on ConfigurationCache reveals very little in terms of anyone having hit this issue before. Are you happy to raise this on the EMF newsgroup? I'm happy to support you as best I can, but I think direct communication between you and them is going to be the easiest way to resolve this. Kelvin.
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.emf.doc/references/javadoc/org/eclipse/emf/ecore/xmi/impl/ConfigurationCache.html On 10/01/2008, Ron Gavlin <[EMAIL PROTECTED]> wrote: > > Greetings, > > We are using Tuscany SDO 1.0 in a production server environment. During > application execution, we see the XMLStrings contained in the EMF > org.eclipse.emf.ecore.xmi.impl.ConfigurationCache.printers[] array growing > without bound until eventually we are forced to restart the application. > There exists a ConfigurationCache.release() method which appears designed > to release this cache. However, we never see this method being invoked > during the life-cycle of our application. Any suggestions for resolving this > problem? Your prompt assistance with this matter is appreciated. > > - Ron > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
