-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
%
-
-
When a fabric profile that specifies a CXF endpoint is assigned to a container, and an HTTP gateway exists in the fabric, then sometimes the endpoint does not show up in the gateway's API list (on port 9000), even though it shows up in cxf:list-endpoints in the relevant container.
Sometimes, even when the endpoint does show up, it does not show up after a restart of the container. Sometimes refreshing the bundle that exposes the endpoint in that container makes it show up. The problem seems to affect 6.2.1 R1 and 6.2.1 R2, but perhaps not 6.2.1 GA.
There might be some connection with the changes made in the fix of ENTESB-4956.
- causes
-
ENTESB-5986 REST Endpoints are registered under /fabric/registry/clusters/apis/ws/ instead of ..apis/rest
- Closed
-
ENTESB-5925 cxf quickstarts log WARNs with fabric on Fuse
- Closed
- duplicates
-
ENTESB-3039 [HTTP Gateway] apis mapping rules don't work right after deployment
- Closed
- is caused by
-
ENTESB-4369 Standby Fuse container in active/standby configuration does not expose an SSH service since 6.2
- Closed
- is related to
-
ENTESB-6660 CXF endpoints not getting registered in Fabric registry / not exposed by HTTP Gateway
- Done
- relates to
-
ENTESB-5982 Gateway-Http sometimes does not keep Hawtio url in registry thus not able to redirect
- Closed