Strange stack trace in logs

[Pills]

Hello,

I've put my wicket app in production for a bit more than a month now.
Yesterday, I tried to see what is in the logs. I see a lot of stacktrace
like this:

org.apache.wicket.WicketRuntimeException: Internal error parsing
wicket:interface = :57:container1:link1
    at
org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:583)
    at
org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:554)
    at
org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.decode(WebRequestCodingStrategy.java:199)
    at org.apache.wicket.Request.getRequestParameters(Request.java:171)
    at org.apache.wicket.RequestCycle.step(RequestCycle.java:1224)
    at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1316)
    at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
    at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:354)
    at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
    at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
    at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
    at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
    at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
    at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
    at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
    at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
    at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
    at java.lang.Thread.run(Unknown Source)

But I'm not able to reproduce it...

My Wicket code looks like this:

1- DefaultPage.java
public abstract class DefaultPage extends WebPage {
    public DefaultPage() {
        WebMarkupContainer container1=...;
        Link link1 = ...;
        link1.add(new Image("link1", new
ResourceReference(DefaultPage.class, "link1.png",
getSession().getLocale(), null)));
    }
}

2- Index.java
public class Index extends DefaultPage { ... }


May it be a back button issue? Must I put some code on the
onBeforeRender to refresh the resource references?

Any idea are welcome ;)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Pills]

Nobody ever saw stack traces like this on theire logs?

It's strange, I really have a lot of them... About 2MB only with things
like that... And I haven't any idea on what's going on (I'm not able to
reproduce it on my side)

Piller Sébastien a écrit :

> Hello,
>
> I've put my wicket app in production for a bit more than a month now.
> Yesterday, I tried to see what is in the logs. I see a lot of
> stacktrace like this:
>
> org.apache.wicket.WicketRuntimeException: Internal error parsing
> wicket:interface = :57:container1:link1
>    at
> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:583)
>
>    at
> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:554)
>
>    at
> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.decode(WebRequestCodingStrategy.java:199)
>
>    at org.apache.wicket.Request.getRequestParameters(Request.java:171)
>    at org.apache.wicket.RequestCycle.step(RequestCycle.java:1224)
>    at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1316)
>    at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
>    at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:354)
>    at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
>
>    at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>
>    at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>
>    at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>
>    at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>
>    at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>
>    at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>
>    at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>
>    at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>
>    at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
>
>    at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>
>    at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>
>    at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>
>    at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
>
>    at java.lang.Thread.run(Unknown Source)
>
> But I'm not able to reproduce it...
>
> My Wicket code looks like this:
>
> 1- DefaultPage.java
> public abstract class DefaultPage extends WebPage {
>    public DefaultPage() {
>        WebMarkupContainer container1=...;
>        Link link1 = ...;
>        link1.add(new Image("link1", new
> ResourceReference(DefaultPage.class, "link1.png",
> getSession().getLocale(), null)));
>    }
> }
>
> 2- Index.java
> public class Index extends DefaultPage { ... }
>
>
> May it be a back button issue? Must I put some code on the
> onBeforeRender to refresh the resource references?
>
> Any idea are welcome ;)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Martijn Dashorst]

usually this is from users that copy/paste incomplete url's from other
users, or people tampering with urls

Martijn

On Thu, Jul 3, 2008 at 8:58 AM, Piller Sébastien <pills@...> wrote:

> Nobody ever saw stack traces like this on theire logs?
>
> It's strange, I really have a lot of them... About 2MB only with things like
> that... And I haven't any idea on what's going on (I'm not able to reproduce
> it on my side)
>
> Piller Sébastien a écrit :
>>
>> Hello,
>>
>> I've put my wicket app in production for a bit more than a month now.
>> Yesterday, I tried to see what is in the logs. I see a lot of stacktrace
>> like this:
>>
>> org.apache.wicket.WicketRuntimeException: Internal error parsing
>> wicket:interface = :57:container1:link1
>>   at
>> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:583)
>>   at
>> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:554)
>>   at
>> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.decode(WebRequestCodingStrategy.java:199)
>>   at org.apache.wicket.Request.getRequestParameters(Request.java:171)
>>   at org.apache.wicket.RequestCycle.step(RequestCycle.java:1224)
>>   at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1316)
>>   at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
>>   at
>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:354)
>>   at
>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
>>   at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>>   at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>   at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>>   at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>>   at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>   at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>>   at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>>   at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>>   at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
>>   at
>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>>   at
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>>   at
>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>>   at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
>>   at java.lang.Thread.run(Unknown Source)
>>
>> But I'm not able to reproduce it...
>>
>> My Wicket code looks like this:
>>
>> 1- DefaultPage.java
>> public abstract class DefaultPage extends WebPage {
>>   public DefaultPage() {
>>       WebMarkupContainer container1=...;
>>       Link link1 = ...;
>>       link1.add(new Image("link1", new
>> ResourceReference(DefaultPage.class, "link1.png", getSession().getLocale(),
>> null)));
>>   }
>> }
>>
>> 2- Index.java
>> public class Index extends DefaultPage { ... }
>>
>>
>> May it be a back button issue? Must I put some code on the onBeforeRender
>> to refresh the resource references?
>>
>> Any idea are welcome ;)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Pills]

