Jmeter – WebLogic JMSQ Load Testing


A business usecase has been implemented on WebLogic JMS-Q where client publish or push message in to JMS-Q.


Client or Publisher need to be replace with JMeter.

Components requried before implementation

Before developing a solution we need to be ready with some of the components and details which are needed for implementation.

Weblogic Client Jar Files (Wljmsclient.jar,wlthint3client.jar) – You can get these files from the installation of Weblogic. You can ask either from developers or you can download Weblogic and install on your own to obtains.

Initial Context Factory Name(weblogic.jndi.WLInitialContextFactory) – This information will be provided by developers. Most of the item, above value is used as default. However better to check with your developement team for the same.

Provider Url (t3://servername:port) – Endpoint which need to be used to push the message.
Note: Weblogic JMS has been implemented over T3 Protocal. T3 protocol which is built as wrapper to TCP. Weblogic’s implementation RMI specification uses a proprietary wire-protocol known as T3 (Similar to Microsoft WCF protocol).Please read more about T3 protocal.

ConnectionFactory: (example: mnJanalyserConnectionFactory) – A connection Factory string will be obtained from developers.

Destination: (Example: DirectSaleQueue ) – A Queue name string will be obtained from developers.


Authorization: Username, Password (depend on implementation)

Message template for successful process – A message template which need to be pushed in to Queue.

Weblogic’s implementation RMI specification uses a proprietary wire-protocol known as T3 (Similar to Microsoft WCF protocol)

Implementation Guide

Once we have all the information in hand, first move the *.jar (Wljmsclient.jar,wlthint3client.jar) to /lib/ext directory.

Step 2
Open Jmeter
Add JMS Publisher to Threadgroup.

Entet all the details as show in the picture.


Now we are ready to go and start the testrun.

Note: Mostly Message queue implemented in asynchronous process. You may not recieve any acknolwedge or response from Server,but WebLoginClient jar generates MessageID before sending the message to Server. You should collaborate with server team to verify the message has been successfully delivered.