[
https://issues.apache.org/activemq/browse/AMQ-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43485#action_43485
]
Dan Schooler commented on AMQ-1377:
-----------------------------------
The timeout parameter takes milliseconds, so the multiplication by 1000
converts to seconds.
It is not 25000 seconds, but 25000 milliseconds, which is 25 seconds.
The other parameters ('d' and 'r') are just added to make the query string
unique.
IE6 has a bug where it will not refetch the exact query it has seen before over
GET and instead shows you the cached result (regardless of any no-cache
directives from the server).
I'm not sure what your problem is.
Like I said, this has been working fine in my app for nearly 6 months.
You will need to debug your own unique scenario, I suggest using the firebug
plugin, setting breakpoints in the scripts and seeing what is happening.
The only thing that comes to mind is that if you are actually terminating the
Tomcat server, that is a very different thing than a client having intermittent
connectivity. My solution is really just to handle the network cable getting
unplugged or the wifi being flaky, it is not designed to handle a server
restart.
When you restart the server, the session that your client had (and any topic
subscriptions) are probably no longer valid, and so the client may need to make
a new request for the topic..... maybe something like this:
//Un-Listen from topic
org.activemq.Amq.removeListener("yourTopic",
"topic://Your.Topic");
//One second delay to wait for the Un-Listen to happen
setTimeout(function(){
//Re-Listen
org.activemq.Amq.addListener("yourTopic",
"topic://Your.Topic", yourHandler);
}, 1000);
> amq.js should not have a dependency on prototype.js
> ---------------------------------------------------
>
> Key: AMQ-1377
> URL: https://issues.apache.org/activemq/browse/AMQ-1377
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Jim Cook
> Attachments: amq.js, amq.js, amq.js, amq_js.zip
>
>
> amq.js uses a script loading technique to include behavior.js, prototype.js
> and _amq.js. The Behavior library is included only for the purposes of the
> chat client and is only GUI in nature, so that should go. Also, Prototype is
> included for its AJAX functionality, however everyone has their favorite
> javascript library and although I cut my teeth on prototype, I use jQuery
> now. I certainly don't want amq.js to include prototype when I have a
> perfectly good AJAX library already included in jQuery.
> IMHO, amq.js should include only the functionality of client-side
> javascript-enabled JMS. The page author should include her AJAX library of
> choice (prototype, dojo, jquery, mootools, etc.) and an adapter class that
> allows amq.js to use the particular ajax library.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
