1 2 Previous Next 21 Replies Latest reply: May 3, 2012 7:47 AM by Raul Martinez Go to original post RSS
      • 15. Re: PHP client is unable to connect to HornetQ instance via STOMP
        Yong Hao Gao Master

        For your info, here is the telnet output on my machine: (2.2.14)

         

        howard@howard-ThinkPad-W510$ telnet localhost 61613

        Trying ::1...

        Trying 127.0.0.1...

        Connected to localhost.

        Escape character is '^]'.

        CONNECT

        login: guest

        passcode: guest

        request-id: 1

         

        ^@

        CONNECTED

        session:1377590487

        • 16. Re: PHP client is unable to connect to HornetQ instance via STOMP
          Raul Martinez Newbie

          Hi Howard,

           

          I tried using PECL stomp as well as the library published by Hiram Chrinino and his team.

           

          I also tried running hornet on non-VM environment.

           

                Instance #3:

                         Mac OS X Lion 10.7.3

                         java version "1.6.0_31"

                        Java(TM)  SE Runtime Environment (build 1.6.0_31-b04-415-11M3646)

                        Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)

           

          If his is a network issue, I'm not sure why Apache Apollo which I also set to run on port 61613 is able to acknowledge the frame that's being sent.

           

          I will try again later when I get home. Thanks for the continued assistance

          • 17. Re: PHP client is unable to connect to HornetQ instance via STOMP
            Raul Martinez Newbie

            Using a real machine CentOS 5.5 (Final) Linux 2.6.18-194.32.1.el5 #1 SMP  - I get the right acknowledge ment but I get the following message, too bad I can't run HornetQ on vbox instance...

             

             

            However this time, trying to send a message to "jms.queue.test" returns the following - Address jms.queue.test has not been deployed  

             

            And following is the stack trace from he console

            HornetQException[errorCode=106 message=Address jms.queue.test has not been deployed]

                    at org.hornetq.core.protocol.stomp.StompProtocolManager.validateDestination(StompProtocolManager.java:611)

                    at org.hornetq.core.protocol.stomp.StompProtocolManager.onSend(StompProtocolManager.java:566)

                    at org.hornetq.core.protocol.stomp.StompProtocolManager.handleBuffer(StompProtocolManager.java:211)

                    at org.hornetq.core.protocol.stomp.StompConnection.bufferReceived(StompConnection.java:292)

                    at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:533)

                    at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73)

                    at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100)

                    at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372)

                    at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:367)

                    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)

                    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)

                    at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:90)

                    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)

                    at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)

                    at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181)

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

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

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

             

            • 18. Re: PHP client is unable to connect to HornetQ instance via STOMP
              Andy Taylor Master

              have you configured the queue?

              • 19. Re: PHP client is unable to connect to HornetQ instance via STOMP
                Yong Hao Gao Master

                you need to deploy a 'test' queue.

                 

                I didn't have a virtual machine installed but I assume if you can run it on a non-virtual system, you can run it on a virual box too.

                I'd suggest you run a tcp tool (like wireshark) to moniter the traffic and see if you can find anything wrong.

                 

                Howard

                • 20. Re: PHP client is unable to connect to HornetQ instance via STOMP
                  Raul Martinez Newbie

                  Hello Andy,

                  I will have to read the documentation on this first. Apologies. I'm just excited to make hornetq work.

                  • 21. Re: PHP client is unable to connect to HornetQ instance via STOMP
                    Raul Martinez Newbie

                    @Howard,

                     

                    Okay, I'll read about it. Thank you!

                     

                    Yes, looks like I need to use wireshark to see what's going on with my hornetq instance on vbox. Thanks

                    1 2 Previous Next