Forum Discussion

crk's avatar
crk
Occasional Contributor
15 years ago

soapUI and AMF

Hi.
I am using soapUI 3.6.1. I am trying to create an AMF test step. I keep getting the following error.


Wed Nov 17 13:41:31 IST 2010:ERROR:ClientStatusException 
 message: flex.messaging.MessageException: Unsupported AMF version 15,393.
 code: AMFConnection.Call.Failed
   ClientStatusException 
    message: flex.messaging.MessageException: Unsupported AMF version 15,393.
    code: AMFConnection.Call.Failed
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:277)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.executeAmfCall(AMFSubmit.java:185)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.run(AMFSubmit.java:129)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
   Caused by: flex.messaging.MessageException: Unsupported AMF version 15,393.
    at flex.messaging.io.amf.AmfMessageDeserializer.readMessage(AmfMessageDeserializer.java:98)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponseBody(SoapUIAMFConnection.java:411)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponse(SoapUIAMFConnection.java:397)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.send(SoapUIAMFConnection.java:489)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:267)
    ... 8 more


I am using BlazeDS 3.2.0.3978. And I am following the steps in this (http://www.soapui.org/AMF/calling-amf-services.html) tutorial. I read some previous posts in the forum and am at a loss to understand why I am getting this message. Any help will be greatly appreciated!

Thanks & Regards,
Ravi.
  • crk's avatar
    crk
    Occasional Contributor
    15 years ago
    hmm.. I was able to solve that issue.
    How can we test a streaming channel using soapUI? I have specified the endpoint, but what about the AMF Call field? It will be great if someone can give me an example or at least guide me in the right direction.

    Regards,
    Ravi.
  • robigre's avatar
    robigre
    15 years ago
    Hi,

    how did you resolve this? - I am getting a similar issue (unsupported AMF version 15, 432) running against a running BlazeDS service.

    the version of BlazeDS is 3.2

    Greg
  • newsoapuiuser's avatar
    newsoapuiuser
    New Contributor
    14 years ago
    I am also facing this issue. I am using soapui 3.6.
    If anyone was able to resolve this please suggest a solution

    Thanks,


    Thu Apr 07 11:43:57 PDT 2011:ERROR:ClientStatusException
    message: flex.messaging.MessageException: Unsupported AMF version 15,464.
    code: AMFConnection.Call.Failed
    ClientStatusException
    message: flex.messaging.MessageException: Unsupported AMF version 15,464.
    code: AMFConnection.Call.Failed
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:277)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.executeAmfCall(AMFSubmit.java:185)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.run(AMFSubmit.java:129)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    Caused by: flex.messaging.MessageException: Unsupported AMF version 15,464.
    at flex.messaging.io.amf.AmfMessageDeserializer.readMessage(AmfMessageDeserializer.java:98)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponseBody(SoapUIAMFConnection.java:411)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponse(SoapUIAMFConnection.java:397)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.send(SoapUIAMFConnection.java:489)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:267)
    ... 8 more
  • kaja78's avatar
    kaja78
    14 years ago
    I faced this issue on soapui 4.0.1. The cause was, that my amf endpoint was secured - it required basic authentication. After I disabled authorization constraint in blazeds app, it started to work as expected.