Using STOMP with Wildfly

[jesstei]

Hello,

I am trying to connect a python message sender to my JMS system. Therefore I added the following lines to the standard-full.xml file of the Wildfly application server:

<acceptor name="stomp-acceptor">

    <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

    <param key="protocols" value="STOMP"/>

    <param key="port" value="61613"/>

</acceptor>

<jms-queue name="EventQueue">

    <entry name="java:/jms/queue/EventQueue"/>

</jms-queue>

Further I added an Management User and an Application User to Wildfly.

To test the configuration of my EventQueue, I developed a simple MDB:

@MessageDriven(

        activationConfig = { @ActivationConfigProperty(

                propertyName = "destination", propertyValue = "java:/jms/queue/EventQueue"), @ActivationConfigProperty(

                propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(

                propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge")

        },

        mappedName = "java:/jms/queue/EventQueue")

public class EventMessageDrivenBean implements MessageListener {

    public EventMessageDrivenBean() {

    }

    /**

     * @see MessageListener#onMessage(Message)

     */

    public void onMessage(Message message) {

        try {

            if (message instanceof TextMessage){

                TextMessage tm = (TextMessage) message;

                System.out.println("Received message on EMDB is ==========> " + tm.getText());

            }

            else{

                System.out.println("Received unexpected message type: "+message.getClass().getName());

            }

        } catch (JMSException e) {

            System.out.println("Caught exception in onMessage(): "+e.getMessage());

            e.printStackTrace();

        }

    }

}

Besided this MDB, I created a Servlet. Using this servlet I am able to send messages to my JMS Queue.

As I am not familar with Python I decided to implement a STOMP messsage producer in java first to get an idea. Therefore I took the sample of hornetQ and removed the part, that describes receiving and consuming a STOMP message.

public class StompProducer2 {

        private static final String END_OF_FRAME = "\u0000";

           public static void main(final String[] args) throws Exception

           {

              Connection connection = null;

              InitialContext initialContext = null;

              try

              {

                 // Step 1. Create a TCP socket to connect to the Stomp port

                 Socket socket = new Socket("localhost", 61613);

                 // Step 2. Send a CONNECT frame to connect to the server

                 String connectFrame = "CONNECT\n" +

                    "accept-version:1.2\n" +

                    "host:localhost\n" +

                    "login:login\n" +

                    "passcode:password\n" +

                    "request-id:1\n" +

                    "\n" +

                    END_OF_FRAME;

                 sendFrame(socket, connectFrame);

                 System.out.println("Connected: "+socket.isConnected());

                 String response = receiveFrame(socket);

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

                 // Step 3. Send a SEND frame (a Stomp message) to the

                 // jms.queue.exampleQueue address with a text body

                 String text = "Hello World from Stomp 1.2 !";

                 String message = "SEND\n" +

                    "destination:jms.queue.EventQueue\n" +

                    "\n" +

                    text +

                    END_OF_FRAME;

                 sendFrame(socket, message);

                 System.out.println("Sent Stomp message: " + text);

                 // Step 4. Send a DISCONNECT frame to disconnect from the server

                 String disconnectFrame = "DISCONNECT\n" +

                    "\n" +

                    END_OF_FRAME;

                 sendFrame(socket, disconnectFrame);

                 // Step 5. Slose the TCP socket

                 socket.close();

              }

              finally

              {

                 // Step 11. Be sure to close our JMS resources!

                 if (initialContext != null)

                 {

                    initialContext.close();

                 }

                 if (connection != null)

                 {

                    connection.close();

                 }

              }

           }

           private static void sendFrame(Socket socket, String data) throws Exception

           {

              byte[] bytes = data.getBytes("UTF-8");

              OutputStream outputStream = socket.getOutputStream();

              for (int i = 0; i < bytes.length; i++)

              {

                 outputStream.write(bytes[i]);

              }

              outputStream.flush();

           }

           private static String receiveFrame(Socket socket) throws Exception

           {

              InputStream inputStream = socket.getInputStream();

              byte[] buffer = new byte[1024];

              int size = inputStream.read(buffer);

              byte[] data = new byte[size];

              System.arraycopy(buffer, 0, data, 0, size);

              String frame = new String(data, "UTF-8");

              return frame;

           }

}

Within the server log wildfly reports:

[org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP

But also Wildfly reports:

[org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version unknown localhost:61613

[org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

In contrast to my servlet, the STOMP message Producer prints out:

Connected: true

response: CONNECTED

version:1.2

session:746882306

server:HornetQ/2.4.1.Final (Fast Hornet, 124) HornetQ Messaging Engine

response-id:1

and terminates without an exception. On a windows based system Wildfly does not display anything. Exact the same source code and configuration changes within Kubuntu produces at least a warning of Wildfly:

09:07:28,687 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222067: Connection failure has been detected: HQ119014: Did not receive data from null. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

09:07:28,688 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session badca3e9-4d72-11e4-8027-3395d56bbe5c

09:07:28,689 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session badca3e9-4d72-11e4-8027-3395d56bbe5c

Any ideas what I should change in order to send STOMP messages?

Thanks in advance for your help.

[gaohoward]

Can you add a 'catch (Throwable)' before the finally block and print out the stack? This will help debugging the issue.

Howard

[jesstei]

Hallo Yong,

thanks for your help.

I added the follwoing lines of source code to the STOMP producer client:

// Step 5. Slose the TCP socket

         socket.close();

      }

      catch(Throwable t ){

          t.printStackTrace();

      }

      finally

      {

         // Step 11. Be sure to close our JMS resources!

         if (initialContext != null)

         {

            initialContext.close();

         }

         if (connection != null)

         {

            connection.close();

         }

      }

   }

Unfortunatly no StackTrace is shown. The Producer client terminates as usual.

WIldfly also does not print a message on windows. On kubuntu the aforementioned warnings appear.

I though that it might be problem of a  firewall. So I turned it off completly on my windows machine, but it does not change anything.

[gaohoward]

looks like the message has been sent successfully. I'd suggest you use admin console (or cli tool) to check if there is any messages at queue EventQueue. Then to make sure your MDB is working, send a message to the queue using standard JMS client and see what happens.

[jesstei]

Hello Yong,

I connected to my EventQueue via CLI and found out that the messages produced by my small servlet are sent.

[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=EventQueue/:read-attribute(name=messages-added,include-defaults=true)

{

    "outcome" => "success",

    "result" => 2500L

}

However, I was not able to get helloworld-jms from quickstarts (quickstart/helloworld-jms at master · wildfly/quickstart · GitHub) working. Everytime I execute the HelloWorldJMSClient.java it terminates with an exception:

Okt 08, 2014 4:09:44 AM org.xnio.Xnio <clinit>

INFO: XNIO version 3.2.2.Final

Okt 08, 2014 4:09:44 AM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.2.2.Final

Okt 08, 2014 4:09:44 AM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version (unknown)

Okt 08, 2014 4:09:44 AM jms.JMSClient main

INFORMATION: Attempting to acquire connection factory "jms/RemoteConnectionFactory"

Okt 08, 2014 4:09:45 AM jms.JMSClient main

INFORMATION: Found connection factory "jms/RemoteConnectionFactory" in JNDI

Okt 08, 2014 4:09:45 AM jms.JMSClient main

INFORMATION: Attempting to acquire destination "jms.queue.EventQueue"

Okt 08, 2014 4:09:45 AM jms.JMSClient main

FATAL: jms.queue.EventQueue -- service jboss.naming.context.java.jboss.exported."jms.queue.EventQueue"

javax.naming.NameNotFoundException: jms.queue.EventQueue -- service jboss.naming.context.java.jboss.exported."jms.queue.EventQueue"

    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)

    at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)

    at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)

Whereas WIdlfly reports:

14:21:54,724 INFO  [org.jboss.as.naming] (default task-30) JBAS011806: Channel end notification received, closing channel Channel ID 06ef917d (inbound) of Remoting connection 0c630a99 to /127.0.0.1:61925

[gaohoward]

From cli result I can see the stomp client works. The problem is with your MDB perhaps. Regarding the example error, I think it's probably a config issue. How did you run the client? did you use configure-jms.cli ?

[jesstei]

Hello Yong,

maybe I wrote a bit confusing. I built  three different use-cases. 1) A servlet sending messages to my MDB, 2) a Java STOMP Client sending messages to my MDB and 3) a Java JMS Client. Besides this I run these three different use -cases on a windows and kubuntu machine.

