activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2394) Ajax does not consume the first message in Firefox
Date Tue, 10 Aug 2010 13:26:57 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hadrian Zbarcea updated AMQ-2394:
---------------------------------

    Fix Version/s: 5.4.1
                       (was: 5.4.0)

> Ajax does not consume the first message in Firefox
> --------------------------------------------------
>
>                 Key: AMQ-2394
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2394
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.4.1
>
>         Attachments: bug.zip
>
>
> We're trying to use the Jetty continuations MessageListenerService as
> an endpoint for an AJAX app where people get near-realtime updates in
> their browser, where each end user subscribes to their own queue of
> notifications.  (If the user were to leave and then come back, they'd
> get another, brand new queue (with a new, unique name - not sure if
> this is relevant.)
> The plumbing seems to be working pretty well and it's quite a flashy
> bit of work, but we're seeing strange behavior with the very first
> message placed on the queue just disappearing (the
> MessageListenerServlet shows it consumes them but they never come down
> the pipe to the browser over HTTP - or maybe they're being sent to a
> different client or something?).  Sometimes none of the subsequent
> messages ever show up on the client, other times everything works as
> expected.
> We tried unsuccessfully to figure out the cause of the problem,
> because it's sporadic, but it seems to be at least somewhat related to
> http sessions (a cleanly wiped firefox will work great - but then
> repeating the test in the same firefox usually doesn't work) and for
> whatever reason safari seems to work OK whether its cache has been
> cleared or not.  Since there's a difference between web browsers the
> obvious implication is that something is messed up client-side but
> we're having a real hard time figuring out what that could be - no JS
> exceptions or errors, etc, so we've tried messing with all kinds of
> caching to no avail.  This is activemq 5.2.0.  I attached two files,
> one is the debug output from a working session (with safari) and one
> from a non-working session with firefox - the events seem to all show
> up in the logs OK, but for whatever reason they don't make it to the
> browser.
> ------
> A simple case to demonstrate, consisting of an html page
> with JS that subscribes to a random queue, the _amq js file, and
> prototype.js.
> Refreshing the page (and therefore subscribing to a new random queue)
> does not seem to work in firefox, but does work in safari.  any ideas
> why that is?
> To run the demo, unzip the attached zip file into the /demo directory
> of the activemq project, and then hit http://localhost:8161/demo/bug/
> in firefox/safari - add things to the queue from the activemq admin
> console.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message