hornetq

Is that possible to run HornetQ (JBoss JMS implementation) on Tomcat? The HornetQ documentation is all about JBoss AS or standalone scenarios... Update: This is from HornetQ feature list: "HornetQ is architected as a set of Plain Old Java Objects, it can therefore be run in JBoss Microcontainer, Spring, Google Guice or embedded in any third party product and instantiated directly". So I would be glad to to know how the Web Application (WAR) running on plain Tomcat can embed HornetQ? Tomcat is the same as standalone, you just have Tomcat running in a JVM and all you need to do is put the proper

I'm trying to write a build for my project where I'm trying to replace autobuild, and I need to proper use FIND_JNI. I could make a simple build but it's not properly finding jni.h And I need to find a proper way (without a hack) to define the Java include as this needs to be portable to other users. The following code works for me. In your root CMakeLists.txt file add: find_package(JNI) if (JNI_FOUND) message (STATUS "JNI_INCLUDE_DIRS=${JNI_INCLUDE_DIRS}") message (STATUS "JNI_LIBRARIES=${JNI_LIBRARIES}") endif() 来源： https://stackoverflow.com/questions/7715804/how-to-use-find-jni-on-cmake

I would appreciate some general pointers and opinions regarding which of the two messaging systems is easier to manage has less gotchas or magic stuff one needs to know and avoid has less overal dependencies is simple to work with. Clebert Suconic easier to manage hornetQ has a clear API for management and it's very easy to use. has less gotchas or magic stuff one needs to know and avoid hornetQ was made for the embedded case. It is very, very easy to integrate it in your code. As a matter of fact you can do it with less than 10 lines of code. has less overall dependencies Everything on

I read the hornetQ documentation, confused a lot. Can someone give an exact example to create a JMS topic in hornetQ. I mean the xml configurations in hornetq-jms.xml and hornetq-configuration.xml . assume we have a topic named top and 2 subscribers named: sub1 , sub2 . what I get is that we should define two queues(one for each subscribers) and bind them to an address which is the topic name actually, but how the subscriber would know they should connect to which one?(They only know the topic name) I think you are confused by the way HornetQ handles topics internaly in contrast to the way the

In application based on HornetQ engine I intend to create multiple Producers and Consumers. I have learned, that I should reuse resources as much as possible thanks to this page . Does that mean, that for my application I should crate one and exactly one ConnectionFactory, one Connection, one Session and then (using this Session object) creating as many Producers/Consumers as I want? That shouldn't be hard, but I'm not sure if this is the proper approach. The best rule of thumb for minimum resource usage is to use the fewest constructs as possible while remaining thread safe. Accordingly:

In my client application, I create several consumers, but they can't concurrently process the queue. Always, only a single consumer processes the queue messages. I don't know why. Hashtable<String, String> env = new Hashtable<String, String>(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); env.put(Context.PROVIDER_URL, "192.168.1.111:1099"); InitialContext ctx = new InitialContext(env); ConnectionFactory cf = (ConnectionFactory) ctx.lookup("/ConnectionFactory"); Queue downQueue =

I am using JBoss-6.0.0 AS which by default comes with HornetQ-2.1.2 version but this version of HornetQ has many Iteration related bugs which are now resolved in HornetQ-2.2.5 version which by default comes with JBoss 7 AS. I can't switch to JBoss 7 AS because I am already using many other services specific to JBoss 6 AS and it would be very risky for us to switch to JBoss 7 AS as of now. Is there anyway by which I can upgrade HornetQ version in JBoss 6 AS ? I tried with standalone HornetQ-2.2.5 by running it as different process, but with that JBoss JMX Console is not available. Any