Thanks for the info, and the patience.
I will download Firebug and see what I can see. You will most likely be hearing from me. J chago wrote: > > I have tried your example and it works for me with my new amq.js file and > the one that is in the head. I suspect that their is some component > outside the javascript and servlets that is silently failing for you. > FWIW, I have disabled persistence in my configuration: > > <context-param> > <param-name>org.apache.activemq.brokerURL</param-name> > <param-value>vm://localhost?broker.persistent=false</param-value> > </context-param> > > > The first two connections that you see should be a GET and a POST. > > The POST should will look like this: > http://localhost:8080/webapp/amq > - destination=channel://gnip > - message=gnip > - type=listen > > (Note: the response from the server is an empty string) > > The first GET should have a timeout value of 0 and looks like this: > http://localhost:8080/webapp/amq > - timeout=0 > > Both of these should return very quickly. Then another GET request is made > without a timeout value. The MessageListenerServlet uses a default timeout > of 25 secs. These GET requests are the long polls and are the basis for > the Comet approach to AJAX calls. It works very well with an asynchronous > interface like JMS. > > As for debugging, here are some general approaches I have used. > > #1 - Firebug > Firebug is a developer's plugin for Firefox browser that lets you easily > monitor XmlHttpRequest (AJAX) calls made by the client. It shows you the > message that was sent out and the response returned by the server. It > shows you these in real time so you can see your request sending and > waiting for a response. > > By using this, you can make sure that the client is actually sending the > message. You can also verify that the server responds with a reply; proper > or not. There is also a two connection limit to the server, so this tool > will show you how many outstanding connections there are. > > #2 - Live Debugging > I sometime remote debug or debug an embedded Jetty server by placing > breakpoints in MessageListenerServlet. > > #3 - Debug Logging > I generally turn on full debug output for as many components that I can. > The MessageListenerServlet has debug statements that are useful when faced > with a strange problem. > > Hope it helps. > > Feel free to Skype me if you want to walk thru it in more detail. You will > find me by searching for skype.at.visualxs.dot.com. > > > Zanderfax wrote: >> >> Attached is the logfile with debug info. >> >> I started activemq, then jetty, loaded the web page and sent 2 messages. >> >> I see the connections but there is nothing transfered. >> >> Any ideas? >> >> http://www.nabble.com/file/p12665375/activemq.log activemq.log >> >> chago wrote: >>> >>> http://activemq.apache.org/how-do-i-enable-debug-logging.html >>> >>> >>> Zanderfax wrote: >>>> >>>> I made the changes with no apparent effect. Where would I look for the >>>> debug log or stack trace if they exist? >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Looking-for-Help-ActiveMQ-and-Jetty-tf4379195s2354.html#a12757627 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
