[CONTROLLER-1431] "java.lang.OutOfMemoryError: GC overhead limit exceeded" when re-installing DIDM Created: 22/Oct/15 Updated: 19/Oct/17 Resolved: 05/Jul/17 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | config |
| Affects Version/s: | Beryllium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Linh Pham | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4516 |
| Priority: | Normal |
| Description |
|
Installing DIDM and Openflowplugin seems to work well the first time after the first fresh start of Karaf. After the initial installation, different exceptions occur on uninstall and reinstall of the same set of Karaf features for DIDM and Openflowplugin causing Karaf to hang. Steps to reproduce: 1. Download and install Karaf integration distribution (link to download: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.4.0-SNAPSHOT/distribution-karaf-0.4.0-20151022.192517-1764.zip) 2. Install DIDM and openflowplugin: 3. Uninstall DIDM and openflowplugin: 4. Reinstall DIDM and openflowplugin (repeat step 2) Different exceptions occur during step 3 and 4 (not seen on the the first fresh installation of Karaf). Example 1: Karaf terminal capture opendaylight-user@root>feature:install odl-openflowplugin-all-li Example 2: Exceptions found in karaf.log 2015-10-22 13:31:59,431 | ERROR | l for user karaf | ExtensibleBundleTracker | 114 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to remove bundle org.opendaylight.didm.hp3800.hp-3800-impl_0.2.0.SNAPSHOT [273] ] to org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.didm.identification.impl.rev150202.DeviceIdentificationManagerModuleFactory@22b7a92f |
| Comments |
| Comment by Vratko Polak [ 23/Oct/15 ] |
|
Feature uninstallation is not supported in Beryllium, specifically Config Subsystem does not know to unload configuration upon uninstall. That may explain the IllegalStateException. On the other hand, OutOfMemoryError should not happen just because of feature uninstall. That is severe enough to be considered a Beryllium config subsystem Bug. |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
A memory dump is required to debug OOM errors. |
| Comment by Tom Pantelis [ 05/Jul/17 ] |
|
This bug is old and I assume it's no longer an issue. |