Test result 1):

The servlets sents the messages successfully and my MDB is able to print out a string on the wildfly console. Works fine for windows and kubuntu.

The CLI returns:

[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=EventQueue/:read-attribute(name=messages-added,include-defaults=true)

{

    "outcome" => "success",

    "result" => 2500L

}

Test result 2):

The Java STOMP client tries to connects to my MDB. The client terminates without an exception on both operating systems.

The client prints out:

STOMP Client output:

Connected: true

response: CONNECTED

version:1.2

session:573308848

server:HornetQ/2.4.1.Final (Fast Hornet, 124) HornetQ Messaging Engine

response-id:1

The main difference between both operating systems is that wildfly on kubuntu reports a warning :

09:07:28,687 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222067: Connection failure has been detected: HQ119014: Did not receive data from null. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

09:07:28,688 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session badca3e9-4d72-11e4-8027-3395d56bbe5c

09:07:28,689 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session badca3e9-4d72-11e4-8027-3395d56bbe5c

Wildfly on windows does not report anything.

The CLI 0 messages after execution of STOMP client in kubuntu.:

[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=EventQueue/:read-attribute(name=messages-added,include-defaults=true)

{

    "outcome" => "success",

    "result" => 0L

}

Test result 3):

The Java JMS Client from the HelloworldJMSExample of Wildfly is not running on both operating systems.

