# HttpChannel warning - /system/gateway {}

**URL:** <https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [January 13, 2020, 12:50am UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239 "2020-01-13T00:50:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\
**Post date:** [January 13, 2020, 12:50am UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/1 "2020-01-13T00:50:57Z")

</div>

I’ve just started getting a lot of these errors in the wrapper.log.  
I can’t work out what has changed in the project that may be causing them.  
Does anyone know what they mean or where I need to look to fix them?

Using version 8.0.6

```auto
INFO | jvm 1 | 2020/01/13 09:07:16 | W [o.e.j.s.HttpChannel] [22:07:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:08:46 | W [o.e.j.s.HttpChannel] [22:08:46]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:09:16 | W [o.e.j.s.HttpChannel] [22:09:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:11:16 | W [o.e.j.s.HttpChannel] [22:11:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:11:36 | W [o.e.j.s.HttpChannel] [22:11:36]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:12:56 | W [o.e.j.s.HttpChannel] [22:12:56]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:13:56 | W [o.e.j.s.HttpChannel] [22:13:56]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:14:26 | W [o.e.j.s.HttpChannel] [22:14:26]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:15:46 | W [o.e.j.s.HttpChannel] [22:15:46]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:16:16 | W [o.e.j.s.HttpChannel] [22:16:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:17:16 | W [o.e.j.s.HttpChannel] [22:17:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:21:56 | W [o.e.j.s.HttpChannel] [22:21:56]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:24:06 | W [o.e.j.s.HttpChannel] [22:24:06]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:24:16 | W [o.e.j.s.HttpChannel] [22:24:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:24:36 | W [o.e.j.s.HttpChannel] [22:24:36]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:27:16 | W [o.e.j.s.HttpChannel] [22:27:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:31:26 | W [o.e.j.s.HttpChannel] [22:31:26]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:33:46 | W [o.e.j.s.HttpChannel] [22:33:46]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:34:46 | W [o.e.j.s.HttpChannel] [22:34:46]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:36:06 | W [o.e.j.s.HttpChannel] [22:36:06]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:36:26 | W [o.e.j.s.HttpChannel] [22:36:26]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:37:16 | W [o.e.j.s.HttpChannel] [22:37:16]: /system/gateway {} 
INFO | jvm 1 | 2020/01/13 09:37:36 | W [o.e.j.s.HttpChannel] [22:37:36]: /system/gateway {} 

```

---

<div class="post-metadata">

**Author:** ![mhicks1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mhicks1/32/14121_2.png) [@mhicks1](https://forum.inductiveautomation.com/u/mhicks1)\
**Post date:** [December 23, 2021, 2:30pm UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/2 "2021-12-23T14:30:50Z")

</div>

Hi David,  
I have recently started receiving these errors in my gateway log. We have had our gateway running since 12/2019 on version 8.0.6 and we just started getting these. I have added a snip of our log file to see if this is the same waring you were getting and if you found the root cause. Thanks…

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/8/b802ebe8d116b6e8deb63e06b2597af2692cf052.png)

---

<div class="post-metadata">

**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\
**Post date:** [December 26, 2021, 7:15am UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/3 "2021-12-26T07:15:56Z")

</div>

Hi mhicks,  
Looks like the same error. Unfortunately I can’t remember how I fixed it. I’ve upgraded to a more recent version and that may have helped.

---

<div class="post-metadata">

**Author:** ![mhicks1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mhicks1/32/14121_2.png) [@mhicks1](https://forum.inductiveautomation.com/u/mhicks1)\
**Post date:** [January 4, 2022, 12:10pm UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/4 "2022-01-04T12:10:37Z")

</div>

Thank you @DavidWisely . If you happen to remember, please let me know. FYI, we had a short period of time where we were getting those warnings but now they seem to have subsided. Crazy, Right?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 4, 2022, 3:49pm UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/5 "2022-01-04T15:49:12Z")

</div>

You can try turning HttpChannel to DEBUG, which should log the stacktrace of the errors (be wary of performance implications if you do):

> <https://github.com/eclipse/jetty.project/issues/2346#issuecomment-389419301>
>
> Similar to #1696, exceptions from \`HTTPChannel.onException\` are mishandled. As …in that ticket, I also believe this is a bug in \`JettyAwareLogger.log\` and should be fixed there rather than in the callers: \`MessageFormatter.arrayFormat\` \[removes\](https://github.com/qos-ch/slf4j/blob/9b536f4259adf2f01852e86306a3a2d7e4a238c0/slf4j-api/src/main/java/org/slf4j/helpers/MessageFormatter.java#L168-L171) the last argument if it is \`Throwable\` and does not include the message or stack trace in \`getMessage\`. Instead, the \`Throwable\` is returned via \`FormattingTuple.getThrowable\`, so \`log\` should at least be doing:
> \`\`\`
> \_logger.log(marker, FQCN, level, ft.getMessage(), null, ft.getThrowable());
> \`\`\`
> 
> This improves the output to include a stack trace:
> \`\`\`
> 2018-03-16 14:59:29,450 WARN \[qtp2053996178-20\] o.e.j.s.HttpChannel \[HttpChannel.java:564\] /test {}
> java.io.IOException: test
> at ...
> \`\`\`
> 
> However, you'll see it does include a stray \`{}\` since the argument. This could be ignored, or it could be fixed by removing \`{}\` if present and \`getThrowable()\` returns non-null.

Maybe your IT group is running a network scanning utility periodically to look for vulnerable HTTP servers in the network?

---

<div class="post-metadata">

**Author:** ![mhicks1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mhicks1/32/14121_2.png) [@mhicks1](https://forum.inductiveautomation.com/u/mhicks1)\
**Post date:** [January 5, 2022, 10:16pm UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/6 "2022-01-05T22:16:57Z")

</div>

Thank you @paul-griffith I will contact them. Strangely enough, I have not had that error pop up since the original post.

---

<div class="post-metadata">

**Author:** ![mhicks1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mhicks1/32/14121_2.png) [@mhicks1](https://forum.inductiveautomation.com/u/mhicks1)\
**Post date:** [January 19, 2022, 12:39pm UTC](https://forum.inductiveautomation.com/t/httpchannel-warning-system-gateway/31239/7 "2022-01-19T12:39:21Z")

</div>

Good Morning… I wanted to add another comment to this thread in case anyone else has this same problem. I did speak with our IT department and they were running some vulnerability scans during those time frames in December. Since they completed, we have not had those errors again. Thanks for help pointing us in the right direction.
