Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Heap Space?? HELP¡

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Heap Space?? HELP¡

    Hi, I've set te heap space to 512M and I'm going on getting the next message, anyone know what's the problem??

    INFO 2007-10-17 16:25:43,854 [Thread-0] com.webreach.mirth.server.Mirth: starting mirth server...
    WARN 2007-10-18 08:40:50,416 [SslListener0-0] org.mortbay.jetty.context.Mirth Server: /channelstatistics:
    com.webreach.mirth.server.controllers.ControllerEx ception: com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby-statistic.xml.
    --- The error occurred while applying a parameter map.
    --- Check the getReceivedCount-InlineParameterMap.
    --- Check the results (failed to retrieve results).
    --- Cause: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at com.webreach.mirth.server.controllers.ChannelStati sticsController.getReceivedCount(ChannelStatistics Controller.java:63)
    at com.webreach.mirth.server.controllers.ChannelStati sticsController.getStatistics(ChannelStatisticsCon troller.java:52)
    at com.webreach.mirth.server.servlets.ChannelStatisti csServlet.doPost(ChannelStatisticsServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:616)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler.di spatch(WebApplicationHandler.java:473)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:568)
    at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1530)
    at org.mortbay.jetty.servlet.WebApplicationContext.ha ndle(WebApplicationContext.java:633)
    at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1482)
    at org.mortbay.http.HttpServer.service(HttpServer.jav a:909)
    at org.mortbay.http.HttpConnection.service(HttpConnec tion.java:816)
    at org.mortbay.http.HttpConnection.handleNext(HttpCon nection.java:982)
    at org.mortbay.http.HttpConnection.handle(HttpConnect ion.java:833)
    at org.mortbay.http.SocketListener.handleConnection(S ocketListener.java:244)
    at org.mortbay.util.ThreadedServer.handle(ThreadedSer ver.java:357)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadP ool.java:534)
    Caused by: com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby-statistic.xml.
    --- The error occurred while applying a parameter map.
    --- Check the getReceivedCount-InlineParameterMap.
    --- Check the results (failed to retrieve results).
    --- Cause: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryWithCallback(GeneralStatemen t.java:185)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryForObject(GeneralStatement.j ava:104)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForObject(SqlMapExecutorDelegate.java:566)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForObject(SqlMapExecutorDelegate.java:541)
    at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.qu eryForObject(SqlMapSessionImpl.java:106)
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.que ryForObject(SqlMapClientImpl.java:83)
    at com.webreach.mirth.server.controllers.ChannelStati sticsController.getReceivedCount(ChannelStatistics Controller.java:61)
    ... 17 more
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at org.apache.derby.impl.jdbc.SQLExceptionFactory.get SQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.javaException(Unkn own 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.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.ConnectionChild.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnT ransactionError(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.movePosi tion(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unk nown Source)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.han dleResults(SqlExecutor.java:380)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.han dleMultipleResults(SqlExecutor.java:301)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteQuery(SqlExecutor.java:190)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.sqlExecuteQuery(GeneralStatement.java:20 5)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryWithCallback(GeneralStatemen t.java:173)
    ... 23 moreat org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.javaException(Unkn own Source)
    at org.apache.derby.impl.jdbc.TransactionResourceImpl .wrapInSQLException(Unknown Source)

    WARN 2007-10-18 08:40:53,449 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:40:55,397 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:40:56,309 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:41:04,524 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.1] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: f3e63a1f-5a6e-4021-b3dd-041bd70e8492: java.lang.ClassCastException: java.lang.OutOfMemoryError
    java.lang.ClassCastException: java.lang.OutOfMemoryError
    at com.informix.jdbc.IfxDriver.connect(IfxDriver.java )
    at java.sql.DriverManager.getConnection(DriverManager .java:525)
    at java.sql.DriverManager.getConnection(DriverManager .java:171)
    at org.mule.providers.jdbc.JdbcConnector.getConnectio n(JdbcConnector.java:373)
    at org.mule.providers.jdbc.JdbcMessageReceiver.getMes sages(JdbcMessageReceiver.java:119)
    at org.mule.providers.TransactedPollingMessageReceive r.poll(TransactedPollingMessageReceiver.java:108)
    at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:73)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
    at java.lang.Thread.run(Thread.java:595)
    ERROR 2007-10-18 08:42:15,656 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.7] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    WARN 2007-10-18 08:42:20,092 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:42:20,771 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.4] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    WARN 2007-10-18 08:42:21,382 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:21,990 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:22,605 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:23,212 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:23,822 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:24,436 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:25,044 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:25,656 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:26,270 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:26,882 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:27,808 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:28,424 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:29,038 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:29,651 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:38,259 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:38,867 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:40,994 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:41,601 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:42:42,281 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:42:50,220 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.5] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    ERROR 2007-10-18 08:42:54,387 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.10] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    ERROR 2007-10-18 08:42:59,687 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.10] com.webreach.mirth.server.controllers.MessageObjec tController: could not log message: id=9b41c609-888b-47fd-90b3-d10237d1d58c
    com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby-message.xml.
    --- The error occurred while applying a parameter map.
    --- Check the Message.insert-message-param.
    --- Check the statement (update failed).
    --- Cause: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeUpdate(GeneralStatement.java:91)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.insert(SqlMapExecutorDelegate.java:447)
    at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.in sert(SqlMapSessionImpl.java:82)
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.ins ert(SqlMapClientImpl.java:59)
    at com.webreach.mirth.server.controllers.MessageObjec tController.updateMessage(MessageObjectController. java:76)
    at com.webreach.mirth.server.mule.transformers.XMLToM essageObject.doTransform(XMLToMessageObject.java:5 5)
    at org.mule.transformers.AbstractTransformer.transfor m(AbstractTransformer.java:197)
    at org.mule.transformers.AbstractTransformer.transfor m(AbstractTransformer.java:200)
    at org.mule.transformers.AbstractTransformer.transfor m(AbstractTransformer.java:200)
    at org.mule.impl.MuleEvent.getTransformedMessage(Mule Event.java:251)
    at org.mule.impl.MuleEventContext.getTransformedMessa ge(MuleEventContext.java:100)
    at com.webreach.mirth.server.mule.components.Channel. onCall(Channel.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.mule.model.DynamicEntryPoint.invokeCurrent(Dyn amicEntryPoint.java:168)
    at org.mule.model.DynamicEntryPoint.invoke(DynamicEnt ryPoint.java:90)
    at org.mule.impl.DefaultLifecycleAdapter.onCall(Defau ltLifecycleAdapter.java:177)
    at org.mule.impl.DefaultLifecycleAdapter.intercept(De faultLifecycleAdapter.java:232)
    at org.mule.impl.InterceptorsInvoker.execute(Intercep torsInvoker.java:53)
    at org.mule.impl.model.DefaultMuleProxy.onCall(Defaul tMuleProxy.java:230)
    at org.mule.impl.model.seda.SedaComponent.doSend(Seda Component.java:209)
    at org.mule.impl.model.AbstractComponent.sendEvent(Ab stractComponent.java:277)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:201)
    at org.mule.routing.inbound.InboundMessageRouter.send (InboundMessageRouter.java:161)
    at org.mule.routing.inbound.InboundMessageRouter.rout e(InboundMessageRouter.java:128)
    at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR eceiver.java:492)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:271)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:234)
    at org.mule.providers.jdbc.JdbcMessageReceiver.proces sMessage(JdbcMessageReceiver.java:103)
    at org.mule.providers.TransactedPollingMessageReceive r$MessageProcessorWorker.doInTransaction(Transacte dPollingMessageReceiver.java:159)
    at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:72)
    at org.mule.providers.TransactedPollingMessageReceive r$MessageProcessorWorker.run(TransactedPollingMess ageReceiver.java:149)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at org.apache.derby.impl.jdbc.SQLExceptionFactory.get SQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.javaException(Unkn own 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.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.ConnectionChild.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedStatement.executeS tatement(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedPreparedStatement. executeStatement(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedPreparedStatement. execute(Unknown Source)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteUpdate(SqlExecutor.java:81)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.sqlExecuteUpdate(GeneralStatement.java:2 00)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeUpdate(GeneralStatement.java:78)
    ... 37 more

    Caused by:
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:31,683 [SslListener0-0] org.mortbay.http.HttpConnection: null null null
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:18,170 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:43,505 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:44,420 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:45,033 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:45,645 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:46,329 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:46,942 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:47,550 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:48,158 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:48,767 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:43:49,746 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.2] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    WARN 2007-10-18 08:43:50,657 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:43:51,573 [SslListener0-0] org.mortbay.http.HttpConnection: null null null
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:43:56,210 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.8] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    WARN 2007-10-18 08:44:04,185 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:04,806 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:05,805 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:06,423 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:07,037 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:07,649 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:08,639 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:09,250 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:09,861 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:10,472 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:11,388 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:12,309 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:12,919 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:13,837 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:14,450 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    ERROR 2007-10-18 08:44:15,132 [f3e63a1f-5a6e-4021-b3dd-041bd70e8492_source_connector._jdbcEndpoint#118116 5029.receiver.9] org.mule.providers.jdbc.JdbcMessageReceiver: Error in the ACK sentence of the JDBC connection, but the message is being sent anywayjava.lang.ClassCastException: java.lang.OutOfMemoryError
    WARN 2007-10-18 08:44:17,037 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:19,035 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:19,644 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:20,254 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:20,866 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:21,476 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:22,089 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:23,005 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:23,623 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:24,545 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:27,387 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:45,959 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:46,567 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:44:58,088 [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8443]]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: Java heap space
    WARN 2007-10-18 08:45:03,057 [SslListener0-0] org.mortbay.jetty.context.Mirth Server: /channels:
    com.webreach.mirth.server.controllers.ControllerEx ception: com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby-channel.xml.
    --- The error occurred while applying a parameter map.
    --- Check the getChannelRevision-InlineParameterMap.
    --- Check the results (failed to retrieve results).
    --- Cause: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at com.webreach.mirth.server.controllers.ChannelContr oller.getChannelSummary(ChannelController.java:148 )
    at com.webreach.mirth.server.servlets.ChannelServlet. doPost(ChannelServlet.java:68)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:616)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler.di spatch(WebApplicationHandler.java:473)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:568)
    at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1530)
    at org.mortbay.jetty.servlet.WebApplicationContext.ha ndle(WebApplicationContext.java:633)
    at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1482)
    at org.mortbay.http.HttpServer.service(HttpServer.jav a:909)
    at org.mortbay.http.HttpConnection.service(HttpConnec tion.java:816)
    at org.mortbay.http.HttpConnection.handleNext(HttpCon nection.java:982)
    at org.mortbay.http.HttpConnection.handle(HttpConnect ion.java:833)
    at org.mortbay.http.SocketListener.handleConnection(S ocketListener.java:244)
    at org.mortbay.util.ThreadedServer.handle(ThreadedSer ver.java:357)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadP ool.java:534)
    Caused by: com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby-channel.xml.
    --- The error occurred while applying a parameter map.
    --- Check the getChannelRevision-InlineParameterMap.
    --- Check the results (failed to retrieve results).
    --- Cause: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryWithCallback(GeneralStatemen t.java:185)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryForList(GeneralStatement.jav a:123)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForList(SqlMapExecutorDelegate.java:615)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForList(SqlMapExecutorDelegate.java:589)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForMap(SqlMapExecutorDelegate.java:706)
    at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.qu eryForMap(SqlMapSessionImpl.java:152)
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.que ryForMap(SqlMapClientImpl.java:129)
    at com.webreach.mirth.server.controllers.ChannelContr oller.getChannelSummary(ChannelController.java:84)
    ... 16 more
    Caused by: java.sql.SQLException: Java exception: 'Java heap space: java.lang.OutOfMemoryError'.
    at org.apache.derby.impl.jdbc.SQLExceptionFactory.get SQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.javaException(Unkn own 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.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.ConnectionChild.handleE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnT ransactionError(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.movePosi tion(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unk nown Source)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.han dleResults(SqlExecutor.java:380)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.han dleMultipleResults(SqlExecutor.java:301)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteQuery(SqlExecutor.java:190)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.sqlExecuteQuery(GeneralStatement.java:20 5)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryWithCallback(GeneralStatemen t.java:173)
    ... 23 more

  • #2
    Re:Heap Space?? HELP¡

    Sometimes, JVM get stuck with this message. Try restarting the server (the fisical machine).

    Comment


    • #3
      Re:Heap Space?? HELP¡

      The error is raised again...

      We have changed the mith instalation folder by the backup instalation forder we preparated and it runs.

      Thanks.

      Comment


      • #4
        Re:Heap Space?? HELP¡

        If I'm reading the trace correctly the problem might not be the Java heap, instead it looks like it could be a nasty SQL statement.

        Can you post your channel?
        Jon Bartels

        Zen is hiring!!!!
        http://consultzen.com/careers/
        Talented healthcare IT professionals wanted. Engineers to sales to management.
        Good benefits, great working environment, genuinely interesting work.

        Comment


        • #5
          Re:Heap Space?? HELP¡

          Do you think It could be dangerous? Do you think it could be a problem retrieving several rows and sending/updating just one?

          SQL-Statement

          select code, msg, state
          from tb_ready_msg
          where state = 'READY'
          order by date asc

          On-Update Statement

          update tb_ready_msg
          state= 'PROCESSED'
          where code= ${code}

          Comment

          Working...
          X