Hi Jordan,
The original problem was too many messages coming to log,
while you complain your application does not work when you
add the filter, right? What does your filter do exactly?
I also noticed Paul did not have the time to turn off the logging,
and i am not 100 % sure the logging should be controlled
by the tracing feature. Another possibility would be to only
log once per a web component and a request uri.
What do you think?
~Jakub
On 8.11.2011 18:35, Jordan Blay wrote:
> Hi!
>
> I have the exact same problem.
>
> I wrote my own logging servlet:
>
> <filter>
> <filter-name>RestLoggingFilter</filter-name>
> <filter-class>com.mine.filter.RestLoggingFilter</filter-class>
> </filter>
>
> <filter-mapping>
> <filter-name>RestLoggingFilter</filter-name>
> <servlet-name>Jersey Web Application</servlet-name>
> </filter-mapping>
>
> And I get the same message!
>
> The request is :
>
> http://myip:8080/mine/api/order/test/?pId=288888&pName=Default+products
>
> And it is not being processed.. How can I overcome this problem? I don't
> want to turn off the filter logging for these requests..
>
>
>
>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/Log-warnings-tp4280745p6975189.html
> Sent from the Jersey mailing list archive at Nabble.com.
>