Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5014

Log files truncated when jboss.as.management.blocking.timeout error happens on startup

XMLWordPrintable

    • Hide
      1. Install a new copy of EAP 7.2, this is reproducible on any patch level
      2. Copy the jboss.as.management.blocking.timeout and logging config from the standalone_example.xml into your standalone.xml file
      3. Now copy the provided sample-test-war-0.0.1-SNAPSHOT.war file to the deployment directory
      4. Start the EAP server, wait for the jboss.as.management.blocking.timeout
      5. Check the logs directory, all log files get truncated after the timeout
      Show
      Install a new copy of EAP 7.2, this is reproducible on any patch level Copy the jboss.as.management.blocking.timeout and logging config from the standalone_example.xml into your standalone.xml file Now copy the provided sample-test-war-0.0.1-SNAPSHOT.war file to the deployment directory Start the EAP server, wait for the jboss.as.management.blocking.timeout Check the logs directory, all log files get truncated after the timeout
    • Hide

      Manually replacing the logging.properties file with a version created by a successful startup (without the jboss.as.management.blocking.timeout error) seems to avoid the issue.

      Show
      Manually replacing the logging.properties file with a version created by a successful startup (without the jboss.as.management.blocking.timeout error) seems to avoid the issue.

      After receiving a jboss.as.management.blocking.timeout error on startup, all the log files are truncated to zero bytes.  This behavior happens on any patch level of EAP 7.2.x and also on EAP 7.3 but does not happen on EAP 7.1.6.

        1. sample-test-war-0.0.1-SNAPSHOT.war
          83 kB
        2. standalone_example.xml
          30 kB

              jperkins-rhn James Perkins
              rhn-support-dboeren David Boeren
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: