We finally solved this. When using Firefox a specific flag has to be set on the XMLHttpRequest object when it is invoked in order to send the cookies. See https://developer.mozilla.org/en/http_access_control#Requests_with_credentials.
2011/5/4 Jordi Fernández <jordi.fernan...@esilog.com>: > Scenario: > > We have a webapp under domain http://www.mydomainA.com. ActiveMQ is > under domain http://www.mydomainB.com with the jetty cross-origin > filter active. User agent is firefox 3.6. > > The browser makes a request to the webapp under mydomainA and gets the > html with the amq js libraries. The js makes ajax requests to the > ActiveMQ server under mydomainB to create a topic. So far so good, the > cross-origin filter is working fine, the topic is correctly created. > But when there is a message for this topic we see in the activeMQ > console and logs that the consumer (firefox ajax comet connection) is > removed and the message is obviously not delivered. The log we see in > activeMQ (DEBUG mode on) is: > > localhost removing consumer: ID-... for destination: > topic://my.topic.3392 | > org.apache.activemq.broker.region.AbstractRegion | VMTransport: > vm://localhost#9 > > This same scenario works correctly when activeMQ is under mydomainA > and no cross-origin technique is necessary. > > Any ideas? > > Thanks in advance. >
