Open maciejfranek opened 10 years ago
download your jars ,a new exception : ERROR - jmeter.protocol.amf.proxy.AmfProxy: Exception when processing sample java.lang.ArrayIndexOutOfBoundsException: -1 at ... ... at jmeter.protocol.amf.util.AmfXmlConverter.convertAmfMessageToXml(AmfXmlConverter.java:173) at jmeter.protocol.amf.util.AmfXmlConverter.convertAmfMessageToXml(AmfXmlConverter.java:140) ... ... at jmeter.protocol.amf.proxy.AmfProxy.run(AmfProxy.java:224) INFO- jmeter.samplers.SampleEvent: List of sample_variables: []
sample can't get amf's xml request
Tried to record amf requests using AMF proxy server, but I have encountered following exceptions:
Despite exceptions, amf requests were recorded, but content of a request was incomplete: After investigation, it was noted that blazeds can`t find object with type '-65'. This is weird as AMF has type identificators between 0 and 17 (see http://grepcode.com/file/repository.springsource.com/com.adobe.flex/com.springsource.flex.messaging/3.2.0.3978/flex/messaging/io/amf/AmfTypes.java). Further findings indicated that there is a bug in a proxy recorder. Conversion from amf to xml might be incorrect as encoded bytes are used to it - https://github.com/steeltomato/jmeter-amf/blob/master/src/protocol/amf/org/apache/jmeter/protocol/amf/proxy/AmfRequestHdr.java#L463 postData is encoded earlier - https://github.com/steeltomato/jmeter-amf/blob/master/src/protocol/amf/org/apache/jmeter/protocol/amf/proxy/AmfRequestHdr.java#L395 causing wrong type identifier (in my case '10' was changed to '-65') Replacing: To: Fixed this issue