All of the JMS* fields are stored outside of the marshalled properties, so I'm thinking JMSType may be your best choice.
Regards, Hiram On 7/28/06, Kuppe <[EMAIL PROTECTED]> wrote:
I am really trying to keep the processing cost to a minimum really. We have a large number of small messages being processed (say hundreds or more per second) and as we have many slow clients i expect the evictMessage method to be called quite frequently - again perhaps a hundred or more times per second... Each time it is called, it would be necessary to unmarshal the properties for each message considered for eviction... I can imaging that this is not the most effective way of using cpu resource:) As i am consolidating many sources of data in my broker, the sources are typically not in the same vm as the producers, therefore the properties are still marshalled and really should be. The question is whether there is any natural place for a single String property to be placed outside of the marshalled properties that may then be used for eviction. -- View this message in context: http://www.nabble.com/LastImage-style-topic-tf1710311.html#a5535046 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
