On 15 Nov 2009, at 19:46, hackingbear wrote:
Hi,
I have BrokerFilter that tries to set message property filter in the
broker
filter (so to prevent malice clients from setting bad property.)
However, I
tried to set the properties in the send(), preProcessDispatch(),
messageDelivered() met
Hi,
To prevent client for idling too long and occupying the connection, is it
possible to force the client to disconnect from the broker (e.g. through
BrokerFilter)? Similar to session timeout in a HTTP server.
Thanks
--
View this message in context:
http://old.nabble.com/How-to-force-client
Hi,
I have BrokerFilter that tries to set message property filter in the broker
filter (so to prevent malice clients from setting bad property.) However, I
tried to set the properties in the send(), preProcessDispatch(),
messageDelivered() methods, but none of the properties are passed to the
con
Well... I figure I just need to change the selector value in string form
using the setSelector() instead of fooling around with this additional
predicate.
hackingbear wrote:
>
> OK, I got it to use v5 OpenWire, but the exact problem occurs in v5 as
> well.
>
> What can I do? (Looks like I can
After start the activemq server, I tried to run the jmsappender example comes
with activemq version 5.3. The program hangs, below is the debug info:
C:\apache\apache-activemq-5.3.0>cd example
C:\apache\apache-activemq-5.3.0\example>ant log4j-jms
Buildfile: build.xml
init:
compile:
log4j-jms: