Link Builder Editor - Published Pages URI's Cannot Be Resolved
(Doc ID 2436499.1)
Last updated on JULY 08, 2020
Applies to:
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.3 and laterInformation in this document applies to any platform.
Symptoms
On : 11.3 version, Customer Experience (Xmgr, Assembler, Workbench, Application Development)
Link Builder Editor - published pages URI's cannot be resolved
26085872 (OCxmgrLinux_11.3.0_p0.12) Patch Set has changed the functioning of Link Builder Editor pages select input.
After applying this patch, the vailable URIs have contained an additional prefix with ATG site name.
'/sites/<app_name>/pages/homeSite/id-bestellung' where '/site/<app_name>' is mentioned above prefix.
ATG application is not able to resolve modified URIs:
When link type is changed from "Page" to "Enter URL" and page URL is entered manually without prefix ('/sites/<app_name>/pages/homeSite/id-bestellung'), ATG is correctly resolving page paths as it was before applying patch 26085872.
ERROR
-----------------------
2018-06-28 13:45:29,256 ERROR [nucleusNamespace.de.dtag.ps.storefront.endeca.assembler.cartridge.handler.MegaMenuDirectLinkHandler] (default task-115) null: com.endeca.infront.content.ContentException: The following content URI could not be resolved: /sites/<app_name>/pages/homeSite/id-bestellung
at com.endeca.infront.cartridge.model.LinkBuilder.fillInPaths(LinkBuilder.java:346)
at com.endeca.infront.cartridge.model.LinkBuilder.createAction(LinkBuilder.java:272)
at com.endeca.infront.cartridge.model.LinkBuilder.createAction(LinkBuilder.java:335)
at de.dtag.ps.storefront.endeca.assembler.cartridge.handler.impl.MegaMenuDirectLinkHandler.createLinkAction(MegaMenuDirectLinkHandler.java:91)
at de.dtag.ps.storefront.endeca.assembler.cartridge.handler.impl.MegaMenuDirectLinkHandler.recursiveCreateLinkAction(MegaMenuDirectLinkHandler.java:48)
at de.dtag.ps.storefront.endeca.assembler.cartridge.handler.impl.MegaMenuDirectLinkHandler.handleProcess(MegaMenuDirectLinkHandler.java:38)
at de.dtag.ps.storefront.endeca.assembler.cartridge.handler.AbstractCartridgeHandler.process(AbstractCartridgeHandler.java:35)
at com.endeca.infront.assembler.support.AbstractAssembler$Processor$ProcessPass.visit(AbstractAssembler.java:278)
The ifcr logs shows the following relevant errors:
03.07.2018 13:44:11.240 *WARN* [FelixStartLevel] com.endeca.ifcr.services.PasswordHistoryServiceImpl Couldn't clean up history node as it doesn't exist
03.07.2018 13:45:17.827 *ERROR* [127.0.0.1 [1530618317605] GET /ifcr/sites/Partnershop.allUserSegments.1.json HTTP/1.1] com.endeca.ifcr.xmgr.usersegments.AtgProfileGroupService Connection refused (Connection refused)
03.07.2018 13:45:17.854 *ERROR* [127.0.0.1 [1530618317605] GET /ifcr/sites/Partnershop.allUserSegments.1.json HTTP/1.1] com.endeca.ifcr.xmgr.usersegments.AtgProfileGroupService Unable to open URL connection to malformed URL: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
....
03.07.2018 13:45:25.460 *ERROR* [127.0.0.1 [1530618325405] GET /ifcr/sites/Partnershop.allUserSegments.1.json HTTP/1.1] com.endeca.ifcr.xmgr.usersegments.AtgProfileGroupService Connection refused (Connection refused)
03.07.2018 13:45:25.461 *ERROR* [127.0.0.1 [1530618325405] GET /ifcr/sites/Partnershop.allUserSegments.1.json HTTP/1.1] com.endeca.ifcr.xmgr.usersegments.AtgProfileGroupService Unable to open URL connection to malformed URL: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:20
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply the latest T&F set of patches
2. From Experience Manager, observe that the URI contain a new prefix
3. Observe the errors from ATG logs, which show that the new URI cannot be resolved
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
NA
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |