I reported the same problem for 5.13.4.
http://activemq.2283324.n4.nabble.com/Message-stuck-in-queue-td4720713.html
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Update: The message finally got consumed after about 2 days. Was this because
of some hanging client? How can I troubleshoot it?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-stuck-in-queue-tp4720713p4720721.html
Sent from the ActiveMQ - User mailing list archiv
ActiveMQ 5.13.4 with kahadb
There are some stuck messages left in one of my queues. The messages are
produced several days ago and it seems they will never be consumed. I can
see from the web console they are in the queue. Though new messages are
produced and consumed in the same queue without prob
Nope, there was not any error message before it.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/mkahadb-with-error-java-lang-IllegalStateException-PageFile-is-not-loaded-tp4718293p4718423.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I'm using 5.13.4 with mkahadb. Sometimes I saw this error:
java.lang.IllegalStateException: PageFile is not loaded
at
org.apache.activemq.store.kahadb.disk.page.PageFile.assertLoaded(PageFile.java:811)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at
org.apache.activemq.store.kahadb.disk
ActiveMQ 5.13.4 with mkahadb storage.
We see this several times: ActiveMQ runs well for some days. From a certain
point, the thread numbers starts to increasing without additional clients.
In the meantime, the log get flooded by connection 'taking a long time to
shutdown' like these:
2016-09-08 17:
I also have the similar case. Is there any way to avoid this on server side?
such as time out and close the client connection if it hangs.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-3000-messages-can-not-be-received-tp4715396p4715653.html
Sent from the Activ
I have the
We don't use ws protocol, only use openwire and nio. Is AMQ-6275 still
related? I upgraded to 5.13.4 anyway. Let's see if it happens again.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Dead-lock-in-5-13-3-tp4715561p4715605.html
Sent from the ActiveMQ - Use
I got a dead lock in 5.13.3. But the jstack failed to get the stack of the
locking threads:
Deadlock Detection:
Found one Java-level deadlock:
=
"ActiveMQ NIO Worker 93810":
waiting for ownable synchronizer 0x7fdafc09e548, (a
java/util/concurrent/locks/ReentrantRe
We used client version 5.10.0 with server version 5.13.3 and it's fine.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Please-tell-me-integrity-version-between-server-and-client-tp4714335p4714336.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Tim,
Thanks. After we fixed the problematic client, ActiveMQ is working as
expected. The producer count stays stable even client exits abnormally.
ActiveMQ is doing the cleanup correctly.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Producer-count-keeps-increasing-
We'v found the leaking client by checking the producer count of the queues
one by one in JConsole.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Producer-count-keeps-increasing-tp4714087p4714138.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Yes, we have many clients produces messages and it's possible that some of
the clients didn't close the producer properly. We will check them closely.
Meantime, is there any way to prevent this at the server side? For example,
if the client network connection is broken, will the orphan producer get
Hi,
I'm using activemq 5.13.3. I'm seeing the producer count on the broker side
keeps increasing and never shrinks. I inspected the value TotalProducerCount
of the broker via jmx. And it is also verified by the class count of
org.apache.activemq.broker.jmx.ProducerView in jvm heap class histogram.
No, they don't come back immediately if I delete them. But they will appear
occasionally when activemq is running in steady status. There is no easy
observed trigger as far as I know such as restart etc. I don't know if it is
triggered by admin console reloading since we always need to reload the
a
I already turned on the trace log on MessageDatabase and also added some
debug code. The file is removed from the GC candidates in this loop in the
method 'void checkpointUpdate(Transaction tx, boolean cleanup) throws
IOException':
// Go through all the destinations to see if any of the
OK, I found the problem. It's browser related. Actually it's a problem of an
extension of firefox which makes hyper link from text. It makes link
'DLQ.com' from the dead letter queue name 'DLQ.com.xxx.xxx' and then caused
the display problem. I can view the page correctly in IE.
However, there is
I noticed some old data files(generated 2 days ago) are not get cleaned up.
So I referred the doc to check which queue is using them. I found they are
reserved for one busy queue. The queue has several hundreds of messages
going through every second. There couldn't be any old message left there. I
OK, I will try to do that next time it occurs
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Queues-with-empty-name-appear-in-web-console-tp4713148p4713228.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I can browse the queue and found its name in URL. It is actually a dead
letter queue. I also checked the page html source and I can see the queue
name in source but somehow it just doesn't display.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Queues-with-empty-name-app
Hi,
I have seen this problem on both 5.13.3 and 5.10.2. There are several
messages in them. Where do they come from?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Queues-with-empty-name-appear-in-web-console-tp4713148.html
Sent from the ActiveMQ - User mailing list arc
All right. I will try with that. Thanks for the info.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/nio-buffer-memory-problem-tp4712706p4712910.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I found this article: http://www.evanjones.ca/java-bytebuffer-leak.html
I guess 5.10.2 uses 'Heap ByteBuffers' which is backed with unlimited
'temporary Direct ByteBuffer', while 5.13.3 uses 'Direct ByteBuffer'
directly?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/nio
We only ran 5.13.3 in production for several days and didn't see this issue.
But we saw another issue which we didn't see in 5.10.2:
Some old data file(2 days ago) is reserved because of some queue. But when I
check the queue in admin ui, I didn't see any old message. The new messsages
are in and
based on your log, I think it should be passengerride.user.1234567890 which
prevents the deletion of #6
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-5-13-2-Kaha-DB-logs-cleanup-issue-tp4712046p4712707.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
Hi,
We've been run activemq 5.10.2 with thousands of clients in our production
for quite a long time. Several days ago, we upgraded to the newer version
5.13.3. After running for several days, we saw the OutOfMemoryError and
activemq hung up in busy GC:
2016-06-06 02:01:54,238 | ERROR | Error in t
I can view those dead messages in web console by clicking the queue name, not
the count. When I restart, they disappears.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Negative-message-count-and-dead-messages-in-queue-tp4712505p4712591.html
Sent from the ActiveMQ - User
And no, no selector is used, just simple JMS consumer.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Negative-message-count-and-dead-messages-in-queue-tp4712505p4712561.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Yes, in web console. I can see those messages. They are produced several days
ago. When there is no new message, they stick in the queue. When new
messages are produced, they are consumed quickly but those old messages are
still there and no consumer can get them.
--
View this message in context
Because new messages are produced and consumed all the time in the same
queue. Just those messages are left there and it seems no consumers can get
them.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Negative-message-count-and-dead-messages-in-queue-tp4712505p4712545.ht
OK, so the ACKs referencing to those non-existing file won't prevent GC to
remove this file right?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/data-file-gc-log-indicates-ack-refer-to-non-existing-file-tp4712509p4712537.html
Sent from the ActiveMQ - User mailing list a
activemq 5.10.2, the gc log show:
2016-06-01 16:26:37,299 | TRACE | not removing data file: 857 as contained
ack(s) refer to referenced file: [834, 850, 832, 849, 833, 855, 854, 836,
837, 857, 856] | org.apache.activemq.store.kahadb.MessageD
atabase | ActiveMQ Journal Checkpoint Worker
But the exis
Hi,
We are using activemq 5.10.2 on our production. I always see negative
message count on some busy queues with many producers and consumers in admin
ui. This is not a big problem but another issue is important. There are some
stuck messages left in some of my queues. The messages are produced se
All right looks I'm stupid. this thread can be discarded. This is not an
Activemq problem but just the output problem of my receive end. The web
admin console displays bad characters but that's just fine. It just doesn't
show them correctly but the message in it is correct.
--
View this message in
Hi, I'm using Activemq 5.4.2 on Ubuntu server.
I put text message with java by these codes:
TextMessage message = session.createTextMessage(myText);
producer.send(message);
myLogger.finest("Sent message:");
myLogger.finest(message.getText());
"myText" contains some Chinese
may be too big for confluence (jira) also and also for gmail(25MB),
> maybe try one of the fileshare sites, not sure what to recommend here.
>
> On 25 March 2010 13:23, RuralHunter wrote:
>
>>
>> How to? I haven't used jira before...and the data directory is quite
>
How to? I haven't used jira before...and the data directory is quite large,
more than200M.
Gary Tully wrote:
>
> Would it be possible to tar and compress a data directory that fails to
> start and attach it to a jira issue?
>
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
Hi,
I'm using kahadb as storage. I have seen this several times, for both 5.3.0
and 5.3.1. If there are many messages in queues and ActiveMQ is not stopped
in a correct manner, such as server crash or reboot accidentally, then
ActiveMQ can not be started. I have to delete all files in data directo
Looks there is similar issue raised already:
http://old.nabble.com/Brigded-brokers-wont-reconnect-td27427208.html#a27427208
My point is that, no matter what caused the connection between 2 brokers
broken, activemq should be able to re-establish the connection when things
get fixed/recovered. I do
Hi,
I created a network connector from my local activemq to a remote activemq
server with configuration below:
The problem is that sometime I got InactivityIOException and the connector
never gets recovered after that. The communication between 2 servers is
stopped until I recycle
40 matches
Mail list logo