Hi Kuppe, In many cases we take the performance hit of unmarshalling the properties like when we need to evaluate against a selector. In any case, I don't think unmarshalling the properties should that expensive. Also, if your producer is in the same JVM as the broker, then chances are the properties have not been marshalled at all and you not take a hit at all.
On 7/28/06, Kuppe <[EMAIL PROTECTED]> wrote:
Hi James, another question regarding this point. I have now implemented my own MessageEvictionStrategy and plugged it in using the instructions from the post below. For now i am using 4.0.1, so am only implementing the eviceMessage method. My question is, how can i add business context information that will allow me to evict messages based on my eviction policy? I initially thought that i would be able to add a simple property to the header of the JMSMessage which could be easily accessed from within the evictMessage method. It seems though that the properties of the message are now stored in the marshalledProperties field. Of course for performance reasons I definitely do not want to be unmarshalling all properties in order to evaluate the business context value. Is there any other field of the message that better suits this stage of the processing? Thanks in advance. m. -- View this message in context: http://www.nabble.com/LastImage-style-topic-tf1710311.html#a5534326 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
