Ok guys, I finally figure out the reason.
It's because we introduced logback from one of our internal packages, so
Knox was using logback instead of log4j underlying, and that's why no
matter how we modify gateway-log4j.properties, nothing changed. By simply
removing that package, Knox is using
Thank you Sandeep for the quick reply. I created the new class and modified
services.xml for yarnui to point to it.
I could see the class being loaded in the logs but the url encoding is the
same, which tells me that the url is not passing through the new class.
Here is the dispatch tag from
You can extend RMUIHaDispatch class and override getDispatchUrl() method
from URLDecodingDispatch
Best,
Sandeep
On Thu, Sep 6, 2018 at 2:28 PM Theyaa Matti wrote:
> Yes I am using HA for resource manager and in that case what should I do
> to the fix this issue?
>
> Best,
>
> Theyaa.
>
>
> On
Yes I am using HA for resource manager and in that case what should I do to
the fix this issue?
Best,
Theyaa.
On Thu, Sep 6, 2018 at 2:24 PM Sandeep Moré wrote:
> Are you using HA setup ? in which case org.apache.
> hadoop.gateway.rm.dispatch.RMUIHaDispatch dispatch will be used.
>
> On Thu,
Are you using HA setup ? in which case org.apache.
hadoop.gateway.rm.dispatch.RMUIHaDispatch dispatch will be used.
On Thu, Sep 6, 2018 at 2:19 PM Theyaa Matti wrote:
> I created the class as follows:
>
> package org.apache.knox.gateway.dispatch;
>
> import
I created the class as follows:
package org.apache.knox.gateway.dispatch;
import javax.servlet.http.HttpServletRequest;
import java.net.URI;
import java.net.URLDecoder;
import org.apache.hadoop.gateway.dispatch.DefaultDispatch;
/**
* Dispatch which decodes the outgoing URLs (to services).
*
That should be a good idea, but I still have an issue with adding the
custom dispatch to the yarnui service.xml. I already have an existing class
there
Should I replace the DefaultDispatch or I can have more than one there?
Regards,
On Tue, Sep 4, 2018 at 10:14 PM Dhruv Goyal