In the operating system kubuntu:

executing configure-jms.cli reports:

mir@ubuntu:/opt/wildfly-8.1.0.Final/bin$ ./jboss-cli.sh --connect --file=/home/mir/wildfly_examples/quickstart-master/helloworld-jms/configure-jms.cli

The batch executed successfully

Executing the JMSClient.java prints out:

Okt 08, 2014 7:42:33 AM org.xnio.Xnio <clinit>

INFO: XNIO version 3.2.2.Final

Okt 08, 2014 7:42:33 AM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.2.2.Final

Okt 08, 2014 7:42:33 AM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version (unknown)

Okt 08, 2014 7:42:33 AM jms.JMSClient main

INFORMATION: Attempting to acquire connection factory "jms/RemoteConnectionFactory"

Okt 08, 2014 7:42:34 AM jms.JMSClient main

INFORMATION: Found connection factory "jms/RemoteConnectionFactory" in JNDI

Okt 08, 2014 7:42:34 AM jms.JMSClient main

INFORMATION: Attempting to acquire destination "jms/queue/test"

Okt 08, 2014 7:42:34 AM jms.JMSClient main

INFORMATION: Found destination "jms/queue/test" in JNDI

WIldfily reports:

07:42:35,464 WARNING [io.netty.channel.DefaultChannelPipeline] (default I/O-2) An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.netty.handler.codec.DecoderException: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:257)

    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:139)

    at org.hornetq.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:110)

    at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338)

    at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324)

    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785)

    at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)

    at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)

    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

Caused by: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199)

    at org.hornetq.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:139)

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:226)

    ... 11 more

07:43:05,415 WARNING [io.netty.channel.DefaultChannelPipeline] (default I/O-2) An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.netty.handler.codec.DecoderException: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:257)

    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:139)

    at org.hornetq.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:110)

    at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338)

    at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324)

    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785)

    at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)

    at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)

    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

Caused by: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199)

    at org.hornetq.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:139)

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:226)

    ... 11 more

07:43:05,526 WARNING [io.netty.channel.DefaultChannelPipeline] (default I/O-2) An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.netty.handler.codec.DecoderException: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:257)

    at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:190)

    at io.netty.channel.DefaultChannelHandlerContext.invokeChannelInactive(DefaultChannelHandlerContext.java:238)

    at io.netty.channel.DefaultChannelHandlerContext.fireChannelInactive(DefaultChannelHandlerContext.java:224)

    at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:767)

    at io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:560)

    at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:560) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

    at org.xnio.nio.WorkerThread.run(WorkerThread.java:462) [xnio-nio-3.2.2.Final.jar:3.2.2.Final]

Caused by: java.lang.UnsupportedOperationException: direct buffer

    at io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199)

    at org.hornetq.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:139)

    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:226)

    ... 7 more

07:43:05,564 INFO  [org.jboss.as.naming] (default task-8) JBAS011806: Channel end notification received, closing channel Channel ID 72169277 (inbound) of Remoting connection 13c07552 to /127.0.0.1:44077

