[英]Error in Running Multiple Threads with JPOS on JMeter for ISO8583
I am Trying to run My IS08583 Script for Multiple Users using JPOS Plugin.我正在尝试使用 JPOS 插件为多个用户运行我的 IS08583 脚本。 However i could find below Output in the Sampler Result.
但是,我可以在采样器结果中的输出下方找到。 Can anyone suggest what settings needs to be changed in JPOS for running my Script on Multiple users without this Error.
任何人都可以建议需要在 JPOS 中更改哪些设置才能在没有此错误的情况下在多个用户上运行我的脚本。 Currently i am running only 2 Threads, in which one thread gives successful Output and Other gives error as mentioned below..
目前我只运行 2 个线程,其中一个线程给出了成功的输出,其他线程给出了如下所述的错误。
Thread Name: GBM_Transaction Sample Start: 2020-08-24 15:45:13 IST Load time: 1 Connect Time: 0 Latency: 0 Size in bytes: 0 Sent bytes:0 Headers size in bytes: 0 Body size in bytes: 0 Sample Count: 1 Error Count: 1 Data type ("text"|"bin"|""): text Response code: Response message: org.jpos.iso.ISOException: Duplicate key 'jmeter-2d8b3043-send.120000003938777.req' detected线程名称:GBM_Transaction 示例开始:2020-08-24 15:45:13 IST 加载时间:1 连接时间:0 延迟:0 字节大小:0 已发送字节:0 标头大小(字节):0 正文大小(字节):0样本计数:1 错误计数:1 数据类型(“文本”|“bin”|“”):文本 响应代码:响应消息:org.jpos.iso.ISOException:重复键 'jmeter-2d8b3043-send.120000003938777.req '检测到
SampleResult fields: ContentType: DataEncoding: null SampleResult 字段: ContentType: DataEncoding: null
When sending and receiving multiple request and response messages over the same socket connection, jPOS needs to match responses (as they may come in in a different order) to requests.当通过同一个套接字连接发送和接收多个请求和响应消息时,jPOS 需要将响应(因为它们可能以不同的顺序出现)与请求匹配。 It does that based on keys it generates for each message, eg
jmeter-2d8b3043-send.120000003938777.req
.它根据为每条消息生成的密钥来执行此操作,例如
jmeter-2d8b3043-send.120000003938777.req
。
The part 120000003938777
is generated (by default) from the fields MTI (1200), DE41 and DE11 (00003 and 938777 presumably).部分
120000003938777
是从字段 MTI (1200)、DE41 和 DE11(大概是 00003 和 938777)生成的(默认情况下)。
If your script does not vary those fields eg randomly, as suggested, the same key will be generated for multiple messages and you get that error when jPOS detects the duplicate key.如果您的脚本没有改变这些字段,例如随机,如建议的那样,将为多条消息生成相同的密钥,并且当 jPOS 检测到重复的密钥时,您会收到该错误。 Obviously, this makes it impossible to unambiguously match responses to requests.
显然,这使得无法明确地将响应与请求匹配。
What you can do is:你可以做的是:
The JMeter functions ${__time()}
and ${__RandomString()}
are quite useful for that. JMeter 函数
${__time()}
和${__RandomString()}
对此非常有用。
Refer also https://github.com/jpos/jPOS/blob/master/doc/src/asciidoc/ch08/qmux.adoc#mti-mapping-and-default-key .另请参阅https://github.com/jpos/jPOS/blob/master/doc/src/asciidoc/ch08/qmux.adoc#mti-mapping-and-default-key 。
Disclaimer: I am the author of the JMeter ISO8583 plugin.免责声明:我是 JMeter ISO8583 插件的作者。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.