Gld EAP 7 JMS Run: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 41: Line 41:


   load-strategy:
   load-strategy:
     name: send
     name: receive
     queue: jms/queue/novaordis
     queue: jms/queue/novaordis
     connection-factory: jms/RemoteConnectionFactory
     connection-factory: jms/RemoteConnectionFactory
Line 52: Line 52:
     name: jboss-eap-7-jms
     name: jboss-eap-7-jms
     version: 7.0.4
     version: 7.0.4
    jndi-url: localhost:8080 # remoting access to the JNDI server
load:
  threads: 1
  messages: 10000
output:
  statistics:
      file: test.csv
</pre>


==receive.yml==


    # 'classpath' is optional; if specified, it takes precedence
<pre>
    # over the libraries we ship with. if 'classpath' is missing,
service:
    # or the JAR(s) cannot be loaded, we will use the shipped
    # libraries


    # classpath: ${JDG_HOME}/client/activemq.jar
  type: jms
  message-size: 1024


     #
  load-strategy:
     # implementation-specific configuration
    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
     jndi-url: localhost:8080 # remoting access to the JNDI server


Line 74: Line 93:
output:
output:
   statistics:
   statistics:
       file: /Users/ovidiu/tmp/test.csv
       file: test.csv
</pre>
</pre>
==receive.yml==

Revision as of 00:50, 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 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 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 Files

send.yml

service:

  type: jms
  message-size: 1024

  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

output:
  statistics:
      file: test.csv

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