[AAA-141] Servlet alias conflict with Dlux Created: 31/Jul/17 Updated: 21/Mar/19 Resolved: 01/Aug/17 |
|
| Status: | Resolved |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Daniel Malachovsky | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 8915 |
| Priority: | Highest |
| Description |
|
Hi, I received several emails from downstream projects, that Dlux bases UIs are broken in Nitrogen. After some investigation found this: Caused by: org.osgi.service.http.NamespaceException: alias: '/' is already in use in this or another context This error appears in Karaf log after feature:install odl-dlux-core. http:list command in karaf console pointed me to aaa project and aaa-shiro feature. In aaa/aaa-shiro/impl/pom.xml found this: <Web-ContextPath>/</Web-ContextPath> I'm not familiar with aaa project and Jetty at all, so don't know if this is valid configuration change, but there is a conflict and we should resolve it somehow. Thanks |
| Comments |
| Comment by Daniel Malachovsky [ 31/Jul/17 ] |
|
Attachment bug.txt has been added with description: Error message from Karaf log |
| Comment by Ryan Goulding [ 31/Jul/17 ] |
|
I think what we want will be closer to this: https://git.opendaylight.org/gerrit/#/c/60957/ still testing |
| Comment by Ryan Goulding [ 31/Jul/17 ] |
|
Final analysis: Both bundles try to own the root servlet context. Neither probably should. AAA backed off in the above patch, and dlux should do the same in the future. For now, its fine to keep it for backwards compatibility reasons. We should better document how this stuff works in the future. In general projects just rely on RESTCONF for web interaction, but these two projects are special circumstances/exceptions to the rules. This won't ever be caught at compile time with current jetty code unfortunately, and the CI test would take a while to perform so we need to just document better for now. |