Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-30092

GSS [EAP 8.1.0.GA] Startup error traces related to serialization errors are not captured in the log files

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Start the domain with

      bin/domain.sh -Djdk.serialFilter=maxbytes=1

      Show
      Start the domain with bin/domain.sh -Djdk.serialFilter=maxbytes=1

      DomainServerMain is in charge of starting the managed servers, It is launched from the process controller, which captures the stderr of the launched process and saves any captured errors in the process-controller.log file. This was implemented by JBEAP-25724.

      This capture of the stderr works only until a certain point; once the managed process installs the StdioContext, the process controller assumes that any stdout/stderr traces will be managed by the managed server and its logging framework.

      However, there are still usages of the original stderr in the DomainServerMain after the StdioContext gets installed, which means that any trace printed using this original stream gets out of control of the logger framework, which makes difficult to review an analize the root cause of an issue if the user has no access to the server output console where this original stderr gets printed.

              yborgess1@redhat.com Yeray Borges Santana
              yborgess1@redhat.com Yeray Borges Santana
              Martin Svehla Martin Svehla
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: