Forum Discussion

anders_wallsten's avatar
anders_wallsten
New Contributor
14 years ago
Solved

Sometimes "Missing operation for soapAction"

Hi,

I have created a mock service and I have the following strange behaviour:

1. Open SoapUI
2. Start MockService
3. Run a test case/test request against the MockService (works great!)
4. Run the test case/test request again (does not work!!!)
=> I get "Missing operation for soapAction"
=> Very strange since it worked the first time (I promise nothing has been changed from the first time)
5. Wait for a couple of minutes (works again!)
6. Run the test case/test request again (does not work!!!)
=> I get "Missing operation for soapAction"
=> Very strange since it worked the first time

Has anyone experienced the same problem? Is there a solution/workaround for this?

BR,
Anders
  • anders_wallsten's avatar
    anders_wallsten
    14 years ago
    It is when you have the settings flag "HTTP Settings/Logs wire content of all mock requests" set to true.
    => Uncheck the flag and it works fine!

13 Replies

Sort By
  • anders_wallsten's avatar
    anders_wallsten
    New Contributor
    14 years ago
    It is when you have the settings flag "HTTP Settings/Logs wire content of all mock requests" set to true.
    => Uncheck the flag and it works fine!
    • j_g's avatar
      j_g
      Visitor
      8 years ago

      Hi, i just registered here to thank you, i had this same problem and this solved it.

    • Za_Dolber's avatar
      Za_Dolber
      New Contributor
      8 years ago

      Register here after almst six years to say thanks.

      On SoapUI 5.2.1 I've had the same problem and it fixed it.

      • monmonmon's avatar
        monmonmon
        New Contributor
        8 years ago

        Hi, thank you. I had the same issue and tried to find the solution for several days.

        Thank you very for sharing the solution!!  5.2.0 had the same problem. It fixed now!

  • anders_wallsten's avatar
    anders_wallsten
    New Contributor
    14 years ago
    Hi,

    A bit more info:

    I am using SoapUI, ver 3.6.

    I get the following in the error.log (only when the request does not work):

    Wed Dec 22 07:11:35 CET 2010:ERROR:com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [urn:base-teliasonera-com:services:managecustomer:v2_0:GetCustomersBySearchCriteria] and body element [null] with SOAP Version [SOAP 1.1]
    com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [urn:base-teliasonera-com:services:managecustomer:v2_0:GetCustomersBySearchCriteria] and body element [null] with SOAP Version [SOAP 1.1]
    at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchPostRequest(WsdlMockRunner.java:327)
    at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchRequest(WsdlMockRunner.java:384)
    at com.eviware.soapui.monitor.JettyMockEngine$ServerHandler.handle(JettyMockEngine.java:701)
    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Wed Dec 22 07:11:35 CET 2010:ERROR:java.lang.IllegalStateException: WRITER
    java.lang.IllegalStateException: WRITER
    at org.mortbay.jetty.Response.getOutputStream(Response.java:594)
    at com.eviware.soapui.monitor.JettyMockEngine$MockRequestLog.log(JettyMockEngine.java:810)
    at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:51)
    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

    BR,
    Anders
  • schoolguy's avatar
    schoolguy
    13 years ago
    hi anders

    thanks a ton for that... i was going crazy with this error...

    cheers
  • stevedearl's avatar
    stevedearl
    New Contributor
    8 years ago

    Hi Smartbear,

     

    Any reason why this bug hasn't been fixed since it was raised seven years ago? I've just wasted an hour on this trying to figure out what the hell was going wrong with my service call.....

     

    Steve

    • NamrataD's avatar
      NamrataD
      New Member
      8 years ago

      I am facing same issue with 4.6.4 version.Tried above mentioned solution.But still issue exists,

       

       

      • Za_Dolber's avatar
        Za_Dolber
        New Contributor
        8 years ago

        I think, i found solution for this:

        In Windows just run SoapUI as Administrator. At my case it helps.

    • mindgnat's avatar
      mindgnat
      Occasional Contributor
      7 years ago

      Good luck getting an answer. SmartBear seems to have abandoned this forum.

  • jmfr94's avatar
    jmfr94
    New Member
    7 years ago

    Thank you for sharing the solution! I had the same issue and tried to find the solution for several days (in several wrong places).

    5.3.0 had the same problem. It fixed now!