Newbie to Flex

Hi,

are you using SoapUI to send amf messages?

regards
Nebojsa
eviware.com

I'm using soapUI 3.5-beta2

Hi,

can you please paste error log here, so we can look into deeper stack trace.

regards
nebojsa
eviware.com

Here tis...

The first error message was running on tomcat 6.0.18...below is running on Jetty..

Tue Feb 09 12:06:04 PST 2010:ERROR:ClientStatusException
message: flex.messaging.MessageException: Unsupported AMF version 3,338.
code: AMFConnection.Call.Failed
  ClientStatusException
  message: flex.messaging.MessageException: Unsupported AMF version 3,338.
  code: AMFConnection.Call.Failed
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:276)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.executeAmfCall(AMFSubmit.java:184)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.run(AMFSubmit.java:128)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  at java.lang.Thread.run(Thread.java:619)
  Caused by: flex.messaging.MessageException: Unsupported AMF version 3,338.
  at flex.messaging.io.amf.AmfMessageDeserializer.readMessage(AmfMessageDeserializer.java:98)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponseBody(SoapUIAMFConnection.java:410)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.processHttpResponse(SoapUIAMFConnection.java:396)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.send(SoapUIAMFConnection.java:488)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.SoapUIAMFConnection.call(SoapUIAMFConnection.java:266)
  ... 8 more
Tue Feb 09 12:06:04 PST 2010:ERROR:java.lang.NullPointerException
  java.lang.NullPointerException
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFResponse.initAMFHeaders(AMFResponse.java:197)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFResponse.initHeaders(AMFResponse.java:183)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFResponse.(AMFResponse.java:67)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.createResponse(AMFSubmit.java:165)
  at com.eviware.soapui.impl.wsdl.panels.teststeps.amf.AMFSubmit.run(AMFSubmit.java:129)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  at java.lang.Thread.run(Thread.java:619)

Another wrinkle...I get the error message "unsupported AMF version" when I'm testing locally and running windows XP.  Deploying the war to a client Linux box and testing with it...soapUI works fine.

Any ideas ??

Hi,

this is very tricky.
Version number can be 0 or 3 ( http://osflash.org/documentation/amf/envelopes/remoting )
and any other number will raise error ( http://kb2.adobe.com/cps/407/kb407204.html )


But if SoapUI works fine when you deploy war on other server, we can conclude that this is something to do with the server.

Don't think that this will help you but that is what I've found.

If you manged to solve your problem , please share that with us.

regards
nebojsa
eviware.com

Hi,

I am trying to follow the instructions on the AMF tutorial and I also get this error. However, I was not able to download the flexsample.jar as it isn't found on the server. I looked for it in the blaze-ds distro but can't find it there either. Is this jar required for sending AMf requests? If so, do you know where I can find it?

Thanks!

Hi,


here is the jar file in attachment. I changed extension to .txt just to manage to upload on server so you need to rename it back to flexsample.jar
The file was probably lost due to moving to new web site. Sorry for inconvenience!

Regards
Nebojsa
eviware.com

I am facing the same problem.

SmartBear Support wrote:

Hi, this is very tricky. Version number can be 0 or 3 ( http://osflash.org/documentation/amf/envelopes/remoting ) and any other number will raise error ( http://kb2.adobe.com/cps/407/kb407204.html ) But if SoapUI works fine when you deploy war on other server, we can conclude that this is something to do with the server. Don't think that this will help you but that is what I've found. If you manged to solve your problem , please share that with us. regards nebojsa eviware.com

The KB Adobe article you pointed to above, says:
This is most likely the result of a client sending a non-AMF formatted message (for instance a browser GET or POST request) to the server endpoint.
SoapUI is the client in this case, or am I understanding that wrong? Would you be able to explain?

Thanx.