GC overhead limit exceeded at startup after "Installing DBCP monitoring instruments"

Yohann DULONG December 3, 2013

Hi,

We migrate jira 6.x 32 bits (test 6.0.8 and 6.1.4 - Xmx1200m) from jira 4.3.3 and we have a problem "GC overhead limit exceeded" when we start, every time at the same moment :

2013-12-04 09:24:52,984 localhost-startStop-1 INFO [jira.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2013-12-04 09:28:32,207 localhost-startStop-1 ERROR [atlassian.jira.startup.LauncherContextListener] Unable to start JIRA due to Java Error.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.HashMap.createEntry(HashMap.java:869)
at java.util.HashMap.addEntry(HashMap.java:856)
at java.util.HashMap.put(HashMap.java:484)
at org.ofbiz.core.entity.GenericEntity.dangerousSetNoCheckButFast(GenericEntity.java:283)
at org.ofbiz.core.entity.jdbc.SqlJdbcUtil.getValue(SqlJdbcUtil.java:529)
at org.ofbiz.core.entity.EntityListIterator.currentGenericValue(EntityListIterator.java:169)
at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:246)
at org.ofbiz.core.entity.EntityListIterator.getCompleteList(EntityListIterator.java:308)
at org.ofbiz.core.entity.GenericDAO.selectByAnd(GenericDAO.java:631)
at org.ofbiz.core.entity.GenericHelperDAO.findByAnd(GenericHelperDAO.java:131)
at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:804)
at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:789)
at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:766)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:91)
at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.findByAnd(WrappingOfBizDelegator.java:63)
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizInternalMembershipDao.findMemberships(OfBizInternalMembershipDao.java:313)
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizInternalMembershipDao.buildCache(OfBizInternalMembershipDao.java:332)
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizInternalMembershipDao.<init>(OfBizInternalMembershipDao.java:52) <+3> (NativeConstructorAccessorImpl.java:57) (DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:100)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:200)
at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:45)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getConstructorArguments(ConstructorInjectionComponentAdapter.java:222)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:198)
at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)

How can we resolved this ?

Thank you for your help

2 answers

0 votes
Yohann DULONG December 10, 2013

The problem comes from the LDAP synchronisation. It's takes 50 mins and shedule every 60 mins.

The CPU and Memory goes up. So synchronisation is every 24h now.

Thw for help

0 votes
Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 3, 2013

You would require to include certain parameters in order to fix the issue, please see https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+Due+to+OutOfMemoryError+GC+Overhead+Limit+Exceeded for more information.

Suggest an answer

Log in or Sign up to answer