Uploaded image for project: 'XNIO'
  1. XNIO
  2. XNIO-402

Log Xnio thread size config at debug

XMLWordPrintable

      It would be helpful to have xnio log at debug: io-threads , pool-size, stack-size, task-keepalive etc , when xnio starts up, so that we can see if there is some tuning that is needed when a user encounters an issue.

      18:49:23,743 INFO  [org.xnio] XNIO version 3.8.4.Final-redhat-00001
      18:49:23,756 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.8.4.Final-redhat-00001
      18:49:23,764 TRACE [org.xnio.nio] Starting up with selector provider class sun.nio.ch.KQueueSelectorProvider
      18:49:23,769 TRACE [org.xnio.nio] Using Default system selector creator for provider class sun.nio.ch.KQueueSelectorProvider for main selectors and Default system selector creator for provider class sun.nio.ch.KQueueSelectorProvider for temp selectors
      18:49:23,827 INFO  [org.jboss.threads] JBoss Threads version 2.4.0.Final-redhat-00001
      18:49:23,848 TRACE [org.xnio.nio] CAS org.xnio.nio.NioXnioWorker@7dadc46d 00000001 -> 00000002
      18:49:23,848 TRACE [org.xnio.nio] CAS org.xnio.nio.NioXnioWorker@7dadc46d 00000002 -> 00000003
      18:49:23,848 TRACE [org.xnio.nio] Starting worker thread Thread[XNIO-1 I/O-1,5,main]
      18:49:23,848 DEBUG [org.xnio.nio] Started channel thread 'XNIO-1 I/O-1', selector sun.nio.ch.KQueueSelectorImpl@1c9d0f0d
      18:49:23,848 TRACE [org.xnio.nio] Starting worker thread Thread[XNIO-1 Accept,5,main]
      18:49:23,849 DEBUG [org.xnio.nio] Started channel thread 'XNIO-1 Accept', selector sun.nio.ch.KQueueSelectorImpl@7511858d
      18:49:23,849 TRACE [org.xnio.nio.selector] Beginning select on sun.nio.ch.KQueueSelectorImpl@1c9d0f0d
      18:49:23,849 TRACE [org.xnio.nio.selector] Beginning select on sun.nio.ch.KQueueSelectorImpl@7511858d
      

              rhn-support-ivassile Ilia Vassilev
              rhn-support-ivassile Ilia Vassilev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: