How to debug IllegalArgumentException

#26333

Hello,

We are getting an IllegalArgumentException while converting an HTML document. It’s not obvious what’s wrong in the HTML that caused this error. Is it possible that we can get the source code so we can step through the debugger? We are a volume license customer.

Best regards,

Caused by: java.lang.IllegalArgumentException
at sun.net.www.ParseUtil.decode(ParseUtil.java:189)
at sun.net.www.protocol.file.Handler.openConnection(Handler.java:65)
at sun.net.www.protocol.file.Handler.openConnection(Handler.java:55)
at java.net.URL.openConnection(URL.java:945)
at org.zefer.cache.c.getResourceAsBytes(Unknown Source)
at org.zefer.cache.ResourceCache.getObject(Unknown Source)
at org.zefer.cache.ResourceCache.getObject(Unknown Source)
at org.zefer.cache.ResourceCache.getImage(Unknown Source)
at org.zefer.html.doc.o.OO0000(Unknown Source)
at org.zefer.html.doc.o.super(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.p.super(Unknown Source)
at org.zefer.html.doc.m.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.p.super(Unknown Source)
at org.zefer.html.doc.m.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.b.d.o00000(Unknown Source)
at org.zefer.html.doc.ab.super(Unknown Source)
at org.zefer.html.doc.Document.paint(Unknown Source)
at org.zefer.pd4ml.PD4ML.super(Unknown Source)
at org.zefer.pd4ml.PD4ML.render(Unknown Source)

#27854

Obviously the exception is thrown in the standard JDK classes and the “problem” method (sun.net.www.protocol.file.Handler.openConnection (Handler.java:55)) has anything to do with URL connections.

A good strategy in the case would be to switch PD4Ml debug on (pd4ml.enableDebugInfo()) and to inspect STDOUT (or server’s log) for the last URL it tried to connect.

[Author]

Posts