Forum Discussion

himanshugrover's avatar
himanshugrover
New Contributor
12 years ago

[Resolved] Deploy as war and weblogic

Hi Everyone,

I am new to SOAP UI and still learning it. I deployed the mocking service war generated using the deploy as a war feature of the SOAP UI 4.5.1.

After deploying the WAR, I tested the mocking service. Strange thing is happening. I got the response for the first request but for subsequent request for the same operation I am not getting the response. I checked out the diagnostic logs of the weblogic which shows the below mentioned error.

Any help would be highly appreciated.

Regards,
Himanshu

[AdminServer] [ERROR] [] [com.eviware.soapui.mockaswar.MockAsWarServlet] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9e4b8ce653d1e16f:-668d251c:1422757715c:-8000-000000000000159f,0] [APP: SalesforceStubs] [[
com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [] and body element [{urn:enterprise.soap.sforce.com}create] with SOAP Version [SOAP 1.1]
at com.eviware.soapui.impl.wsdl.support.soap.SoapUtils.findOperationForRequest(SoapUtils.java:359)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchPostRequest(WsdlMockRunner.java:250)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchRequest(WsdlMockRunner.java:375)
at com.eviware.soapui.mockaswar.MockAsWarServlet$MockServletSoapUICore.dispatchRequest(MockAsWarServlet.java:261)
at com.eviware.soapui.mockaswar.MockAsWarServlet.service(MockAsWarServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

]]
  • An update.

    Tried with SOAP UI 4.6.1. War generation process goes on and on but doesn't generate any war.

    In short no success with SOAP UI 4.6.1. as well.

    Regards,
    Himanshu
  • Hi,

    This is unfortunately a known issue with 4.6.1 release.
    SOAP-906 is tracking this issue, and is fixed in next release.
  • Also,

    To clarify, this in regards to the war file creation in SoapUI.
  • sam9046's avatar
    sam9046
    Occasional Contributor
    Hi, joined here as I am having the exact same problem.

    Tried creating a war file in both the eclipse plugin for SOAP UI and, the individual install of SOAP UI.

    In the eclipse plugin, I get a java null pointer error. In the SOAP UI application itself it just gets stuck generating the war file.

    I've tried this with both my mock service and with the tutorial ones, on two different pc's with the same results.

    Can't try the workaround as the soap ui jar file is not writeable?

    Any other advice, if I roll back a release will this bug not exist?

    Appreciate any advice, thanks,

    sam9046
  • Hi,

    If you use a tool such as 7zip (http://www.7-zip.org/) you should be able to open the jar file and update the jar file in place.


    Regards,
    Marcus
    SmartBear Support
  • sam9046's avatar
    sam9046
    Occasional Contributor
    Hey,

    I used winRAR which wouldn't let me write to the .jar. No longer relevant anyway as I've deleted 4.6.1 and installed 4.6.0... now I can deploy a mock service as a .war.

    I thought great, until I ran it on tomcat and tried going to the URI directly, and I'm getting tons of like box size adjustment lines up on the screen. Is this normal?

    When sending a request into the mock service through soapui (which worked locally) I'm now getting this response:


    <html>
    <head>
    <title>soapUI MockServices Log for project [SOAP WSDL TEST]</title>
    </head>
    <frameset rows="40%,40%,*">
    <frame src="master"/>
    <frame name="detail" src="detail"/>
    <frame src="log"/>
    </frameset>
    </html>


    Any ideas? I am new to soapui so this could easily be me doing something wrong.
  • sam9046's avatar
    sam9046
    Occasional Contributor
    Ok figured this out, I stupidly named my project and endpoint the same name, and didn't put in the additional name for the endpoint ie /mockservice/mockservice.

    It's working as expected. The webui picks up my request as well.

    So seems just an issue with deploy as war functionality in both soapui 4.6.1, and eclipse plugin 4.0.1. Using the application directly and version 4.6.0 fixes this problem for anyone else who navigates to this forum.

    Cheers,

    sam9046