That sounds fine. The web console and web demos's usually have a
broker embedded inside them that you can talk to via TCP so there's no
absolute reason to disable vm:// transport in the web demo/console and
explicitly use TCP.
On 2/26/07, pandi79 <[EMAIL PROTECTED]> wrote:
Finally my Jms progra
Finally my Jms program is able to receve messages from the queue.. I'ave
updated the web.xml
lThe paragraph ine in web.xml
vm://localhost
is replaced by
tcp://localhost:61616
1. started web demo example by the coomand mvn jetty6:run
2. started the activemq broker by the command 'activemq'
Thanks for your response.
Once I sent the message through html page (webdemo example), I tried the
link http://localhost:8080/activemq-web-demo/queueBrowse/myqueue?view=xml to
browse all the messages. I am able to see (it is browse option) all the
messaages which I posted.
Then I ran my jms pro