But CLI reports:

[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=EventQueue/:read-attribute(name=messages-added,include-defaults=true)

{

    "outcome" => "success",

    "result" => 0L

}

Within windows:

I fail to connect to CLI:

H:\wildfly-8.1.0.Final\bin>jboss-cli.bat --connect controller-127.0.0.1:9999

org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

I had to change the ports for the management console due to an error caused by the NVIDIA driver (http://www.newinstance.org/drupal/?q=node/1).

But can not connect to CLI anymore as described in this post: https://developer.jboss.org/message/853280

[gaohoward]

Regarding java stomp client:

System.out.println("Sent Stomp message: " + text);

I see you have the above code, did you see it printed out to console? Any 'ERROR' message in wildfly server log?

Regarding the example:

looks to me you have different version of netty/hornetq between your client and wildfly server. I'd suggest you check out the classpath of your client.

[jesstei]

Hello Yong,

System.out.println("Sent Stomp message: " + text); was printed on my console within Eclipse during execution of the STOMP Client on both operating systems:

Connected: true

response: CONNECTED

version:1.2

session:-1249611988

server:HornetQ/2.4.1.Final (Fast Hornet, 124) HornetQ Messaging Engine

response-id:1

In kubuntu the server.log file prints out:

2014-10-08 10:03:38,786 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final "Kenny" sta$

2014-10-08 10:03:38,793 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties:

        awt.toolkit = sun.awt.X11.XToolkit

        file.encoding = UTF-8

        file.encoding.pkg = sun.io

        file.separator = /

        java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment

        java.awt.headless = true

        java.awt.printerjob = sun.print.PSPrinterJob

        java.class.path = /opt/wildfly-8.1.0.Final/jboss-modules.jar

        java.class.version = 52.0

        java.endorsed.dirs = /usr/lib/jvm/java-8-oracle/jre/lib/endorsed

        java.ext.dirs = /usr/lib/jvm/java-8-oracle/jre/lib/ext:/usr/java/packages/lib/ext

        java.home = /usr/lib/jvm/java-8-oracle/jre

        java.io.tmpdir = /tmp

        java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

        java.net.preferIPv4Stack = true

        java.runtime.name = Java(TM) SE Runtime Environment

        java.runtime.version = 1.8.0_20-b26

        java.specification.name = Java Platform API Specification

        java.specification.vendor = Oracle Corporation

        java.specification.version = 1.8

        java.util.logging.manager = org.jboss.logmanager.LogManager

        java.vendor = Oracle Corporation

        java.vendor.url = http://java.oracle.com/

        java.vendor.url.bug = http://bugreport.sun.com/bugreport/

        java.version = 1.8.0_20

        java.vm.info = mixed mode

        java.vm.name = Java HotSpot(TM) 64-Bit Server VM

        java.vm.specification.name = Java Virtual Machine Specification

        java.vm.specification.vendor = Oracle Corporation

        java.vm.specification.version = 1.8

....

2014-10-08 10:03:43,945 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221012: Using AIO Journal

2014-10-08 10:03:44,273 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final

2014-10-08 10:03:44,558 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE

2014-10-08 10:03:44,593 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP

2014-10-08 10:03:44,622 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP

2014-10-08 10:03:44,726 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

2014-10-08 10:03:44,727 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

2014-10-08 10:03:45,350 INFO  [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor

2014-10-08 10:03:45,350 INFO  [org.jboss.messaging] (MSC service thread 1-4) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor

2014-10-08 10:03:45,586 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version unknown localhost:61613

2014-10-08 10:03:45,592 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

2014-10-08 10:03:45,593 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [a47c35fc-4d55-11e4-8de6-db312495ecf2]

2014-10-08 10:03:45,606 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.DLQ

2014-10-08 10:03:45,619 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ

2014-10-08 10:03:45,755 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

2014-10-08 10:03:45,755 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

2014-10-08 10:03:45,757 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue

2014-10-08 10:03:45,757 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.testQueue

2014-10-08 10:03:45,758 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name queue/test

2014-10-08 10:03:45,758 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

2014-10-08 10:03:45,759 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

2014-10-08 10:03:45,759 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.EventQueue

2014-10-08 10:03:45,759 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queues/EventQueue

2014-10-08 10:03:45,760 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/jms/queue/EventQueue

2014-10-08 10:03:45,761 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.topic.EventTopic

2014-10-08 10:03:45,764 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/jms/topic/EventTopic

2014-10-08 10:03:46,098 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA

2014-10-08 10:03:46,176 INFO  [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started

2014-10-08 10:03:46,177 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra

2014-10-08 10:03:46,180 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

2014-10-08 10:03:46,181 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

2014-10-08 10:03:46,347 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'EventMessageDrivenBean' with 'hornetq-ra.rar' resource adapter

2014-10-08 10:03:46,858 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /JMSTest

2014-10-08 10:03:46,910 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "JMSTest.war" (runtime-name : "JMSTest.war")

2014-10-08 10:03:46,971 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

2014-10-08 10:03:46,972 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

2014-10-08 10:03:46,973 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 9842ms - Started 303 of 356 services (105 services are lazy, passive or on-demand)

2014-10-08 10:05:01,672 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222067: Connection failure has been detected: HQ119014: Did not receive data from null. It is likely the client has exited or crashed witho$

2014-10-08 10:05:01,672 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session 19145704-4f0d-11e4-abd1-2bb59113b42a

2014-10-08 10:05:01,673 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session 19145704-4f0d-11e4-abd1-2bb59113b42a

In windows the server log file looks like:

2014-10-08 21:27:00,435 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.1.0.Final "Kenny" starting

2014-10-08 21:27:00,442 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:

    awt.toolkit = sun.awt.windows.WToolkit

    file.encoding = Cp1252

    file.encoding.pkg = sun.io

    file.separator = \

    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

    java.awt.headless = true

    java.awt.printerjob = sun.awt.windows.WPrinterJob

    java.class.path = H:\wildfly-8.1.0.Final\jboss-modules.jar

    java.class.version = 52.0

    java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_05\jre\lib\endorsed

    java.ext.dirs = C:\Program Files\Java\jdk1.8.0_05\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

    java.home = C:\Program Files\Java\jdk1.8.0_05\jre

    java.io.tmpdir = C:\Users\Jimena\AppData\Local\Temp\

    java.library.path = C:\Program Files\Java\jdk1.8.0_05\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native;C:\ProgramData\Oracle\Java\javapath;

    java.net.preferIPv4Stack = true

    java.runtime.name = Java(TM) SE Runtime Environment

    java.runtime.version = 1.8.0_05-b13

    java.specification.name = Java Platform API Specification

    java.specification.vendor = Oracle Corporation

    java.specification.version = 1.8

    java.util.logging.manager = org.jboss.logmanager.LogManager

    java.vendor = Oracle Corporation

    java.vendor.url = http://java.oracle.com/

    java.vendor.url.bug = http://bugreport.sun.com/bugreport/

    java.version = 1.8.0_05

    java.vm.info = mixed mode

    java.vm.name = Java HotSpot(TM) 64-Bit Server VM

    java.vm.specification.name = Java Virtual Machine Specification

    java.vm.specification.vendor = Oracle Corporation

    java.vm.specification.version = 1.8

    java.vm.vendor = Oracle Corporation

    java.vm.version = 25.5-b02

    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

    javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

    javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

    javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

    javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

    javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

    javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

    javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

    javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

    javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

    jboss.bind.address = localhost

    jboss.bind.address.management = localhost

    jboss.home.dir = H:\wildfly-8.1.0.Final

.....

2014-10-08 21:27:04,723 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

2014-10-08 21:27:04,757 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2

2014-10-08 21:27:04,922 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path H:\wildfly-8.1.0.Final/welcome-content

2014-10-08 21:27:04,960 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017525: Started server default-server.

2014-10-08 21:27:04,999 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017531: Host default-host starting

2014-10-08 21:27:05,055 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017519: Undertow HTTP listener default listening on localhost/127.0.0.1:8080

2014-10-08 21:27:05,239 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-13) JBAS015012: Started FileSystemDeploymentService for directory H:\wildfly-8.1.0.Final\standalone\deployments

2014-10-08 21:27:05,246 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "JMSTest.war" (runtime-name: "JMSTest.war")

2014-10-08 21:27:05,276 WARN  [jacorb.codeset] (MSC service thread 1-7) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

2014-10-08 21:27:05,311 WARN  [org.jboss.as.messaging] (MSC service thread 1-16) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

2014-10-08 21:27:05,376 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

2014-10-08 21:27:05,381 INFO  [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016330: CORBA ORB Service started

2014-10-08 21:27:05,401 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=H:\wildfly-8.1.0.Final\standalone\data\messagingjournal,bindingsDirectory=H:\wildfly-8.1.0.Final\standalone\data\messagingbindings,largeMessagesDirectory=H:\wildfly-8.1.0.Final\standalone\data\messaginglargemessages,pagingDirectory=H:\wildfly-8.1.0.Final\standalone\data\messagingpaging)

2014-10-08 21:27:05,410 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock

2014-10-08 21:27:05,464 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal

2014-10-08 21:27:05,599 INFO  [org.jboss.as.jacorb] (MSC service thread 1-15) JBAS016328: CORBA Naming Service started

2014-10-08 21:27:05,756 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE

2014-10-08 21:27:05,770 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final

2014-10-08 21:27:05,926 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP

2014-10-08 21:27:05,931 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP

2014-10-08 21:27:06,004 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

2014-10-08 21:27:06,005 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

2014-10-08 21:27:06,581 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221019: Deleting unreferenced message id=83.751.862.855 from the journal

2014-10-08 21:27:06,590 INFO  [org.jboss.messaging] (MSC service thread 1-11) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor

2014-10-08 21:27:06,591 INFO  [org.jboss.messaging] (MSC service thread 1-4) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor

2014-10-08 21:27:06,907 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version unknown localhost:61613

2014-10-08 21:27:06,911 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

2014-10-08 21:27:06,911 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [dc49f412-2c4f-11e4-9912-dfbb079ab869]

2014-10-08 21:27:06,950 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

2014-10-08 21:27:06,952 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

2014-10-08 21:27:06,959 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue

2014-10-08 21:27:06,959 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DLQ

2014-10-08 21:27:06,960 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ

2014-10-08 21:27:06,960 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.queue.EventQueue

2014-10-08 21:27:06,961 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/jms/queue/EventQueue

2014-10-08 21:27:06,961 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.topic.EventTopic

2014-10-08 21:27:06,966 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/topic/EventTopic

2014-10-08 21:27:06,966 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

2014-10-08 21:27:07,004 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA

2014-10-08 21:27:07,050 INFO  [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started

2014-10-08 21:27:07,051 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra

2014-10-08 21:27:07,378 INFO  [org.jboss.as.messaging] (MSC service thread 1-15) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

2014-10-08 21:27:07,378 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-7) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

2014-10-08 21:27:07,430 INFO  [org.jboss.as.ejb3] (MSC service thread 1-11) JBAS014142: Started message driven bean 'EventMessageDrivenBean' with 'hornetq-ra.rar' resource adapter

2014-10-08 21:27:07,431 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) JBAS014142: Started message driven bean 'IncidentMessageDrivenBean' with 'hornetq-ra.rar' resource adapter

2014-10-08 21:27:07,639 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-12) JBAS017534: Registered web context: /JMSTest

2014-10-08 21:27:07,671 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "JMSTest.war" (runtime-name : "JMSTest.war")

2014-10-08 21:27:07,734 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9999/management

2014-10-08 21:27:07,734 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9999

2014-10-08 21:27:07,734 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 8565ms - Started 313 of 366 services (104 services are lazy, passive or on-demand)

Where do I check netty/hornetq version between your client and wildfly server?

I am using Eclipse Luna and JBoss Tools to start Wildfly. If there where any dependencies I included the wildfly lib to the project build path. So I am not aware of any version differences. 

Thanks a lot for your help  :-)

