forked from imatix/openamq-jms
-
Notifications
You must be signed in to change notification settings - Fork 1
/
readme.txt
107 lines (65 loc) · 2.99 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
OpenAMQ/JMS version 1.0b0
Copyright 2008 iMatix Corporation
For copying conditions, please see the file license.txt included
with this distribution.
Building OpenAMQ/JMS
--------------------
In order to build OpenAMQ/JMS you need:
* Sun J2SE 5.0 JDK, which can be downloaded from http://java.sun.com/
* Apache Ant 1.7.0 or newer, which can be downloaded from
http://ant.apache.org/
To build, please ensure that Ant and your JDK are installed correctly,
and that the JAVA_HOME environment variable, if set, is pointing to the
root directory of the JDK that you wish to build OpenAMQ/JMS with.
Then, run the following:
> ant
This will build OpenAMQ/JMS and test classes, and leave the JAR files in
the dist directory of the distribution.
To install the JAR files into an OpenAMQ IBASE, you can run
> ant install
which will install them into $IBASE/java/lib, if the IBASE environment
variable is set.
For other useful targets, try:
> ant -projecthelp
Running Example Programs
------------------------
Scripts to run the examples are in the bin directory.
The simplest test to ensure everything is working is the "service
request reply" test. This involves one client that is known as a
"service provider" and it listens on a well-known queue for requests.
Another client, known as the "service requester" creates a private
(temporary) response queue, creates a message with the private response
queue set as the "reply to" field and then publishes the message to the
well known service queue. The test allows you to time how long it takes
to send messages and receive the response back. It also allows varying
of the message size.
You must start the service provider first:
On UNIX:
> bin/serviceProvidingClient.sh host:port
On Windows:
> bin\serviceProvidingClient host:port
where host:port is the host and port you are running the broker on.
To run the service requester:
On UNIX:
> bin/serviceRequestingClient.sh host:post <message count> <message size in bytes>
On Windows:
> bin\serviceRequestingClient host:post <message count> <message size in bytes>
After receiving all the messages the client outputs the rate it achieved.
A more realistic example is the "headers test", which tests the
performance of routing messages based on message headers to a
configurable number of clients (e.g. 50). A publisher sends e.g. 10000
messages to each client and waits to receive a message from each client
when it has received all the messages.
You run the listener processes first (repeat for as many listeners as
you like):
On UNIX:
> bin/headersListener.sh -host 127.0.0.1 -port 5672
On Windows:
> bin\headersListener.bat -host 127.0.0.1 -port 5672
Then run the publisher process:
On UNIX:
> bin/headersPublisher.sh -host 10.0.0.1 -port 5672 <message count> <number of listeners>
On Windows:
> bin\headersPublisher.bat -host 10.0.0.1 -port 5672 <message count> <number of listeners>
Note that before starting the publisher you should wait a few seconds to
ensure all the clients are registered with the broker.