Forum Discussion

morciani's avatar
morciani
Occasional Contributor
16 years ago

'Java heap space...' error when opening Test Requests

Hi All,

I have been experiencing this problem using SoapUI Pro (Version 2.5.1).  I am working with fairly large pieces of XML- this problem manifests intself when I attempt to open a third piece of XML (Test Request) within the same SoapUI session.  It happens like this:

1.  Open a Test Request, work with it, edit it, submit it, do whatever.
2.  Open a second Test Request, work with it, edit it, do whatever.
3.  Attempt to open a third Test Request- BANG.  SoapUI freezez and my entire machine comes to a screeching halt.  I'm forced to kill SoapUI and relaunch.

This ALWAYS happens on my third attempt at opening a test request during the same session.  I can always open two requests, never a third.  It happens regardless of what other programs I am running on my machine- it happens even when SoapUI is the only application running.  Also, it does not seem to matter what else I do within SoapUI when or during the first two requests are open.  The act of opening the third requests seems to be the straw breaking the camels back.  It is like the machine is running out of memory and choking...  I've avoided the problem by exiting and relaunching after every third Test Request that I need to send, but this is really starting to hamper my productivity.

I am running a 1.73 mhZ Pentium with 2GB RAM.  Below is the stack trace from the command window that runs in the background:

10:12:35,629 INFO  [WorkspaceImpl] Saved workspace to [\\R-INTM-0001-CLA\Clientd
ata$\n0170217\default-soapui-workspace.xml]
Exception in thread "MemoryMonitor" java.lang.OutOfMemoryError: Java heap space
        at com.eviware.soapui.support.monitor.MonitorPanel$Surface.run(MonitorPa
nel.java:211)
        at java.lang.Thread.run(Unknown Source)
10:28:42,941 ERROR [SoapUI] An error occured [Java heap space], see error log fo
r details
Exception in thread "AutoSave Timer" java.lang.OutOfMemoryError: Java heap space

        at org.apache.xmlbeans.impl.store.Xobj$ElementXobj.newNode(Xobj.java:2726)
        at org.apache.xmlbeans.impl.store.Xobj.copyNode(Xobj.java:1111)
        at org.apache.xmlbeans.impl.store.Xobj.copy_contents_from(Xobj.java:2331)
        at org.apache.xmlbeans.impl.store.Xobj.copy(Xobj.java:2405)
        at org.apache.xmlbeans.impl.values.XmlObjectBase._copy(XmlObjectBase.java:155)
        at org.apache.xmlbeans.impl.values.XmlObjectBase._copy(XmlObjectBase.java:138)
        at org.apache.xmlbeans.impl.values.XmlObjectBase.copy(XmlObjectBase.java:119)
        at com.eviware.soapui.impl.wsdl.WsdlProjectPro.saveIn(SourceFile:205)
        at com.eviware.soapui.impl.wsdl.WsdlProject.saveBackup(WsdlProject.java:619)
        at com.eviware.soapui.impl.wsdl.WsdlProjectPro.createBackup(SourceFile:575)
        at com.eviware.soapui.impl.wsdl.WsdlProjectPro.save(SourceFile:361)
        at com.eviware.soapui.impl.WorkspaceImpl.save(WorkspaceImpl.java:293)
        at com.eviware.soapui.SoapUI$AutoSaveTimerTask.run(SoapUI.java:1244)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)

Any ideas or help is appreciated.  Thank you!

-Mike

2 Replies

  • morciani's avatar
    morciani
    Occasional Contributor
    I upgraded to the 10/6/2009 build of SoapUI Pro 3.0.1.  This fixed the issue!  I noticed that the -Xmx????m setting is set to -Xmx1000m after doing the upgrade, so maybe this is taking care of the issue.  At any rate, the problem is solved!  Thank you!

    -Mike