You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/01/21 19:24:40 UTC

[jira] [Closed] (AMQ-3009) using ajax client with jquery adapter, activemq not automatically start broadcast data, need refresh first

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

Timothy Bish closed AMQ-3009.
-----------------------------
    Resolution: Unresolved

Recommend using WebSocket connections from the browser now

> using ajax client with jquery adapter, activemq not automatically start broadcast data, need refresh first
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3009
>                 URL: https://issues.apache.org/jira/browse/AMQ-3009
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.4.1
>         Environment: windows 7, windows server 2008, jquery 1.4.3, firefox 3.6.12
>            Reporter: heriyanto binduni
>            Priority: Minor
>
> i'm using jquery adapter as describe here: https://issues.apache.org/activemq/browse/AMQ-1377
> to listening message via browser but activemq session seem not start broadcast data to webpage as soon as we open the page. need to refresh the page first before activemq starting to broadcast message. the same problem not happen if i use the old ways, using prototype and behaviour script. have not try it with prototype adapter. 
> from firebugs i see it send request to server something like this: http://localhost:8081/demo/amq?timeout=2000&d=1288535246706&r=0.7241340907954991, but still no broadcast data until page refresh. any solution for this?
> using the old protype and behaviour script would lead to another bugs, prototype conflict with jquery as reported on this: https://issues.apache.org/activemq/browse/AMQ-2427
> tq



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)