SOAPUI thread end troubleshooting

[ecoly]

Hello guys,

I got a big problem using open source version of soapui. I got a server that run permantly and that load wsdl project and run them when a network client ask it.

But when I look the jvm status on my java server with visual vm I see a lot of test suite runner threads that are never end.

This is how a part of my code work :

public class MyTestCaseRunner extends AbstractSoapUITestRunner implements TestSuiteRunListener, ProjectRunListener {

....

 @Override
  public boolean runRunner(){

       final WsdlProject project = XXX.loadWsdlProject(path);

       initProjectProperties(project);

       project.run(new StringToObjectMap(), false);

  }

}

Each time I run the runRunner method a lot of thread are created for running test suite but they never end.

It's a big problem for me because my server must run 24 hours a day. When I come in the moorning I see hundreds of threads in Park state.

Is that a bug in SOAPUI thread pool management or is there a mistake or a bad approach in my code ?

Thanks for your help.

[nmrao]

Ok thanks. Any sample report that intended to create?

By the way, the class attached does not have anything that creates report on the quick glance.

[ecoly]

I removed this code because it is not important for you to see a sample of report or how it is generated.

What you need to see is that wsdl project file execution in the soapui framework seems to have some problem of thread pool management.

[nmrao]

Well. First If I were you, then I look for ways to achieve the same thing using out-0f-box functionalities. So that it guarantees that I do not introduce any new issue.

If I write custom code, then there are also chances that my code might possibly also contribute to new issue. So, need to avoid this situation.

Request you for a dummy report that you intended to create, because to see if it is possible to achieve without writing custom code or just using stylesheet etc.

May be you can try reproducing using testrunner and see if you run in to the same. Because, the utility is used widely to execute the tests command line and never heard something like what you mentioned in the forum.

By the way, are you running the tests in Parallell mode?

[ecoly]

In fact I am using stylsheet, but it is not important.

The problem, I repeat, is the thread pool management.

Thanks you for getting time for me!

ecoly

[ecoly]

Hello,

no I am not using parallel mode.

Did you investigate the problem ?

[nmrao]

Please note that it is a community, sharing the knowledge or help by other community members.

Understand / do not expect others work on your problem.

[nmrao]

Have you looked at the earlier reply? what have you done based on that? There is no reply to the requested information regarding how the desired report should like?
And you expect others to investigate?

[ecoly]

OK,

the early replies did not help.

So I have to patch the soapui source code.

I was expected that the soapui team will investigate this problem that may be a soapui framework bug.

I will check the source code by myself and patch it.

Thanks you.

[ecoly]

Hello,

after some check with visualvm, I saw that the number of thread ia growing up until ~230 threads.

I think that it is just a pool that suffer of over sizing. But it is not a real soapui bug, since the number stop to grow.

Sorry for disturbing you.