Thank you for your answer... Unfortunately, it doesn't seem to be the
only reason... I've got some stack trace speaking about css and js

java.lang.IllegalStateException: URL fragment has unmatched key/value pair: ../../resources/mypack.MyClass/script.js
        at org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)
        at org.apache.wicket.request.target.coding.PackageRequestTargetUrlCodingStrategy.decode(PackageRequestTargetUrlCodingStrategy.java:103)

I think the user didn't try anything with the js scripts... And I really
have a lot of traces...


Martijn Dashorst a écrit :
> usually this is from users that copy/paste incomplete url's from other
> users, or people tampering with urls
>
> Martijn
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jan Stette-2]

I've also had reports of a similar problem.  The logs I have show references
to css files, and I'm sure that the user didn't modify any URLs:

ERROR 11:52:37,426 [btpool1-5] wicket.RequestCycle URL fragment has
unmatched key/value pair:
wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css

java.lang.IllegalStateException: URL fragment has unmatched key/value pair:
wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css

at
org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)

at
org.apache.wicket.request.target.coding.BookmarkablePageRequestTargetUrlCodingStrategy.decode(BookmarkablePageRequestTargetUrlCodingStrategy.java:76)

<...>

I'm trying to reproduce/debug this at the moment, I'll post more details if
I find anything out.  (We're on Wicket 1.3.3 by the way)

Jan


2008/7/4 Piller Sébastien <pills@...>:

> Thank you for your answer... Unfortunately, it doesn't seem to be the only
> reason... I've got some stack trace speaking about css and js
>
> java.lang.IllegalStateException: URL fragment has unmatched key/value pair:
> ../../resources/mypack.MyClass/script.js
>        at
> org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)
>        at
> org.apache.wicket.request.target.coding.PackageRequestTargetUrlCodingStrategy.decode(PackageRequestTargetUrlCodingStrategy.java:103)
>
> I think the user didn't try anything with the js scripts... And I really
> have a lot of traces...
>
>
> Martijn Dashorst a écrit :
>
>> usually this is from users that copy/paste incomplete url's from other
>> users, or people tampering with urls
>>
>> Martijn
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[Pills]

Thank you Jan! I'm glad not to be alone with this strange problem

On our side, we're using wicket 1.3.1 with the same behavior.

Jan Stette a écrit :

> I've also had reports of a similar problem.  The logs I have show references
> to css files, and I'm sure that the user didn't modify any URLs:
>
> ERROR 11:52:37,426 [btpool1-5] wicket.RequestCycle URL fragment has
> unmatched key/value pair:
> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>
> java.lang.IllegalStateException: URL fragment has unmatched key/value pair:
> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>
> at
> org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)
>
> at
> org.apache.wicket.request.target.coding.BookmarkablePageRequestTargetUrlCodingStrategy.decode(BookmarkablePageRequestTargetUrlCodingStrategy.java:76)
>
> <...>
>
> I'm trying to reproduce/debug this at the moment, I'll post more details if
> I find anything out.  (We're on Wicket 1.3.3 by the way)
>
> Jan
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jan Stette-2]

I can actually reproduce this problem now, with our application.  I don't
know if this is the only way to make it happen, but it occurs when right
clicking a link and selecting "open in new tab", but only where the
resulting page contains a specific type of component that includes the css
file mentioned in the log trace.

Looking at it in the debugger, the request looks like:

[method = GET, protocol = HTTP/1.1, requestURL =
http://localhost:8081/xxxx/home/wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css,
contentType = null, contentLength = -1, contextPath = , pathInfo =
/home/wicket:interface/:2:1:INewBrowserWindowListener::/CollectionNodeComponent.css,
requestURI =
/xxxx/home/wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css,
servletPath = /xxxx, pathTranslated = null]

AbstractRequestTargetUrlCodingStrategy.decodeParameters tries to decode the
parametersFragment:
"wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css"

which splits into 3 parts:
    wicket:interface
    %3A2%3A1%3AINewBrowserWindowListener%3A%3A
    CollectionNodeComponent.css

Which causes the error as it's an odd number of items.

So I guess the question is why the path for this request looks like it does
- maybe someone who knows the internals of Wicket can shed some light on
this?

