Persistance & Stomp

View: New views
2 Messages — Rating Filter:   Alert me  

Persistance & Stomp

by Tom Samplonius-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


  I saw a message from James in Feb with a question about whether to make persistent messages the default in Stomp.  I'm trying a 4.2 snapshot from Monday, and it appears to not have have this change yet.  Will this change make it into 4.2?  Or the next version?

  Also, I notice that apparently "persistent:true" is a valid header on a SEND command, but http://stomp.codehaus.org/Protocol does not mention this option.  Is there a more up to date version of the protocol spec?

  I've also heard that in activemq, persistence can be forced on, on a queue by queue basis?  How is this done?  I saw a message from brianm to this affect, but no mention of how it is done.  I checked the docs on the <queue> element in the configuration, and there is nothing there.

Tom

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


Re: Persistance & Stomp

by andrewk :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

'persistent' is not in the stomp protocol - at least not yet.
It is a jms/activemq addition over and above the plain stomp standard, and so is documented here:

http://activemq.apache.org/stomp.html
http://stomp.codehaus.org/Stomp+JMS

I never found a good way to do persistence except sending this header, but if someone figures out another that works with stomp, I'm all ears.

-Andrew

Tom Samplonius-2 wrote:
  I saw a message from James in Feb with a question about whether to make persistent messages the default in Stomp.  I'm trying a 4.2 snapshot from Monday, and it appears to not have have this change yet.  Will this change make it into 4.2?  Or the next version?

  Also, I notice that apparently "persistent:true" is a valid header on a SEND command, but http://stomp.codehaus.org/Protocol does not mention this option.  Is there a more up to date version of the protocol spec?

  I've also heard that in activemq, persistence can be forced on, on a queue by queue basis?  How is this done?  I saw a message from brianm to this affect, but no mention of how it is done.  I checked the docs on the <queue> element in the configuration, and there is nothing there.

Tom

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email