[DERBY-5412] MemoryLeakFixesTest.testRepeatedDatabaseCreationWithAutoStats() fails on phoneME: java.lang.InternalError: Number of class names exceeds vm limit.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.2.2, 10.9.1.0
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: Test
• Bug behavior facts: Regression Test Failure
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 15/Sep/11 10:00
• Updated: 24/Jul/12 17:26
• Resolved: 16/Sep/11 17:08

Description

Seen when running MemoryLeakFixesTest, both with trunk and with the 10.8.2.1 release candidate:

1) testRepeatedDatabaseCreationWithAutoStats(org.apache.derbyTesting.functionTests.tests.memory.MemoryLeakFixesTest)java.lang.InternalError: Number of class names
exceeds vm limit.
at java.lang.ClassLoader.findLoadedClass0(Native Method)
at java.lang.ClassLoader.findLoadedClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.util.ResourceBundle.loadBundle(Unknown Source)
at java.util.ResourceBundle.findBundle(Unknown Source)
at java.util.ResourceBundle.getBundleImpl(Unknown Source)
at java.util.ResourceBundle.getBundle(Unknown Source)
at org.apache.derby.iapi.services.i18n.MessageService.getBundleWithEnDefault(Unknown Source)
at org.apache.derby.iapi.services.i18n.MessageService.getBundleForLocale(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.getBundle(Unknown Source)
at org.apache.derby.iapi.services.i18n.MessageService.getBundle(Unknown Source)
at org.apache.derby.iapi.services.i18n.MessageService.getCompleteMessage(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver169.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.EmbeddedSimpleDataSource.getConnection(Unknown Source)
at org.apache.derby.jdbc.EmbeddedSimpleDataSource.getConnection(Unknown Source)
at org.apache.derbyTesting.functionTests.tests.memory.MemoryLeakFixesTest.testRepeatedDatabaseCreationWithAutoStats(Unknown Source)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(Unknown Source)
at junit.extensions.TestDecorator.basicRun(Unknown Source)
at junit.extensions.TestSetup$1.protect(Unknown Source)
at junit.extensions.TestSetup.run(Unknown Source)
at org.apache.derbyTesting.junit.BaseTestSetup.run(Unknown Source)
at sun.misc.CVM.runMain(Unknown Source)

Issue Links

• relates to: DERBY-5336 Repeated database creation causes OutOfMemoryError