| commit | c46a2a15f4d0035e4c36ebb674e0c27f9e597e14 | [log] [tgz] |
|---|---|---|
| author | Hiram R. Chirino <chirino@apache.org> | Fri Feb 04 18:02:19 2011 +0000 |
| committer | Hiram R. Chirino <chirino@apache.org> | Fri Feb 04 18:02:19 2011 +0000 |
| tree | 9f09428e83b4a30bd6a35f0745396d2fcf98f4ad | |
| parent | 2bd5e510612877f605ba39fd256be3ff38b53d2f [diff] |
Simplified OSGi integration by just using bundle fragments. git-svn-id: https://svn.apache.org/repos/asf/activemq/activemq-apollo/trunk@1067244 13f79535-47bb-0310-9956-ffa450edef68
Apollo is a forked and stripped down Apache ActiveMQ message broker. It is focused on simplicity, stability and scalability.
Prerequisites:
Then run:
mvn install -Pdownload
if you're building it for the first time, or just
mvn install
if you already initialized the repo
We are still working on creating a binary distribution. Once that's created we will update these instructions to work off that distribution. Until then, they will be based on a built source distribution.
A broker with a web based admin interface will be started by using the the Scala REPL console.
$ cd apollo-web $ mvn -o scala:console ... [output ommitted for brevity] scala> val main = org.apache.activemq.apollo.web.Main ... [output ommitted for brevity] scala> main run ... [output ommitted for brevity] Web interface available at: http://localhost:8080/
You can point your web browser at http://localhost:8080/ to explore the management structure of the broker. Additional status objects will become visible once there are connected client which cause connections and destination management objects to be created.
A stomp client will be started by using the the Scala repl console.
$ cd apollo-stomp $ mvn -o scala:console ... [output ommitted for brevity] scala> val client = org.apache.activemq.apollo.stomp.perf.StompLoadClient client: org.apache.activemq.apollo.stomp.perf.StompLoadClient.type = -------------------------------------- StompLoadClient Properties -------------------------------------- uri = stomp://127.0.0.1:61613 destinationType = queue destinationCount = 1 sampleInterval = 5000 --- Producer Properties --- producers = 1 messageSize = 1024 persistent = false syncSend = false useContentLength = true producerSleep = 0 headers = List() --- Consumer Properties --- consumers = 1 consumerSleep = 0 ack = auto selector = null
The above creates a client variable which allows you to customize all the displayed properties. Those properties control how the client applies load to the STOMP broker. You could change the client configuration so that it uses messages with 20 byte contents and send and receive on topics instead of queues:
scala> client.messageSize = 20 scala> client.destinationType = "topic"
Once you are happy with the client configuration, you just run it and wait for it to report back the producer and consumer throughput rates.
scala> client.run ======================= Press ENTER to shutdown ======================= Producer rate: 155,783.906 per second, total: 778,960 Consumer rate: 154,345.969 per second, total: 771,770 Producer rate: 165,831.141 per second, total: 1,608,210 Consumer rate: 165,798.734 per second, total: 1,600,858