Forum Discussion
austino
10 years agoContributor
Hi Marcus,
Yes, it does occur very randomly. Our service project is pretty big and a lot of it is modular, so I don't think it's feasible for me to break it down into other projects. Earlier in the thread it was mentioned to increase the java max heap space and that has increased SoapUI performance greatly, but didn't stop the bug from appearing. Also, I've been having this issue since I started the project in August (when there were way fewer services), I just didn't know what was going on at that time. Thank you for looking into it.
Yes, it does occur very randomly. Our service project is pretty big and a lot of it is modular, so I don't think it's feasible for me to break it down into other projects. Earlier in the thread it was mentioned to increase the java max heap space and that has increased SoapUI performance greatly, but didn't stop the bug from appearing. Also, I've been having this issue since I started the project in August (when there were way fewer services), I just didn't know what was going on at that time. Thank you for looking into it.
- austino9 years agoContributor
Just wanted to mention that this issue is still present in Soap NG in the Ready! API program using version 1.4.1.