Re: [jetty-users] org.eclipse.jetty.servlet.DefaultServlet: "d != java.l

[Jan Bartel <janb@xxxxxxxxxxx>]

Fixed bug in jetty-9.2.x branch and will merge it across to jetty-9.3.

Jan

On 19 September 2014 10:26, Jan Bartel <janb@xxxxxxxxxxx> wrote:
> Yes, its a bug in ResourceCache.Content. In fact I thought I'd fixed
> that recently, but must have accidentally backed it out as part of
> removing some printlns.
>
> Opened bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=444547
>
> Jan
>
> On 19 September 2014 00:41, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
>> Sounds like a bug.
>> But in the meantime, disable the debug logging of DefaultServlet in your
>> logging configuration.
>> That will avoid that specific warning/error for you.
>>
>> --
>> Joakim Erdfelt <joakim@xxxxxxxxxxx>
>> webtide.com - intalio.com/jetty
>> Expert advice, services and support from from the Jetty & CometD experts
>> eclipse.org/jetty - cometd.org
>>
>> On Thu, Sep 18, 2014 at 7:08 AM, Vullhorst, Wolfgang <wvullhorst@xxxxxxxxxx>
>> wrote:
>>>
>>> Hi all,
>>>
>>>
>>>
>>>   I installed Jetty 9.2.3.v20140905 and deployed my servlets successfully.
>>>
>>>
>>>
>>> When requesting Javascript or binary data I receive the following message:
>>>
>>>
>>>
>>> 18.09 13:30:53.176  WARN (qtp15683161-17 -
>>> /cetis-ssml/nextgendialog/dlgnextgen/CH/images/common/header.gif?sessionId=ky8pOZB)
>>> [servlet.DefaultServlet] EXCEPTION
>>>
>>> java.util.IllegalFormatConversionException: d != java.lang.String
>>>
>>>       ...
>>>
>>>       at java.util.Formatter.format(Formatter.java:2520)
>>>
>>>       at java.util.Formatter.format(Formatter.java:2455)
>>>
>>>       at java.lang.String.format(String.java:2927)
>>>
>>>       at
>>> org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:497)
>>>
>>>
>>>
>>> The source code of DefaultServlet looks like this at lines 496,497:
>>>
>>>
>>>
>>> if (LOG.isDebugEnabled())
>>>
>>> LOG.debug(String.format("uri=%s, resource=%s,
>>> content=%s",request.getRequestURI(),resource,content));
>>>
>>>
>>>
>>> When I change the Log level in my configuration to INFO, the problem
>>> logically disappears.
>>>
>>>
>>>
>>> My question is:
>>>
>>> Is this a bug in the DefaultServlet implementation (the code was modified
>>> at this point fom 9.2.2 to 9.2.3) or do I miss something in my deployment
>>> (e.g. content types)?
>>>
>>>
>>>
>>> Freundliche Grüße / Kind regards
>>> Wolfgang Vullhorst
>>>
>>>
>>> _______________________________________________
>>> jetty-users mailing list
>>> jetty-users@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>>
>>
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
> --
> Jan Bartel <janb@xxxxxxxxxxx>
> www.webtide.com
> 'Expert Jetty/CometD developer,production,operations advice'



-- 
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
'Expert Jetty/CometD developer,production,operations advice'