IntelliJ running / debug configurations logging

Answered

I recently migrated from Eclipse to IntelliJ IDEA, and I used the eclipser plugin in order to convert my eclipse run configuration to IntelliJ IDEA run configuration.

However, when I run or debug. I get many logs, and I wish to disable that.

i.e I get:

How can I disable these logs, and what are they exactly?

11:48:30.923 [qtp1824837049-34] DEBUG org.eclipse.jetty.io.WriteFlusher - ignored: WriteFlusher@2f517749{IDLE}->null
java.nio.channels.ClosedChannelException: null
    at org.eclipse.jetty.io.WriteFlusher.onClose(WriteFlusher.java:492)
    at org.eclipse.jetty.io.AbstractEndPoint.onClose(AbstractEndPoint.java:353)
    at org.eclipse.jetty.io.ChannelEndPoint.onClose(ChannelEndPoint.java:215)
    at org.eclipse.jetty.io.AbstractEndPoint.doOnClose(AbstractEndPoint.java:225)
    at org.eclipse.jetty.io.AbstractEndPoint.shutdownInput(AbstractEndPoint.java:107)
    at org.eclipse.jetty.io.ChannelEndPoint.fill(ChannelEndPoint.java:238)
    at org.eclipse.jetty.server.HttpConnection.fillRequestBuffer(HttpConnection.java:340)
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:250)
    at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
    at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
    at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:698)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:804)
    at java.base/java.lang.Thread.run(Thread.java:832)
11:48:30.923 [qtp1824837049-34] DEBUG org.eclipse.jetty.io.FillInterest - onClose FillInterest@47cdec41{null}
11:48:30.924 [qtp1824837049-34] DEBUG org.eclipse.jetty.io.ManagedSelector - Wakeup ManagedSelector@1991f767{STARTED} id=2 keys=1 selected=0 updates=0
11:48:30.927 [qtp1824837049-34] DEBUG org.eclipse.jetty.util.thread.QueuedThreadPool - queue org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint@6d293e17
11:48:30.927 [qtp1824837049-34] DEBUG org.eclipse.jetty.io.ChannelEndPoint - filled -1 HeapByteBuffer@61ebacc[p=0,l=0,c=8192,r=0]={<<<>>>HTTP/1.1 200 OK\r\n...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
11:48:30.927 [qtp1824837049-34] DEBUG org.eclipse.jetty.http.HttpParser - atEOF HttpParser{s=CLOSE,0 of -1}
11:48:30.927 [qtp1824837049-33] DEBUG org.eclipse.jetty.util.thread.QueuedThreadPool - run org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint@6d293e17
11:48:30.928 [qtp1824837049-36] DEBUG org.eclipse.jetty.io.ManagedSelector - Selector sun.nio.ch.KQueueSelectorImpl@3e20df29 woken with none selected
11:48:30.929 [qtp1824837049-36] DEBUG org.eclipse.jetty.io.ManagedSelector - Selector sun.nio.ch.KQueueSelectorImpl@3e20df29 woken up from select, 0/0/0 selected
0
1 comment
Avatar
Yaroslav Bedrov

Hello,

Could you please share screenshots with your run configuration?

0

Please sign in to leave a comment.