Gld EAP 7 JMS Run: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * gld Installation * gld Extension Development Smoke Tests =Overview= This...") |
|||
Line 14: | Line 14: | ||
./run | ./run | ||
</pre> | </pre> | ||
The EAP profile must have a "novaordis" queue deployed. | |||
Create a <tt>test.yml</tt> in the current directory, with the [[#Configuration_File|content shown below]]. | Create a <tt>test.yml</tt> in the current directory, with the [[#Configuration_File|content shown below]]. |
Revision as of 00:44, 12 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 file shown below into a test.yml in the current directory.
Procedure
cd $RUNTIME_DIR/jboss-eap-7.0.4/profiles/jms ./run
The EAP profile must have a "novaordis" queue deployed.
Create a test.yml in the current directory, with the content shown below.
gld -c ./test.yml
After the run finishes, the "number-of-entries" for the default cache should be updated according to the cluster configuration and the number of operations.
/host=master/server=n1/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:read-attribute(name=number-of-entries)
Configuration File
service: type: cache key-size: 10 value-size: 1024 implementation: name: jboss-datagrid-7 nodes: - localhost:11222 load-strategy: name: read-then-write-on-miss reuse-value: true load: threads: 1 operations: 10000 output: statistics: file: test.csv