Jetty Warning badMessage: 400 Illegal character for HttpChannelOverHttp"

[Anuj]

Hi Simon,


I am using jetty-9.2.2 with CometD-3.0.1.

I am seeing below warning in my setup. It comes ~4,5 times in a day.:

2014-08-28 08:50:53.712:WARN:oejh.HttpParser:qtp607635164-15194: badMessage: 400 Illegal character for HttpChannelOverHttp@5946f125{r=1,a=IDLE,uri=-}

It looks like some bad request sent to the jetty server. I checked the request logs, didn't find anything over there.

What can cause this warning, Anything Should I do to get rid of this warning  ?


Thanks,
Anuj

[Anuj]

Hi Simon,

did you get a chance to look at this ?

[Simone Bordet]

Hi,

A strange case: the parser encounters a bad character and rejects it.
Unfortunately the logging of this case is not extended, you may want
to file an issue at the Jetty project to improve it:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty.

I think you can just ignore these warnings.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.

[Anuj]

> I think you can just ignore these warnings. 

So message is not lost ? We just want to make sure that messages are not lost because of this.

Thanks,
Anuj

[Simone Bordet]

Hi,

On Tue, Sep 2, 2014 at 3:06 PM, Anuj <khandelw...@gmail.com> wrote:
>> I think you can just ignore these warnings.
>
> So message is not lost ? We just want to make sure that messages are not
> lost because of this.

The problem of message guarantee is different (and orthogonal) from
garbage bytes sent over a connection.
You can have messages lost without those errors.

If you care, you should take a network trace of those bad messages,
analyze them and figure out what generates them.
As I said, Jetty could be more detailed in reporting those errors, and
you should really file an issue about this (otherwise won't be fixed),
but meanwhile there is not much you can do apart analyzing what's
going on.

I don't know what's going on, so I cannot help you that much.
Perhaps it's the client closing the connection, perhaps a proxy in the
middle that is buggy, perhaps the hardware on your network that is
faulty and so on.
I *think* you can ignore the warnings, but the final decision is up to you :)

[Anuj Khandelwal]

Logged the request : https://bugs.eclipse.org/bugs/show_bug.cgi?id=443049

--
--
You received this message because you are subscribed to the Google Groups "cometd-users" group.
To post to this group, send email to cometd...@googlegroups.com
To unsubscribe from this group, send email to cometd-users...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cometd-users

Visit the CometD website at http://www.cometd.org

---
You received this message because you are subscribed to the Google Groups "cometd-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cometd-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.