Connection unable to determine response code from navigation engine. Check MDEX Logs and specified query parameters – ATG Endeca

While trying to access an endeca page, I am getting below exception in my server logs. What could be wrong ? –

15:35:18,269 ERROR [atg.endeca.assembler.AssemblerTools] (http-localhost/127.0.0.1:11080-2) JSESSIONID:65ssVfUFPD0ydNZ5f0HyX8Dz.localhost, PROFILE_ID:2149866607, APACHE_UNIQUE_ID:null, SOURCE_IP:null, Client-Source-IP:null, A problem occurred assembling requested content. Response from the assembler was {previewModuleUrl=http://localhost:8006/preview, @type=ContentSlot, atg:currentSiteProductionURL=null, ruleLimit=1, @error=com.endeca.infront.content.ContentException: com.endeca.navigation.ENEConnectionException: Connection unable to determine response code from navigation engine. Check MDEX Logs and specified query parameters. , contentCollection=/content/COM/Contents/MyContent}

15:35:18,269 ERROR [atg.endeca.assembler.droplet.InvokeAssembler] (http-localhost/127.0.0.1:11080-2) JSESSIONID:65ssVfUFPD0ydNZ5f0HyX8Dz.localhost, PROFILE_ID:2149866607, APACHE_UNIQUE_ID:null, SOURCE_IP:null, Client-Source-IP:null, A problem occurred assembling the content for content item /content/COM/Contents/MyContent. The response received was {previewModuleUrl=http://localhost:8006/preview, @type=ContentSlot, atg:currentSiteProductionURL=null, ruleLimit=1, @error=com.endeca.infront.content.ContentException: com.endeca.navigation.ENEConnectionException: Connection unable to determine response code from navigation engine. Check MDEX Logs and specified query parameters. , contentCollection=/content/COM/Contents/MyContent}. Servicing the error open parameter.

Asked

(0) Votes

1 Answers

  • This is typically caused when connecting to intermediate servers like an MDEX Load Balancer (VIP) . To confirm that the issue is with VIP, go ahead and update the assemblerApplicationConfiguration of one of your page servers to point directly to the MDEX instead of VIP.

    If this error goes away, we know there is an issue with the VIP requests. Work with the server administrator to fix the VIP configurations.

    Typical issues are –

    VIP is not setup/enabled to use HTTPs
    The Health monitor for MDEX is not setup correctly in VIP

    Answered 2 months ago