wildfly8-CR1: How to configure http/servlet transport with HornetQ and how to set client's context properties?

[ybxiang.china]

Dear all,

     Is there an example of configuring http/servlet transport with HornetQ in wildfly 8 CR1?

     I spent several days on wildfly 8 CR1 since it's released.

I have studied

hornetq-2.4.0.Final\examples\jms\http-transport\readme.html

and

hornetq-2.4.0.Final/examples/jms/http-transport/readme.html

But, there has been <http-connector name="http" socket-binding="http"/>, and do NOT know if I should configure

	<connector name="netty-connector">
	<factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
	<param key="http-enabled" value="true"/>
	<param key="port" value="80"/>
	</connector>

or connection factory (as the examples in hornetq 2.4.0) in standalone.xml?

How the client-side code look like???

should I use "jnp://localhost:1099" as java.naming.provider.url? Does this mean I should add 1099 into linux firewall filter???

I googled many articles, but nothing is useful!

Please help me! I think this example is VERY important to many of us.

Any tip is highly appreciated!!!

[jmesnil]

The http-connector has been introduced in WildFly 8.0.0.CR1 to upgrade from a HTTP request to HornetQ own JMS binary protocol.

By default, the standalone-full.xml configuration is shipped with a JMS ConnectionFactory that uses such a http-connector.

The client code is simply using the http-remoting://localhost:8080 URL to connect to the JNDI provider and lookup the /jms/HTTPConnectionFactory connection factory:

        InitialContext initialContext = null;

        try

        {

            // Step 1. Create an initial context to perform the JNDI lookup.

            final Properties env = new Properties();

            env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

            env.put(Context.PROVIDER_URL, "http-remoting://localhost:8080");

            env.put(Context.SECURITY_PRINCIPAL, "guest");

            env.put(Context.SECURITY_CREDENTIALS, "password");

            initialContext = new InitialContext(env);

            ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/jms/HTTPConnectionFactory");

            try (JMSContext context = cf.createContext("guest", "password")) {

                TemporaryQueue tempQueue = context.createTemporaryQueue();

                context.createProducer().send(tempQueue, "hello");

                JMSConsumer consumer = context.createConsumer(tempQueue);

                String response = consumer.receiveBody(String.class, 2000);

                System.out.println("response = " + response);

            }

        } finally {

            if (initialContext != null)

            {

                initialContext.close();

            }

       }

[ybxiang.china]

Your explanation is very clear!

The demo code is what I want!

Thank you VERY much! You are good man!

[ybxiang.china]

Dear Jeff Mesnil,

        Have you tried to set security domain for <subsystem xmlns="urn:jboss:domain:messaging:2.0"> in wildfly8???

        I can not make it work, and posted the question here: Security domain does NOT work for <subsystem xmlns="urn:jboss:domain:messaging:2.0">!!!.

        I spent several days on reading many articles (mainly from jboss.org and stackoverflow.com), it seems only you know the answer.

        Would you please help me?

        Any tip is highly appreciated!

[ybxiang.china]

Solved:

add one line in env:

env.put("jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false");

Detail: Security domain does NOT work for <subsystem xmlns="urn:jboss:domain:messaging:2.0">!!!