Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1832

As an EAP developer I do not want too many open files leak when paging

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • None
    • None
    • None
    • None

    Description

      Server shuts down when page files grow out of control. Potentially an issue with user limits in test environment. Feature enhancement to block before running out of files?

      20:55:05,329 WARN [org.apache.activemq.artemis.core.server] (Thread-1 (ActiveMQ-client-netty-threads)) AMQ222010: Critical IO Error, shutting down the server. file=NIOSequentialFile /home/buildadm/workspace/early-testing-messaging-weekly-tests-ha-failover-replicated-journal-network-failures/server2/jboss-eap/standalone/data/activemq/paging/d56c100c-89f2-11e8-b753-fa163eb0dd0f/000003584.page, message=/home/buildadm/workspace/early-testing-messaging-weekly-tests-ha-failover-replicated-journal-network-failures/server2/jboss-eap/standalone/data/activemq/paging/d56c100c-89f2-11e8-b753-fa163eb0dd0f/000003584.page (Too many open files): ActiveMQIOErrorException[errorType=IO_ERROR message=/home/buildadm/workspace/early-testing-messaging-weekly-tests-ha-failover-replicated-journal-network-failures/server2/jboss-eap/standalone/data/activemq/paging/d56c100c-89f2-11e8-b753-fa163eb0dd0f/000003584.page (Too many open files)]

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15133 (7.1.z) ENTMQBR-1832 - too many open files leak when paging replication catch up

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2670 Too many opened FDs after server stops

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              mtaylor1@redhat.com Martyn Taylor (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified