Forum Discussion

scsete's avatar
New Contributor
7 years ago

com.eviware.soapui.DefaultSoapUICore cannot be cast to com.eviware.soapui.mockaswar.MockAsWarCoreInt

I have created a REST mock service with ServiceV PRO version 2.2.0 and after exporting the war file, i'm getting the following error, when i try to access the endpoint in the mock(Tomcat 8.0.48):

Tomcat log:
10-Jan-2018 10:15:02.601 INFO [http-apr-8080-exec-4] com.eviware.soapui.mockaswar.MockAsWarServlet.init Starting REST Virt [REST Virt 1]
10-Jan-2018 10:15:02.608 SEVERE [http-apr-8080-exec-4] com.eviware.soapui.mockaswar.MockAsWarServlet.init null
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.start(
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.<init>(
at com.eviware.soapui.mockaswar.MockAsWarServlet.init(
at javax.servlet.GenericServlet.init(
Why is it trying to deal with Wsdl stuff? No idea...

POSTman message body:

<h1>HTTP Status 500 - com.eviware.soapui.DefaultSoapUICore cannot be cast to com.eviware.soapui.mockaswar.MockAsWarCoreInterface</h1>
<div class="line"></div>
<b>type</b> Exception report
<u>com.eviware.soapui.DefaultSoapUICore cannot be cast to com.eviware.soapui.mockaswar.MockAsWarCoreInterface</u>
<u>The server encountered an internal error that prevented it from fulfilling this request.</u>
<pre>java.lang.ClassCastException: com.eviware.soapui.DefaultSoapUICore cannot be cast to com.eviware.soapui.mockaswar.MockAsWarCoreInterface
<u>The full stack trace of the root cause is available in the Apache Tomcat/8.0.48 logs.</u>
<hr class="line">
<h3>Apache Tomcat/8.0.48</h3>

Export config attached.

I have read the java version matters, where it is exported and where i run, they are identical(JAVA 8_151)

Anyone has any idea, what went wrong?
Any suggestion is welcome!

3 Replies

    • TLerche's avatar
      Occasional Contributor

      Hello is here any solution available?

      • AlexKaras's avatar
        Champion Level 3



        What version of ServiceV you are using? Several updates have been released since past January.

        If the problem still exists for the latest 2.5.0 version of ServiceV, I would recommend to contact Support directly via the form and reference this thread.