Regards,
Jan


2008/7/4 Piller Sébastien <pills@...>:

> Thank you Jan! I'm glad not to be alone with this strange problem
>
> On our side, we're using wicket 1.3.1 with the same behavior.
>
> Jan Stette a écrit :
>
>> I've also had reports of a similar problem.  The logs I have show
>> references
>> to css files, and I'm sure that the user didn't modify any URLs:
>>
>> ERROR 11:52:37,426 [btpool1-5] wicket.RequestCycle URL fragment has
>> unmatched key/value pair:
>>
>> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>>
>> java.lang.IllegalStateException: URL fragment has unmatched key/value
>> pair:
>>
>> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>>
>> at
>>
>> org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)
>>
>> at
>>
>> org.apache.wicket.request.target.coding.BookmarkablePageRequestTargetUrlCodingStrategy.decode(BookmarkablePageRequestTargetUrlCodingStrategy.java:76)
>>
>> <...>
>>
>> I'm trying to reproduce/debug this at the moment, I'll post more details
>> if
>> I find anything out.  (We're on Wicket 1.3.3 by the way)
>>
>> Jan
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

[Jan Stette-2]

So, are there anyone with inside knowledge of Wicket who could shed some
light on these exceptions?

Thanks,
Jan


2008/7/4 Jan Stette <jan.stette@...>:

> I can actually reproduce this problem now, with our application.  I don't
> know if this is the only way to make it happen, but it occurs when right
> clicking a link and selecting "open in new tab", but only where the
> resulting page contains a specific type of component that includes the css
> file mentioned in the log trace.
>
> Looking at it in the debugger, the request looks like:
>
> [method = GET, protocol = HTTP/1.1, requestURL =
> http://localhost:8081/xxxx/home/wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css,
> contentType = null, contentLength = -1, contextPath = , pathInfo =
> /home/wicket:interface/:2:1:INewBrowserWindowListener::/CollectionNodeComponent.css,
> requestURI =
> /xxxx/home/wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css,
> servletPath = /xxxx, pathTranslated = null]
>
> AbstractRequestTargetUrlCodingStrategy.decodeParameters tries to decode the
> parametersFragment:
>
> "wicket:interface/%3A2%3A1%3AINewBrowserWindowListener%3A%3A/CollectionNodeComponent.css"
>
> which splits into 3 parts:
>     wicket:interface
>     %3A2%3A1%3AINewBrowserWindowListener%3A%3A
>     CollectionNodeComponent.css
>
> Which causes the error as it's an odd number of items.
>
> So I guess the question is why the path for this request looks like it does
> - maybe someone who knows the internals of Wicket can shed some light on
> this?
>
> Regards,
> Jan
>
>
> 2008/7/4 Piller Sébastien <pills@...>:
>
>> Thank you Jan! I'm glad not to be alone with this strange problem
>>
>>
>> On our side, we're using wicket 1.3.1 with the same behavior.
>>
>> Jan Stette a écrit :
>>
>>> I've also had reports of a similar problem.  The logs I have show
>>> references
>>> to css files, and I'm sure that the user didn't modify any URLs:
>>>
>>> ERROR 11:52:37,426 [btpool1-5] wicket.RequestCycle URL fragment has
>>> unmatched key/value pair:
>>>
>>> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>>>
>>> java.lang.IllegalStateException: URL fragment has unmatched key/value
>>> pair:
>>>
>>> wicket:interface/xxxx_0_1214298450782%3A0%3A3%3AINewBrowserWindowListener%3A%3A/wicket:pageMapName/xxxx_0_1214298450782/CollectionNodeComponent.css
>>>
>>> at
>>>
>>> org.apache.wicket.request.target.coding.AbstractRequestTargetUrlCodingStrategy.decodeParameters(AbstractRequestTargetUrlCodingStrategy.java:174)
>>>
>>> at
>>>
>>> org.apache.wicket.request.target.coding.BookmarkablePageRequestTargetUrlCodingStrategy.decode(BookmarkablePageRequestTargetUrlCodingStrategy.java:76)
>>>
>>> <...>
>>>
>>> I'm trying to reproduce/debug this at the moment, I'll post more details
>>> if
>>> I find anything out.  (We're on Wicket 1.3.3 by the way)
>>>
>>> Jan
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>

[Pills]

Jan Stette a écrit :
>> it occurs when right clicking a link and selecting "open in new tab", but only where the
>> resulting page contains a specific type of component that includes the css
>> file mentioned in the log trace.
On my side, it seems not to be the reason... Does it happen with every
browser?

I tried Opera, Firefox and IE, opened all my links in new tabs, and
however, was unable to reproduce it...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...