Out of Memory

[dmerck]

I have worked with Shane to have an ADT feed in Mirth1.2.0 populate a Census table, among other things, in a SQL Server database by calling a vbs script from a transformer. We tried it on a few types of ADT messages in a test channel successfully. When we moved to a live feed in the hospital be got blasted by 26000+ messages. When I went to look at some of the messages in status, view messages, I got the following error message. Anyone know why or have any suggestions as to what can be done?

-Dave


com.webreach.mirth.client.core.ClientException: com.webreach.mirth.client.core.ClientException: method failed: HTTP/1.1 500 java%2Esql%2ESQLException%3A+out+of+memory
com.webreach.mirth.client.core.MessageListHandler. getPage(MessageListHandler.java:108)
com.webreach.mirth.client.core.MessageListHandler. getFirstPage(MessageListHandler.java:61)
com.webreach.mirth.client.ui.browsers.message.Mess ageBrowser.makeEventTable(MessageBrowser.java:303)
com.webreach.mirth.client.ui.browsers.message.Mess ageBrowser.filterButtonActionPerformed(MessageBrow ser.java:979)
com.webreach.mirth.client.ui.browsers.message.Mess ageBrowser.loadNew(MessageBrowser.java:189)
com.webreach.mirth.client.ui.Frame.doShowMessages( Frame.java:1743)
com.webreach.mirth.client.ui.Frame$26.actionPerfor med(Frame.java:716)
javax.swing.AbstractButton.fireActionPerformed(Unk nown Source)
javax.swing.AbstractButton$Handler.actionPerformed (Unknown Source)
javax.swing.DefaultButtonModel.fireActionPerformed (Unknown Source)
javax.swing.DefaultButtonModel.setPressed(Unknown Source)
javax.swing.AbstractButton.doClick(Unknown Source)
javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unk nown Source)
javax.swing.plaf.basic.BasicMenuItemUI$Handler.mou seReleased(Unknown Source)
java.awt.Component.processMouseEvent(Unknown Source)
javax.swing.JComponent.processMouseEvent(Unknown Source)
java.awt.Component.processEvent(Unknown Source)
java.awt.Container.processEvent(Unknown Source)
java.awt.Component.dispatchEventImpl(Unknown Source)
java.awt.Container.dispatchEventImpl(Unknown Source)
java.awt.Component.dispatchEvent(Unknown Source)
java.awt.LightweightDispatcher.retargetMouseEvent( Unknown Source)
java.awt.LightweightDispatcher.processMouseEvent(U nknown Source)
java.awt.LightweightDispatcher.dispatchEvent(Unkno wn Source)
java.awt.Container.dispatchEventImpl(Unknown Source)
java.awt.Window.dispatchEventImpl(Unknown Source)
java.awt.Component.dispatchEvent(Unknown Source)
java.awt.EventQueue.dispatchEvent(Unknown Source)
java.awt.EventDispatchThread.pumpOneEventForHierar chy(Unknown Source)
java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
java.awt.EventDispatchThread.pumpEvents(Unknown Source)
java.awt.EventDispatchThread.pumpEvents(Unknown Source)
java.awt.EventDispatchThread.run(Unknown Source)

[chrisl]

Re: Out of Memory

This is fixed in 1.3. The internal DB in 1.2 was very limited.

For the type of message volume you're looking at it would make sense to use the Postgres packages.

-Chris

[dmerck]

Re: Out of Memory


This may sound naive but how would I go about using "Postgres packages"

-Dave

[dmerck]

Re: Out of Memory

Are you suggesting to replace the Mirth internal DB with PostGres Packages or to replace SQL Server we are ultimately populating with Postgres Packages?

-Dave

[chrisl]

Re: Out of Memory

The internal DB. With 1.3 you have the option of using any internal database. If installing on Windows, you will be given the option to choose the database package to use internally for Mirth.

-Chris

[dmerck]

Re: Out of Memory

Thanks Chris, that sounds very promising. Do you know when 1.3 will be available?

-Dave

[dmerck]

Re: Out of Memory

I was able to get it to work by adding addtional filtering on nurseUnit as well as not storing the messages except for errors. Thanks again for the help Chris.

-Dave

[chrisl]

Re: Out of Memory

No problem! Glad it's working, look out for 1.3 though - huge DB improvements.

[jbartels]

Re: Out of Memory

I was able to get it to work by adding addtional filtering on nurseUnit as well as not storing the messages except for errors. Thanks again for the help Chris.

-Dave

Dave,

I'm currently working on some scalability testing for Mirth. Our goal is to find out if Mirth can handle 3 million messages a day (we're testing for a wildly theoretical maximum). I'm still getting some of the testing application hammered out. Though as fast as the Mirth team keeps pushing out new versions it looks like they'll solve the problems before I find them.

It sounds like you have a larger installation using Mirth and if you can spare a few minutes I'd like to hear a bit more about how you're using Mirth. Specifically any issues that you had running on a larger installation so that I can tweak my tests to beat on the soft areas a little more.

Post here or drop an email to [email protected] .

[chrisl]

Re: Out of Memory

Jon,

We'd be very interested in assisting you with getting tests setup or identifying areas that can be improved with Mirth. We've been stress testing 1.3 with batches of 30,000 messages at one time (over LLP and File Reader, going to DB and LLP) and we've noticied dramatic improvements over 1.1 and 1.2. This is magnified when switching to Postgres as the internal DB.

If you have any findings, questions, comments then please contact me directly at chrisl [at] webreachinc.com

Thanks,
-Chris

[jbartels]

Re: Out of Memory

It has always been my goal to contribute the testing results and software back to Mirth.

I should have my testing plan polished off today or tomorrow and I'll post it in the Dev forum for comments.