UEM with JAWR returns a 404
We ran into a 404 error trying to implement UEM on an application. We learned that the application uses JAWR to bundle and serve all their javascript files. Where all requests for URL patterns of “*.js” are mapped to the JAWR servlet. Because of this the JAWR does not know about the dynatrace file so sends a 404. Has anyone had any experience in implementing UEM with JAWR to make this work?
Thanks, David
Thanks Markus, yes I've had the active UEM sensor on during the test. I think the app owners assumption was that because they got a 404 that the JAWR servlet could not find th javascript agent. But if the JAWR servlet is part of a chain then what they were throwing up was a red herring that should not be followed. So I will take your insight and dig in further with this. Thank you very much!
David
Hi Dave
What one would expect is that the net.jawr.web.servlet.JawrServlet gets instrumented by the UEM sensor and serves the JavaScript agent without resulting in a 404 error. In addition, the JawrServlet wouldn't even be the first servlet in the filter chain, therefore the request should be handled by a servlet that comes before in the chain. I also verified this in a local test.
A prerequisite is that the user experience sensor is set to "active", which is not the case in a new system profile. Is the user experience sensor set to "active" in your system profile? Otherwise, the request for the JavaScript agent wouldn't be handled and results in a 404 error.
Regards,
Markus
