You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a test plan to publish/subscribe using JMS Publisher and JMS Subscriber.
Before JMS Publisher is called I have e JSR223 Preprocessor that creates a jndi.properties file with a dynamic name containing the thread number.
When running the script I see that, even if JMS Publisher uses the different JNDI files, it always publishes to the queue from the first file. Somehow it seems this is cached.
Result of execution:
JMS Publisher:
jndi.properties file:
On the other hand, the JMS Subscriber properly tries to consume messages from the proper queue when loading the same jndi file.
Thank you
JMeter Version
5.6.2
Java Version
java 11.0.16.1
OS Version
Microsoft Windows 10.0.19044.4291
The text was updated successfully, but these errors were encountered:
Expected behavior
No response
Actual behavior
No response
Steps to reproduce the problem
I have a test plan to publish/subscribe using JMS Publisher and JMS Subscriber.
Before JMS Publisher is called I have e JSR223 Preprocessor that creates a jndi.properties file with a dynamic name containing the thread number.
When running the script I see that, even if JMS Publisher uses the different JNDI files, it always publishes to the queue from the first file. Somehow it seems this is cached.
Result of execution:
JMS Publisher:
jndi.properties file:
On the other hand, the JMS Subscriber properly tries to consume messages from the proper queue when loading the same jndi file.
Thank you
JMeter Version
5.6.2
Java Version
java 11.0.16.1
OS Version
Microsoft Windows 10.0.19044.4291
The text was updated successfully, but these errors were encountered: