Hi,
Is there a way to configure custom logging when using activemq maven plugin?
I tried
log4j.configuration
file://${project.basedir}/src/test/conf/activemq.log4j.properties
..
but it did'nt do the trick...
Thanks, Ron
Hi,
I am new to ActiveMQ. So, please forgive me if this question sounds weird to
you.
How can I disable TempQueue and TempTopic? Is there any way? I am using AMQ
5.4.2.
Thanks,
Bodhayan.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Disable-TempQueue-TempTopic-tp33344
One other thing I noticed. When I do not try to establish a reply queue, I do
not see any messages about advisory queues being initialized. When I do
create a temporary reply queue, however, I see messages about advisory
queues, e.g. adding destination: topic://ActiveMQ.Advisory.TempQueue.
Perhaps
So after doing some more digging, it seems I can connect to the broker from
behind a NAT fine. I can send messages to the broker machine, and the broker
machine can send messages to the client machine that is behind the NAT. This
can be done with a single outbound TCP transport connector from the c
I am trying to use the job delay feature .It worked .
I am running embedded active mq and it uses file based persistence.I tried
using delayed message delivery for 2 hours it worked . In my use case I
want to delay delivery by 48 hours and when I tried to test it did not
work, within this 48
thanks for closing the loop on this one :-)
On 3 March 2011 13:48, robert.sl...@misys.com wrote:
> Just to note that I was able to resolve this issue by changing our code to
> maintain a single connection for the multiple concurrent processing threads.
> The slow down seems to be caused by contin
On Thu, 2011-03-03 at 07:39 -0800, burns wrote:
> When I call Apache.NMS.IConnection.Start(), it spawns no less than 800
> threads. The gc debugger that I'm using has a default maximum of 256. Are
> the 800 threads intentional? It seems like an awful lot.
We'd need a bit more info to help you o
When I call Apache.NMS.IConnection.Start(), it spawns no less than 800
threads. The gc debugger that I'm using has a default maximum of 256. Are
the 800 threads intentional? It seems like an awful lot.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Hundreds-and-hundreds
Just to note that I was able to resolve this issue by changing our code to
maintain a single connection for the multiple concurrent processing threads.
The slow down seems to be caused by continuous opening and closing of queue
connections to ActiveMQ.
--
View this message in context:
http://acti
Hi,
Seems logs didn't get attached
Log of Broker 1:
2011-03-03 12:04:02,061 | DEBUG | stopping dynamic-broker1 bridge to
dynamic-broker2 |
org.apache.activemq.network.DemandForwardingBridgeSupport |
Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:NC:B
rokerService
Hi,
I am running ActiveMQ on two systems (using default
activemq-dynamic-network-broker.xml config file). Each one is connected
with one application (which is acting both as a publisher and durable
subscriber) present in that system. A topic "SimpleTopic" is defined and
messages are exchanged p
It seems there is some kind of TCP buffering issue (only on linux?) which
causes lng delays when sending certain size messages over ActiveMQ.
This was discussed and supposedly fixed in the past (e.g. here:
https://issues.apache.org/jira/browse/AMQ-1156) but at least with the PHP
Stomp library
12 matches
Mail list logo
