Okay, from what I can tell, when using the ra activation spec driven consumer
construction, the ConsumerInfo options where getting lost.
Upon removing the errant 'this.' and rebuilding the activemq-core module,
things are now working for me.
snippet from org.apache.activemq.ActiveMQConnection.java:
public ConnectionConsumer createConnectionConsumer(Destination
destination, String messageSelector, ServerSessionPool sessionPool, int
maxMessages, boolean noLocal) throws JMSException {
checkClosedOrFailed();
ensureConnectionInfoSent();
ConsumerId consumerId = createConsumerId();
ConsumerInfo info = new ConsumerInfo(consumerId);
info.setDestination(ActiveMQMessageTransformation.transformDestination(destination));
info.setSelector(messageSelector);
info.setPrefetchSize(maxMessages);
info.setNoLocal(noLocal);
info.setDispatchAsync(dispatchAsync);
// Allows the options on the destination to configure the
consumerInfo
if( info.getDestination().getOptions()!=null ) {
HashMap options = new
HashMap(info.getDestination().getOptions());
// IntrospectionSupport.setProperties(-->this.info<--, options,
"consumer.");
//JE 07.02.01 removed the 'this' from info. seems to fix the honoring of
consumer.exclusive option for a jencks jcaconnectior managed consumer
IntrospectionSupport.setProperties(info, options, "consumer.");
}
return new ActiveMQConnectionConsumer(this, sessionPool, info);
}
--
View this message in context:
http://www.nabble.com/How-can-I-configure-an-%22Exclusive-Consumer%22-queue-with-a-Jencks-JCAConnector--tf3159712.html#a8770428
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
