Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to see the URL that generates a java.lang.IllegalArgumentException in ORDS 3.0.11 standalone log

kurtlookOct 4 2017 — edited Oct 8 2017

When I find entries in the log file for my ORDS 3.0.11 standalone log file similar to the one below, I'd love to know what URL stimulated the abort.  In my environment, I usually have control over the environment that called ORDS, so I could go in and fix the URL to avoid these aborts. 

Is there a way to determine the URL?

Thanks.

2017-10-03 19:41:06.585:WARN:oejs.HttpChannel:qtp310656974-20: Failed UTF-8 decode for request path, trying ISO-8859-1

2017-10-03 19:41:06.586:WARN:oejh.HttpParser:qtp310656974-20: badMessage: java.lang.IllegalArgumentException: Bad % encoding: %. for HttpChannelOverHttp@a882e85{r=0,c=false,a=IDLE,uri=%.}

2017-10-03 19:41:06.611:WARN:oejs.HttpChannel:qtp310656974-1025: Failed UTF-8 decode for request path, trying ISO-8859-1

2017-10-03 19:41:06.611:WARN:oejh.HttpParser:qtp310656974-1025: badMessage: java.lang.NumberFormatException: se for HttpChannelOverHttp@2aa21d49{r=0,c=false,a=IDLE,uri=%server.policy}

2017-10-03 19:41:06.636:WARN:oejs.HttpChannel:qtp310656974-1024: Failed UTF-8 decode for request path, trying ISO-8859-1

2017-10-03 19:41:06.637:WARN:oejh.HttpParser:qtp310656974-1024: badMessage: java.lang.NumberFormatException: lo for HttpChannelOverHttp@449c8f52{r=0,c=false,a=IDLE,uri=%login-config.xml}

2017-10-03 19:41:06.661:WARN:oejs.HttpChannel:qtp310656974-20: Failed UTF-8 decode for request path, trying ISO-8859-1

2017-10-03 19:41:06.662:WARN:oejh.HttpParser:qtp310656974-20: badMessage: java.lang.NumberFormatException: or for HttpChannelOverHttp@6868a738{r=0,c=false,a=IDLE,uri=%org/jboss/version.properties}

2017-10-03 19:42:03.647:WARN:oejs.ServletHandler:qtp310656974-1025: /ords/

java.lang.IllegalArgumentException: %{#context['com.opensymphony.xwork2.dispatcher.HttpServletResponse'].addHeader('struts-cve-2017-5638', 'vulnerable')}.multipart/form-data

at oracle.dbtools.http.ContentType.contentType(ContentType.java:225)

at oracle.dbtools.http.servlet.NormalizedHttpServletRequest.isFormPost(NormalizedHttpServletRequest.java:143)

at oracle.dbtools.http.servlet.NormalizedHttpServletRequest.<init>(NormalizedHttpServletRequest.java:105)

at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:66)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)

at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)

at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)

at org.eclipse.jetty.server.Server.handle(Server.java:499)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:258)

at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.lang.Thread.run(Thread.java:748)

This post has been answered by thatJeffSmith-Oracle on Oct 4 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Nov 5 2017
Added on Oct 4 2017
3 comments
604 views