Yes, the application requires things to work across default http/https connection. We cannot require the users of our application to punch holes on their firewall to enable tcp communication over the default activeMQ port.
Dejan Bosanac wrote: > > Hi, > > is there any particular reason you prefer the http transport over the > default tcp one? Http transport has many drawbacks and if you have Java > clients, tcp should be the way to go. > > Cheers > -- > Dejan Bosanac > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Wed, Jan 14, 2009 at 4:47 AM, msatyadi <msaty...@yahoo.com> wrote: > >> >> Hello, >> >> My application consists of a server component and a thick java client >> component. >> I have a requirement that the client should be able to receive JMS >> messages >> from the server. >> So my question is: >> >> 1. How do I configure activeMQ on the server side so that it uses tomcat >> instead of using jetty web server. Is there any configuration that needs >> to >> be done on the tomcat side as well? I've been searching around the >> activeMQ >> site, and it seems like there's no documentation on this. >> >> 2. On the client side, how will the code on the client side receive the >> events? Will activeMQ http transfer take care of the polling of events? >> >> Any pointers would be greatly appreciated. >> >> Thank you! >> >> -- >> View this message in context: >> http://www.nabble.com/HTTP-Transport-Configuration-with-Tomcat-tp21449577p21449577.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > ----- > Dejan Bosanac > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > -- View this message in context: http://www.nabble.com/HTTP-Transport-Configuration-with-Tomcat-tp21449577p21468625.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
