cancel
Showing results for 
Search instead for 
Did you mean: 

Out of memory

jatz
Champ in-the-making
Champ in-the-making
HI,

We see the below error when running Activiti with Spring on a tomcat box.

The app came down after about half a day of running. The parameters set are quite low - could this be the issue?

-Xmx256m

Are there any other suggestions for this?

java.lang.OutOfMemoryError: Java heap space

at java.io.ByteArrayOutputStream.<init>(ByteArrayOutputStream.java:77)

at sun.security.ssl.OutputRecord.<init>(OutputRecord.java:76)

at sun.security.ssl.OutputRecord.<init>(OutputRecord.java:86)

at sun.security.ssl.AppOutputStream.<init>(AppOutputStream.java:52)

at sun.security.ssl.SSLSocketImpl.init(SSLSocketImpl.java:587)

at sun.security.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:494)

at sun.security.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:313)

at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket(JSSESocketFactory.java:178)

at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:352)

at java.lang.Thread.run(Thread.java:722)

at java.lang.reflect.Array.newArray(Native Method)

at java.lang.reflect.Array.newInstance(Array.java:70)

at oracle.jdbc.driver.BufferCache.get(BufferCache.java:226)

at oracle.jdbc.driver.PhysicalConnection.getCharBuffer(PhysicalConnection.java:7600)

at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:991)

at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1170)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)

at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3677)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)

at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:172)

at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:172)

at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)

at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)

at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81)

at $Proxy58.execute(Unknown Source)

at org.apache.ibatis.executor.statement.PreparedStatementHandler.query(PreparedStatementHandler.java:56)

at org.apache.ibatis.executor.statement.RoutingStatementHandler.query(RoutingStatementHandler.java:70)

at org.apache.ibatis.executor.SimpleExecutor.doQuery(SimpleExecutor.java:57)

at org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:267)

at org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:141)

at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:105)

at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:81)

at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:101)

at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:95)

at org.activiti.engine.impl.db.DbSqlSession.selectListWithRawParameter(DbSqlSession.java:301)

at org.activiti.engine.impl.db.DbSqlSession.selectList(DbSqlSession.java:292)

at org.activiti.engine.impl.db.DbSqlSession.selectList(DbSqlSession.java:287)

at org.activiti.engine.impl.db.DbSqlSession.selectList(DbSqlSession.java:274)

at org.activiti.engine.impl.persistence.entity.JobManager.findUnlockedTimersByDuedate(JobManager.java:125)
4 REPLIES 4

jatz
Champ in-the-making
Champ in-the-making
We have upped the java memory params. WIll let you know if we can replicate it

jbarrez
Star Contributor
Star Contributor
Depends on what else you are putting on that Tomcat …

jbarrez
Star Contributor
Star Contributor
(eg webapp using Activiti)

jatz
Champ in-the-making
Champ in-the-making
Yes..there was another really heavy process going on which killed the jobs. Also with such low parameter settings it was never going to run the webapp.