Test case logs and Image upload issue
Hi Support team, I am writing this again because I have posted same question in the forum but for some reason, i don't know it is deleted. It would be great if you guys answer the following questio...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi!
regarding the memory issue this is how it works: when soapUI starts the java runtime it is configured with a max memory setting (-Xmx????m) in the corresponding bar/vmoptions files; this is how much the JVM is allowed to use before running out of memory. The default settings are pretty high (1024?) which means that there is a lot of "space" not being used in most situations. It also means the JVM will not reclaim any left-over memory until the limit has been reached; in your case it seams the 5xx Mb of memory are still well be below the default limit and therefore the JVM won't try to purge or reuse it, event though it might not be used by soapUI. When the JVM runs out of memory it runs a process called "garbage collection" to try to reclaim memory that is no longer being used by the application, in the soapUI GUI you can trigger this manually by right-clicking in the memory-log and selecting "Run GC"; usually you will see a drop in memory which shows how much memory that was allocated by the JVM but not actually being used any more.
In your case, it seems to me that the memory behavior is as expected; what would be interesting is to run the garbage collector after your tests to see how much of the allocated memory is actually being used; what if you run from inside the UI and select the "Run GC" option as mentioned above?
Hope that makes sense! (and is correct :-)
regards!
/Ole
eviware.com
regarding the memory issue this is how it works: when soapUI starts the java runtime it is configured with a max memory setting (-Xmx????m) in the corresponding bar/vmoptions files; this is how much the JVM is allowed to use before running out of memory. The default settings are pretty high (1024?) which means that there is a lot of "space" not being used in most situations. It also means the JVM will not reclaim any left-over memory until the limit has been reached; in your case it seams the 5xx Mb of memory are still well be below the default limit and therefore the JVM won't try to purge or reuse it, event though it might not be used by soapUI. When the JVM runs out of memory it runs a process called "garbage collection" to try to reclaim memory that is no longer being used by the application, in the soapUI GUI you can trigger this manually by right-clicking in the memory-log and selecting "Run GC"; usually you will see a drop in memory which shows how much memory that was allocated by the JVM but not actually being used any more.
In your case, it seems to me that the memory behavior is as expected; what would be interesting is to run the garbage collector after your tests to see how much of the allocated memory is actually being used; what if you run from inside the UI and select the "Run GC" option as mentioned above?
Hope that makes sense! (and is correct :-)
regards!
/Ole
eviware.com