ServiceMix 4.2 crash after SA deployment

[bastien78320]

Hello,

I use Fuse ServiceMix 4.2 for 2 weeks now with no major problems. I have successfully deployed and tested several BPEL process. But today while I was about to test a new one, the server crashed after I deployed the Service Assembly. I tried to restart the server but it continue to crash. I also tried to restart Windows, without succes.

I decided to download a clean version of ServiceMix from fusesource.com and test it only with a SA wich I know it works. But same problem.

So now I'm stuck. Does anyone have an idea how to solve this problem?

Thank you in advance.

Bastien

PS : sorry for the bad english

[gertv]

Bastien,

Could you clarify what you mean by a server crash?  Does the server stop responding, does the process end, are you seeing exceptions in the log, ...?

If the container is still running but not responding, could you try using jstack (or Ctrl-Break) to create a thread dump?  If it's an exception, it would be good to be able to see the exception (with a few dozen lines of extra context logging before/after it).

Regards,

Gert

[bastien78320]

Thank you for your quick answer.

I mean by crash that the server shutdown automatically every time I start the server. If I remove all the SAs from the deploy directory the server stop crashing.

There is no exception in the log file except may be this warning :

09:26:17,890 | WARN  | xtenderThread-47 | ServiceAssemblyInstaller         | er.impl.ServiceAssemblyInstaller  177 | Problem undeploying SU su-mailService-provider

[bastien78320]

I think I found the problem. In fact my SA doesn't work. I tried with another SA and it work fine. I think the problem is caused by the wsdl of my web service.

Anyway its strange that ServiceMix crash because of a wsdl file..

[gertv]

Bastien,

You're right: the container should never behave that way, regardless of what you deploy on it.  If you can provide us with an example of a SA (e.g. the one you have now but with any proprietary bits removed) that causes this, we should be able to reproduce and fix this for the next version of FUSE ESB.

Regards,

Gert

[bastien78320]

Of Course. Where can I sent my SA? May be an e-mail adress?

[gertv]

L.S.,

If you could create a JIRA issue at https://issues.apache.org/activemq and attach your SA there, that would be awesome!

Thanks a lot,

Gert

[bastien78320]

I created the JIRA issue with my SA in attachment.

https://issues.apache.org/activemq/browse/SMX4-529

Thank you.

Bastien

[bastien78320]

I found the reason of the problem!

In my WSDL file I have 2 xsd file import. And these xsd files mutually import themselves. I think it caused an infinite loop and stop the server.

I rewrote the wsdl and xml schema and it works now.

[gertv]

Bastien,

Thanks for the feedback and for raising the issue!  I'll take a look at the issue and see if/how we can either prevent the circular import to kill the server and/or provide a useful message somehow to help people troubleshoot that kind of problem.

Thanks again,

Gert