[
https://issues.apache.org/jira/browse/ARTEMIS-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217953#comment-17217953
]
Clebert Suconic commented on ARTEMIS-2956:
------------------------------------------
[~freddy.correa] Jira is not really a good place to ask question.. you should
have used the user's forum on this...
Anyway: this is not really a bug... the issue is that one thread is just
waiting to submit the write:
at org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.submitWrite(Native
Method)
at
org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.submitWrite(LibaioContext.java:209)
at
org.apache.activemq.artemis.nativo.jlibaio.LibaioFile.write(LibaioFile.java:77)
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFileFactory$AIOSequentialCallback.run(AIOSequentialFileFactory.java:347)
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.writeDirect(AIOSequentialFile.java:279)
at
org.apache.activemq.artemis.core.io.AbstractSequentialFile$LocalBufferObserver.flushBuffer(AbstractSequentialFile.java:284)
at
org.apache.activemq.artemis.core.io.buffer.TimedBuffer.flushBatch(TimedBuffer.java:361)
- locked org.apache.activemq.artemis.core.io.buffer.TimedBuffer@5a45133e
at
org.apache.activemq.artemis.core.io.buffer.TimedBuffer.flush(TimedBuffer.java:338)
at
org.apache.activemq.artemis.core.io.buffer.TimedBuffer$CheckTimer.run(TimedBuffer.java:473)
at java.lang.Thread.run(Thread.java:748)
What made the TimedBuffer to block in there.. so it's really an issue on your
file system.
For a slow file system (such as NFS, GFS2 I really recommend using NIO). It
will be slow based on your file system.. but you won't suffer from timeouts or
other issues.
libaio was designed for local & fast disks... so it's no point using a slow
remote storage anyways.
> Non-clustered ActiveMQ with GFS2 Shared filesystem (with static HA)
> -------------------------------------------------------------------
>
> Key: ARTEMIS-2956
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2956
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: ActiveMQ-Artemis-Native
> Affects Versions: 2.15.0
> Environment: [amquser@inalltd1lxpoc01 bin]$ hostnamectl
> Static hostname: inalltd1lxpoc01
> Icon name: *computer-vm*
> Chassis: vm
> Machine ID: 5c174c18250e4d10846582af291499e4
> Boot ID: be4ce27a1e8742b0af878ec995c3902a
> Virtualization: *vmware*
> Operating System: Red Hat Enterprise Linux
> CPE OS Name: cpe:/o:redhat:enterprise_linux:7.8:GA:server
> Kernel: Linux 3.10.0-1127.19.1.el7.x86_64
> Architecture: x86-64
> Reporter: Fredy Correa
> Assignee: Clebert Suconic
> Priority: Critical
> Labels: newbie
> Fix For: 2.15.0
>
> Attachments: apache-artemismq-architecture-reference-model.png,
> artemis.log, artemis.log.2020-10-16, broker-master.xml, broker-slave.xml
>
>
> 2020-10-20 00:13:18,200 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path
> 02020-10-20 00:13:18,200 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path
> 02020-10-20 00:13:18,212 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224079: The process for the virtual machine will be killed, as component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@5a45133e is not
> responsive2020-10-20 00:13:18,392 WARN
> [org.apache.activemq.artemis.core.server] AMQ222199: Thread dump:
> *******************************************************************************Complete
> Thread dump "Thread-318
> (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$7@2f8dad04)"
> Id=411 BLOCKED on
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@5a45133e owned by
> "activemq-buffer-timeout" Id=19 at
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer.checkSize(TimedBuffer.java:241)
> - blocked on
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer@5a45133e at
> org.apache.activemq.artemis.core.io.AbstractSequentialFile.fits(AbstractSequentialFile.java:180)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:3151)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2882)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$100(JournalImpl.java:92)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:849)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase$$Lambda$26/1030684756.run(Unknown
> Source) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> Number of locked synchronizers = 1 -
> java.util.concurrent.ThreadPoolExecutor$Worker@7dee662a
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
