ISO 8583消息在Jmeter中给出超时错误

发布于 2025-02-03 01:46:50 字数 172 浏览 5 评论 0原文

我正在使用Jmeter进行ISO消息脚本进行负载测试。我已经使用了ISO 8583采样器和连接配置。所有按字段的数据字段都正确映射,包括MTI(字段0)。但是问题是,该请求不是从Jmeter发送到服务器的。它只是不断提出超时问题,我没有反对它。我已经看到了该请求并验证了实施者本人的格式,他说格式是正确的。谁能帮助您打扰这个问题?

I'm scripting for ISO Messages using JMeter to do Load Testing. I have used the ISO 8583 Sampler and connection configuration. All the data field by field is mapped correctly including the MTI (Field 0). But the issue is that the request is not being sent to the server from the JMeter. It just keep on giving the timeout issue and I'm getting no response against it. I've seen the request and validated it format from the implementer himself and he says that the format is correct. Can anyone help to trouble shoot this issue?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

瞳孔里扚悲伤 2025-02-10 01:46:51

查看我为什么要超时?文档部分? ,,,,

我为什么要超时?

响应超时的三个常见原因是:

  1. 采样器未收到任何响应。
  2. 采样器确实会收到响应,但未能打开它。
  3. 采样器确实会收到响应并解开响应,但无法匹配请求。

调试日志应包含类似于以下内容的通道输出:

  2022-02-22 12:34:56,789调试ncbjiq2 :( channel/hostname:post)[send] out:0800 000001
2022-02-22 12:34:56,987 DEBUG NCBJIQ2 :(频道/主机名:post)[接收]
 

如果仅存在第一个日志线,则不会收到响应(上面的情况1)。该请求可能是错误形成的,并将远程系统丢弃,因此检查其日志/痕迹可能会有所帮助。仔细检查包装器配置文件!这定义了在(之后)之前如何打包请求(或响应)。

如果存在两条线,则实际上已经收到了响应(上面的情况2和3)。

如果第二个日志线包含如下的错误,则响应未能解开包装(上面的情况2)。仔细检查包装器配置文件!

  2022-02-22 12:34:56,987错误ncbjiq2 :( channel/hostname:post)[recection] org.jpos.iso.someclassnamehere:问题解开字段...
 

如果第二个日志行不包含错误,则插件可能找不到匹配请求(上面的情况3)。仔细检查MUX设置!这些定义用于匹配的MTI值和消息字段,并且默认设置可能不起作用。

为了提高jmeter的记录词性将下一行添加到 log4j2.xml 文件:

<Logger name="nz.co.breakpoint.jmeter.iso8583" level="debug" />

jmeter重新启动以拿起更改。

另外,请确保您可以从Jmeter使用a ” noreflow noreferrer“> telnet客户端或同等学历。

Check out Why am I getting timeouts? documentation section,

Why am I getting timeouts?

The three common reasons for response timeouts are:

  1. The sampler does not receive any response.
  2. The sampler does receive a response but fails to unpack it.
  3. The sampler does receive a response and unpacks it but no request can be matched.

The debug log should contain Channel output similar to the following:

2022-02-22 12:34:56,789 DEBUG n.c.b.j.i.Q2: (channel/HOSTNAME:POST) [send] Out: 0800 000001
2022-02-22 12:34:56,987 DEBUG n.c.b.j.i.Q2: (channel/HOSTNAME:POST) [receive]  In: 0810 000001

If only the first log line is present, no response was received (case 1 above). It is likely that the request is incorrectly formed and the remote system discarded it, so checking its logs/traces may be helpful. Double-check the Packager Configuration file! This defines how a request is packed (or response is unpacked) before (after) it goes over the wire.

If both lines are present, a response was in fact received (cases 2 and 3 above).

If the second log line instead contains an error like the following, then the response failed to unpack (case 2 above). Double-check the Packager Configuration file!

2022-02-22 12:34:56,987 ERROR n.c.b.j.i.Q2: (channel/HOSTNAME:POST) [receive] org.jpos.iso.SOMECLASSNAMEHERE: Problem unpacking field ...

If the second log line contains no error then it is likely that the plugin did not find a matching request (case 3 above). Double-check the Mux Settings! These define MTI values and message fields that are used for matching, and the default settings may not work.

In order to increase JMeter's logging verbosity for the ISO 8583 sampler add the next line to log4j2.xml file:

<Logger name="nz.co.breakpoint.jmeter.iso8583" level="debug" />

JMeter restart will be required to pick up the change.

Also make sure that you can reach the target server host/port from the machine where JMeter is running using a telnet client or equivalent.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文