Re: ActiveMQ admin command

I have checked the source code but still it is not clear to me that where is the filtering happening. I am using these 3 command: -- activemq-admin query --view *InactiveDurableTopicSubscribers *--jmxurl service:jmx:rmi:///jndi/rmi://amqbroker:8887/jmxrmi --jmxuser guest --jmxpassword activem

Re: producer is getting stuck

Thanks for you quick responses. :) This OutOfMemoryError did not cause my jvm to exit. Even after this error, my jvm ran fine, but the producers got stuck. And the other points to know from the OutOfMemoryError stack trace is, the call to zipping has caused this error. And this call to zipping ha

Re: producer is getting stuck

Any time you get an OutOfMemory exception, that means memory for the JVM has been exhausted, and will lead to all kinds of failed processing. Even getting an OutOfMemory exception logged anywhere can be tricky since the logging may need to allocate memory. Look for leaks in the client. A good to

Re: producer is getting stuck

I see the following three exceptions at producer side. Will this information give any clue? 1) mmap failed for CEN and END part of zip file java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:114) at java.util.jar.

Re: Connection being made, but not registering as a Consumer of any queues

Is there any way you know of to put tracing into that file? If you're not sure where the consumers are started, then are you sure that piece exists on both servers? -- View this message in context: http://activemq.2283324.n4.nabble.com/Connection-being-made-but-not-registering-as-a-Consumer-of

Re: EOF Exception

Clients and broker are all running in the same karaf instance...in fact all my "clients" are connecting using this connection setting: Netstat came back with nothing. On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos wrote: > Hello Chris, > > You can use netstat for identify w

Re: EOF Exception

Hello Chris, You can use netstat for identify what process is listening in 47400 port, as root type: # netstat -punlt | grep 47400 I hope will be helpfully Regards 2014/1/21 artnaseef > Can you use a network packet sniffer, like tcpdump or wireshark? > > Those errors mean the other end of

Create Activemq Instance

We have auto installer for activemq which creates multiple instance of activemq. But when it create new instance it changes borker name. Is there a way to new instance with same broker name. thanks, chirag

Re: ActiveMQ 5.5.1 - Connections stuck in CLOSE_WAIT state, reaching file descriptor limit

I have seen something like this when the hand off thread that deals with accepted sockets die. The error handling needs to be improved to make that case more obvious. It is a long shot, but you could disable the use of an accept queue and see if that resolves the problem. The thread name (fro

Re: EOF Exception

Can you use a network packet sniffer, like tcpdump or wireshark? Those errors mean the other end of the TCP/IP connection was dropped without a higher-level cleanup of the connection. Could be the broker dropping and coming back, network issues (timeouts, disconnects), or aborted connection in th

Re: producer is getting stuck

You are right - that stack trace shows the client waiting for an acknowledgement from the server. It could be caused by producer-flow-control kicking in on the server. If that's the case, the broker will log messages. Running out of memory on the broker could cause this too. Lost packets should

Re: ActiveMQ 5.5.1 - Connections stuck in CLOSE_WAIT state, reaching file descriptor limit

Without looking at the stack trace carefully, problems getting stack traces is often seen with a memory leak or overloaded broker (i.e. running out of heap or permgen space). Can you connect jconsole or visualvm to the broker and check the heap and permgen space when the problem occurs? If you wa

Re: ActiveMQ 5.5.1 - Connections stuck in CLOSE_WAIT state, reaching file descriptor limit

Hi Christian, Apologies for the late reply. I've a thread dump of the broker when it had reached the limit for open sockets. actmqjstack.txt This had to be taken with force with jstack as ActiveMQ at that stage would not ac

LevelDB Dependencies

I am making the change to go from KahaDB to LevelDB. I was a bit shocked to find so many transitive dependencies making their way into our build. Researching the Maven POM for the activemq-leveldb-store, I see many are related to what I determined are optional features: replication and compression.

Re: ActiveMQ admin command

most of the work is done client side at the moment. Peek at the source for all the detail: https://github.com/apache/activemq/blob/trunk/activemq-console/src/main/java/org/apache/activemq/console/command/QueryCommand.java On 21 January 2014 12:04, khandelwalanuj wrote: > Hey, > > Little bit confu

Re: Transport Options (Randomize algorithm)

Thanks for your help and your code. 2014/1/21 Richard Kettelerij > Here's the implementation of ?randomize=true. Source > > https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/transport/failover/FailoverTransport.java > > if (randomize) { >

Re: Transport Options (Randomize algorithm)

Here's the implementation of ?randomize=true. Source https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/transport/failover/FailoverTransport.java if (randomize) { // Randomly, reorder the list by random swapping for (int i = 0; i

Re: Redelivery header and AMQ broker failure

the rewriteOnRedelivery is only for transacted sessions b/c only then does the broker get delivery notifications. On 21 January 2014 10:02, Gnome wrote: > I would like to take advantage of the Redelivery flag to identify potential > message duplicates that going through our system in event of fai

Redelivery header and AMQ broker failure

I would like to take advantage of the Redelivery flag to identify potential message duplicates that going through our system in event of failure. When consumer failure occurs and the JMS connection is established in CLIENT_ACKNOWLEDGE mode, redelivery mechanism of inflight messages is working well

producer is getting stuck

Hi, I have an issue while sending messages to ActiveMQ. I assume that, the following statement stands true. "producer internally receieves a receipt from the broker which unblocks the send() method." I guess in my case, i am not receiving receipt from the broker, hence my sender method could no

Re: ActiveMQ admin command

Hey, Little bit confused here. Please help !! -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-admin-command-tp4676307p4676566.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.