I'm using the barebones default server config for hornet, the only thing I changed is adding a new queue to the jms queues xml file and in the configuration file I changed all references to localhost to my actual server host along with adding the acceptor above. Everything else is default hornet 2.1.2 out of the box.

However you could try different clients to see if the problem is with the client or server, also compare it to a test program that uses the core protocol and see if there is much difference.

When you say "187 seconds to insert 50000 items" I assume you are sending persistent messages and you have the server setup to sync on each message received, and disc write cache is disabled on your disk? (See user manual)

That's actually a very good sync rate. Not many disks can go faster than that. Looks like you've hit your hardware limit. This would be the same whether it's HornetQ, Orackle, MySQL or any other application using your disk.

I will try that today and report back, however could you please answer why when I set durable to false and send non-persistent msgs that disk sync comes into play?

I'm asking a basic question... how can I improve inserts per second for a particular queue using stomp?

Based on my jira configurations I posted, do I have the config files set up correctly? Even if JMS proves to be the same speed with blockondurable set to false I still have the underlying question of how to get better insert performance with stomp. 260 MSGS per second cannot be the top end for writing to memory.