Gld EAP 7 JMS Run: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 6: Line 6:
=Overview=
=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|configuration file]] shown below into a <tt>test.yml</tt> in the current directory.
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|configuration files]] shown below into <tt>send.yml</tt> and <tt>receive.ml</tt> in the current directory.


=Procedure=
=Procedure=
Line 15: Line 15:
</pre>
</pre>


The EAP profile must have a "novaordis" queue deployed.
The EAP profile must have a "jms/queue/novaordis" queue bound in JNDI.


Create a <tt>test.yml</tt> in the current directory, with the [[#Configuration_File|content shown below]].
Create a <tt>[[#send.yml|send.yml]]</tt> and <tt>[[#eceive.yml|receive.yml]]</tt> in the current directory, with the [[#Configuration_Files|content shown below]].
 
Send the messages:


<pre>
<pre>
gld -c ./test.yml
gld -c ./send.yml
</pre>
</pre>


<font color=red>
Then receive them:
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.


<pre>
<pre>
/host=master/server=n1/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:read-attribute(name=number-of-entries)
gld -c ./receive.yml
</pre>
</pre>


=Configuration File=
=Configuration Files=


==send.yml==


<pre>
<pre>
service:
service:


   type: cache
   type: jms
   key-size: 10
 
  value-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:
   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: send.csv
</pre>


    name: jboss-datagrid-7
==receive.yml==
    nodes:
 
      - localhost:11222
<pre>
service:
 
  type: jms


   load-strategy:
   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


     name: read-then-write-on-miss
  implementation:
     reuse-value: true
     name: jboss-eap-7-jms
    version: 7.0.4
     jndi-url: localhost:8080 # remoting access to the JNDI server


load:
load:


   threads: 1
   threads: 1
   operations: 10000
   messages: 10000
  message-size: 1024


output:
output:
   statistics:
   statistics:
    file: test.csv
      file: receive.csv
 
</pre>
</pre>
</font>

Latest revision as of 00:46, 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

  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
  message-size: 1024

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
Retrieved from "https://kb.novaordis.com/index.php?title=Gld_EAP_7_JMS_Run&oldid=17039"