[gaohoward]

Connected: true

response: CONNECTED

version:1.2

session:-1249611988

server:HornetQ/2.4.1.Final (Fast Hornet, 124) HornetQ Messaging Engine

response-id:1

The above is not likely the print out I mentioned. It's a response to the 'CONNECT' frame.

About the version you can add couple of lines in you client. For HornetQ try:

System.out.println(VersionLoader.getVersion());

For netty there seems to be a util:

System.out.println(Version.ID);

[jesstei]

Hello Yong,

I added the following lines to my STOMP Client:

org.hornetq.core.version.Version[] v = VersionLoader.getClientVersions();

for (int i = 0; i < v.length; i++){

    System.out.println(v[i].getFullVersion());

}

Map<String, Version> netty= Version.identify();

for(Map.Entry<String, Version> e : netty.entrySet()){

    System.out.println("Version:" +e.getKey() +" :: "+ e.getValue());

}

System.out.println("VersionLoader: "+VersionLoader.getVersion().getFullVersion());

It results to the following output:

2.4.1.Final (Fast Hornet, 124)

2.4.1.Final (Fast Hornet, 123)

2.4.1.Final (Fast Hornet, 122)

Version:netty-buffer :: netty-buffer-4.0.15.Final.2875152

Version:netty-codec :: netty-codec-4.0.15.Final.2875152

