Bug 62909 - JMS: Normalise JNDI settings
Summary: JMS: Normalise JNDI settings
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.0
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2018-11-15 00:44 UTC by Andrew Burton
Modified: 2018-12-04 07:47 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Burton 2018-11-15 00:44:36 UTC
JMS Publisher, JMS Subscriber and JMS Point to Point share common JNDI fields that could be moved to a panel class.

+- JNDI Properties -------------------------------------------------+
| [] Use jndi.properties                                            |
| ______ Initial Context Factory                                    |
| ______ Provider URL                                               |
| [] Use Authorisation    User [           ]  Password [         ]  |
|                                                                   |

The JMSSampler currently uses a JMeter property JMSSampler.useSecurity.properties for authentication - this would require a change on the JMSSampler to use the above settings, or the GUI code could hide those fields only for the JMSSampler.

This is part of https://bz.apache.org/bugzilla/show_bug.cgi?id=61830

Some questions:
* What should we do with the JNDI Properties table, displayed in the JMS Point to Point sampler? Is it only applicable for this sampler?
* There's a reference to the library jmeter-jms-skip-jndi, which has a single v0.0.1 release in Oct 2012 (https://mvnrepository.com/artifact/com.elega9t/jmeter-jms-skip-jndi) in the documentation - is this still relevant? The docs have little to say on when/where this is used
Comment 1 Andrew Burton 2018-11-15 00:45:23 UTC
I'm working on a patch for this, but guidance on the questions would be appreciated.