ActiveMQ 5.2 : Unable to Move Messages Between Queues

2009-04-08 Thread MaenXe
Hi guys(and gals), I've been having this problem now for almost 2 months now, and I'm really at a loss. I have Security setup on my broker using the simple Authentication and Authorizations examples found in the Security wiki. When I try to move a message from one Queue to another, it fails.

Re: AMQ 5.2: Unable to Move Messages out of a DLQ.

2009-02-26 Thread MaenXe
It's been a week, and no love :-( anyone want to bump with me?? M@ MaenXe wrote: > > Hi all. I'm getting an unexpected error when working with messages in a > DLQ using the jetty Web Console. After resolving the issue client side > that caused a message to be placed in

AMQ 5.2: Unable to Move Messages out of a DLQ.

2009-02-19 Thread MaenXe
Hi all. I'm getting an unexpected error when working with messages in a DLQ using the jetty Web Console. After resolving the issue client side that caused a message to be placed into a DLQ, we'd like to move the message back to the originating Queue for normal processing. The error I'm seeing i

Re: 5.2, Problems Deleting a Queue

2009-01-27 Thread MaenXe
Can I bump my own thread? It seems there are other users who have this issue, but there doesn't seem to be a lot of interest in fixing it. Is this a bug? M@ MaenXe wrote: > > I have a couple of Queues that I am unable to completely get rid of. If I > delete the Queue either

Re: 5.2, Problems Deleting a Queue

2009-01-12 Thread MaenXe
ving the queue's with there are still attached consumers? > > Regards > Tim. > > On Mon, 2009-01-12 at 17:07 -0800, MaenXe wrote: >> Can anyone in this Forum help me out? I would really like to know how to >> properly delete these Queues, or find a worka

Re: 5.2, Problems Deleting a Queue

2009-01-12 Thread MaenXe
Can anyone in this Forum help me out? I would really like to know how to properly delete these Queues, or find a workaround for this bug. M@ MaenXe wrote: > > I have a couple of Queues that I am unable to completely get rid of. If I > delete the Queue either from JMX(using remove

5.2, Problems Deleting a Queue

2009-01-07 Thread MaenXe
I have a couple of Queues that I am unable to completely get rid of. If I delete the Queue either from JMX(using removeQueue) or from the Web Console the Queue will reappear after I restart the Broker. Also, we have Security implemented to block the lazy creation of Queues. This Queue was creat

Re: Unable to Stop ActiveMQ Broker from activemq-admin script

2009-01-06 Thread MaenXe
tches. > > Cheers > -- > Dejan Bosanac > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Tue, Jan 6, 2009 at 4:20 AM, MaenXe wrote: > >> >> I r

Unable to Stop ActiveMQ Broker from activemq-admin script

2009-01-05 Thread MaenXe
I recently tried to password protect the JMX Connector using the instructions here: http://activemq.apache.org/jmx.html#JMX-PasswordProtectingtheJMXConnector Now when I try to stop the broker using "activemq-admin stop" I get the following error: Error: Exception thrown by the agent : java.rmi.s

Re: Error setting up Network of Brokers in 5.2.0

2008-12-23 Thread MaenXe
alf the .... M@ MaenXe wrote: > > Upon further investigation, I think this may be related to > https://issues.apache.org/activemq/browse/AMQ-1489 AMQ-1489 . If I > specify a multicast IP for the discoveryURI it works perfectly, just not a > name. > > M@ > > > MaenXe

Re: NPE: java.net.UnknownHostException after installing 5.2, same config as 5.1

2008-12-23 Thread MaenXe
; The required change is of the form: > > - > + > > > 2008/12/18 MaenXe : >> >> Anyone else having this same issue? We have 4 different environments >> with 4 >> different broker networks setup, we can't use the same multicast name for

Re: Error setting up Network of Brokers in 5.2.0

2008-12-19 Thread MaenXe
Upon further investigation, I think this may be related to https://issues.apache.org/activemq/browse/AMQ-1489 AMQ-1489 . If I specify a multicast IP for the discoveryURI it works perfectly, just not a name. M@ MaenXe wrote: > > I'm trying to setup a multiple networks of br

Error setting up Network of Brokers in 5.2.0

2008-12-19 Thread MaenXe
I'm trying to setup a multiple networks of brokers for 4 different environments we have: dev, qa, stage, and production. The default configuration example shows the following line to setup the transport listener to self advertise over multicast using the name 'default'

Re: NPE: java.net.UnknownHostException after installing 5.2, same config as 5.1

2008-12-18 Thread MaenXe
Anyone else having this same issue? We have 4 different environments with 4 different broker networks setup, we can't use the same multicast name for all of them, and we'd prefer not to spell out each server name in the config file, it's not very flexible. This smells like a bug

NPE: java.net.UnknownHostException

2008-12-15 Thread MaenXe
I'm having an issue with my Network of Brokers configuration and an upgrade to 5.2. The configuration we had in 5.1(which worked fine) was: and Now in 5.2, it doesn't like the uri and/or discoveryUri and we get the following error

Re: Question about Logging in ActiveMQ 5.1

2008-09-04 Thread MaenXe
Well, I thought this was what I needed, but after examining the logs, this isn't gonna do. For one, it puts the entire payload of the message into the log P-(, basically what I'm looking for is something similar to the apache logs, or a mail log. I need producer/consumer ID, queue/topic, msg ID,

Re: Question about Logging in ActiveMQ 5.1

2008-08-29 Thread MaenXe
Thanks Gary! That was what I needed! M@ Have not tried this but it looks promising http://activemq.apache.org/logging-interceptor.html also, with log4j it is possible to specify the logging level on a per class or package basis. see the examples in conf/log4j.configuration. -- View this m

Question about Logging in ActiveMQ 5.1

2008-08-27 Thread Maenxe
I'd like to setup log4j to log when a message was received by the broker, and when a consumer retrieved it. Is there a way to do this? It seems the default logging options are simply INFO, WARN, ERROR, FATAL, and DEBUG. We're currently using INFO, but would like a little more granular detail.