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.
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 into a DLQ, we'd like
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
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 from JMX(using
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 removeQueue) or from
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 workaround for this bug.
M@
MaenXe wrote:
I have a couple of Queues
://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 m...@docmagic.com wrote:
I recently tried to password protect the JMX Connector using the
instructions
here:
http://activemq.apache.org/jmx.html#JMX
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 :
is of the form:
- networkConnector uri=multicast://${groupId}/
+ networkConnector uri=multicast://default?group=${groupId}/
2008/12/18 MaenXe m...@docmagic.com:
Anyone else having this same issue? We have 4 different environments
with 4
different broker networks setup, we can't use
Thanks to Gary Tully's advice, and the comments listed on
https://issues.apache.org/activemq/browse/AMQ-1489 AMQ-1489 , I was able to
get this working. The correct method would be the specify groups as in
multicast://default?group=dev, etc.
Now I know, and knowing is half the
M@
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'
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 brokers for 4
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.
M@
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:
networkConnectors
networkConnector name=dev-jms-nc uri=multicast://dev-jms/
/networkConnectors
and
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.
15 matches
Mail list logo