UPnP: [Fatal Error] :15:1: Content is not allowed in trailing section.

[guest]

Hi,

Since the new upgrade to 0.8.7 yesterday, i get a Fatal error.

2011/06/28 02:06:02 | INFO: Started org.mortbay.jetty.Server@679bfb30
2011/06/28 02:06:02 | [Fatal Error] :15:1: Content is not allowed in trailing section.
2011/06/28 02:06:03 | [Fatal Error] :6:1: Content is not allowed in trailing section.
2011/06/28 02:06:03 | [Fatal Error] :6:1: Content is not allowed in trailing section.
2011/06/28 02:06:03 | [Fatal Error] :6:1: Content is not allowed in trailing section.
2011/06/28 02:06:03 | [Fatal Error] :6:1: Content is not allowed in trailing section.

I2P version: 0.8.7-0deb2

Java version: Sun Microsystems Inc. 1.6.0_20 (OpenJDK Runtime Environment 1.6.0_20-b20)
Platform: Linux amd64 2.6.38-10-generic
Processor: uninitialized (core2)
Jbigi: Locally optimized native BigInteger? library loaded from file
Encoding: UTF-8

Best Regards

[killyourtv]

From IRC:

<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> jvm 1 | [Fatal Error] :6:1: Content is not allowed in trailing section.
<ThePriest?> is this bad???
<zzz> no
<zzz> it's a UPnP error I've tried to fix, guess I wasn't 100% successful :(

[zzz]

The attempted fix was in 0.8.6. I don't think that anything in 0.8.7 made it any worse. The problem is certain UPnP routers returning bad XML. You can ignore the error or turn off UPnP or switch routers.

[guest]

Hi zzz,

Thanks for your answer, i have turn off my upnp, i don't need it anyway.

Best regards

[guest]

Dear i2p Developers:

Just an update on this same issue from a different user (on Windows 7). I have experienced this same error since the earliest 0.8.* versions. I have upgraded continuously as new builds were released. This error has been persisent since then. I am now on 0.9.0 and this error remains.

However, everything within i2p appears to be working properly.

[guest]

Update: issue is resolved under Windows by disabling UPnP.

[zzz]

That's a workaround, not a fix. Changing the title back. As explained above, it's caused by UPnP devices generating bad XML, but our parser should be able to handle it.

I am working on upgrading our UPnP library but I don't think that will fix it either.

[zzz]

UPnP lib updated to latest in 0.9.18-6, but unlikely to fix this. We should proceed with a local fix if possible.

[zzz]

Add a subticket #1653.

[zzz]

See #1653 for resolution