Version:netty-codec-http :: netty-codec-http-4.0.15.Final.2875152

Version:netty-codec-socks :: netty-codec-socks-4.0.15.Final.2875152

Version:netty-common :: netty-common-4.0.15.Final.2875152

Version:netty-handler :: netty-handler-4.0.15.Final.2875152

Version:netty-transport :: netty-transport-4.0.15.Final.2875152

Version:netty-transport-rxtx :: netty-transport-rxtx-4.0.15.Final.2875152

Version:netty-transport-sctp :: netty-transport-sctp-4.0.15.Final.2875152

Version:netty-transport-udt :: netty-transport-udt-4.0.15.Final.2875152

VersionLoader: 2.4.1.Final (Fast Hornet, 124)

I hope this is what you were asking for :-), as Version.ID was not available.

Kind regards,

jesstei

[gaohoward]

Sorry I didn't make it clear, my question is, can you confirm that

System.out.println("Sent Stomp message: " + text); was printed on you console? It should be like

"Sent Stomp message: ...... (whatever the text value is)"

not 'CONNECTED ....' which should be the response to the CONNECT request.

About the version info, I'm referring to your 'helloword-jms" example, just want to make sure your client and server has match versions of hornetq and netty.

[jesstei]

Hello Yong,

the output of String response = receiveFrame(socket); within the console of my STOMP client is:

