Gld EAP 7 JMS Run: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 71: | Line 71: | ||
type: jms | type: jms | ||
load-strategy: | load-strategy: | ||
Line 91: | Line 90: | ||
threads: 1 | threads: 1 | ||
messages: 10000 | messages: 10000 | ||
message-size: 1024 | |||
output: | output: |
Revision as of 00:45, 18 February 2017
Internal
Overview
This page contains the configuration of a simple gld run that validates the installation and interoperability with EAP 7 JMS. You will need to copy an paste the content of the configuration files shown below into send.yml and receive.ml in the current directory.
Procedure
cd $RUNTIME_DIR/jboss-eap-7.0.4/profiles/jms ./run
The EAP profile must have a "jms/queue/novaordis" queue bound in JNDI.
Create a send.yml and receive.yml in the current directory, with the content shown below.
Send the messages:
gld -c ./send.yml
Then receive them:
gld -c ./receive.yml
Configuration Files
send.yml
service: type: jms message-size: 1024 load-strategy: name: send queue: jms/queue/novaordis connection-factory: jms/RemoteConnectionFactory connection-policy: connection-per-run session-policy: session-per-operation user: jmsuser password: jmsuser123 implementation: name: jboss-eap-7-jms version: 7.0.4 jndi-url: localhost:8080 # remoting access to the JNDI server load: threads: 1 messages: 10000 output: statistics: file: send.csv
receive.yml
service: type: jms load-strategy: name: receive queue: jms/queue/novaordis connection-factory: jms/RemoteConnectionFactory connection-policy: connection-per-run session-policy: session-per-operation user: jmsuser password: jmsuser123 implementation: name: jboss-eap-7-jms version: 7.0.4 jndi-url: localhost:8080 # remoting access to the JNDI server load: threads: 1 messages: 10000 message-size: 1024 output: statistics: file: receive.csv