Looking into Tibco EFTL Java client library:
package com.tibco.eftl;
import com.tibco.eftl.impl.WebSocketConnection;
import java.security.KeyStore;
import java.util.Properties;
public class EFTL {
public static final String PROPERTY_USERNAME = "user"; // <------ this is the correct property name
public static final String PROPERTY_PASSWORD = "password";
public static final String PROPERTY_TIMEOUT = "timeout";
public static final String PROPERTY_CLIENT_ID = "client_id";
public static final String PROPERTY_NOTIFICATION_TOKEN = "notification_token";
public static final String PROPERTY_AUTO_RECONNECT_ATTEMPTS = "auto_reconnect_attempts";
public static final String PROPERTY_AUTO_RECONNECT_MAX_DELAY = "auto_reconnect_max_delay";
public static final String PROPERTY_DURABLE_TYPE = "type";
public static final String PROPERTY_DURABLE_KEY = "key";
public static final String DURABLE_TYPE_SHARED = "shared";
public static final String DURABLE_TYPE_LAST_VALUE = "last-value";
private static KeyStore trustStore;
So my expectation is that you need to change your username
property to user
and your scenario should start working normally.
Just in case check out Building a JMS Testing Plan - Apache JMeter article for more information on message queues load testing with JMeter