Connected: true

response: CONNECTED

version:1.2

session:1118283057

server:HornetQ/2.4.1.Final (Fast Hornet, 124) HornetQ Messaging Engine

response-id:1

and the output of   System.out.println("Sent Stomp message: " + text); only appears in my STOMP client java application console. There is no output on the wildfly server console.

My helloworld-jms client reports:

2.4.1.Final (Fast Hornet, 124)

2.4.1.Final (Fast Hornet, 123)

2.4.1.Final (Fast Hornet, 122)

Version:netty-buffer :: netty-buffer-4.0.15.Final.2875152

Version:netty-codec :: netty-codec-4.0.15.Final.2875152

Version:netty-codec-http :: netty-codec-http-4.0.15.Final.2875152

Version:netty-codec-socks :: netty-codec-socks-4.0.15.Final.2875152

Version:netty-common :: netty-common-4.0.15.Final.2875152

Version:netty-handler :: netty-handler-4.0.15.Final.2875152

Version:netty-transport :: netty-transport-4.0.15.Final.2875152

Version:netty-transport-rxtx :: netty-transport-rxtx-4.0.15.Final.2875152

Version:netty-transport-sctp :: netty-transport-sctp-4.0.15.Final.2875152

Version:netty-transport-udt :: netty-transport-udt-4.0.15.Final.2875152

[gaohoward]

Can you attach your standard-full.xml file here so I can give it a try?

[gaohoward]

anyway I tried to add your stomp configuration to the latest wildfly build (from master) and I can see your Stomp java client works. From the client I see the following output:

Connected: true

response: CONNECTED

version:1.2

session:532734563

server:HornetQ/2.4.4.Final (2.4.4.Final, 124) HornetQ Messaging Engine

response-id:1

Sent Stomp message: Hello World from Stomp 1.2 !

After that using jboss cli tool to examine the EventQueue I got:

[standalone@localhost:9990 jms-queue=EventQueue] :read-attribute(name=messages-added,include-defaults=true)

{

    "outcome" => "success",

    "result" => 1L

}

This shows that the message has been successfully sent to the server.