Symptom 1: When running a Baseline Index in Endeca 3.1.1, the MDEX server(s) do appear to be updated, but several errors appear in the console output, the first of which is:
[05.29.13 14:06:10] INFO: Pushing authoring content to dgraph: AuthoringDgraph [05.29.13 14:06:10] SEVERE: null Occurred while executing line 5 of valid BeanShell script: [[ 2| 3| compId = invokingObject.getElementId(); 4| log.info("Publishing Workbench 'authoring' configuration to MDEX '" + compId + "'"); 5| IFCR.pushAuthoringContentToDgraphById(compId); 6| 7| ]] [05.29.13 14:06:10] WARNING: Caught an exception while executing post-startup script for server component 'AuthoringDgraph'. Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script. Caused by java.lang.NullPointerException com.endeca.soleng.eac.toolkit.utility.IFCRUtility extractIfcrErrorMessage – null
Symptom 2: Running the control/promote_content.sh script fails with a similar error.
Symptom 3: Trying to add a new content item in the Endeca Workbench Rule Manager fails with the error “Last attempt to publish to the MDEX Engine failed”. If the mouse cursor is hovered over the error message, a tooltip appears with an additional error message: “com.endeca.ifcr.publish.impl.PublishException: Failed to publish to the following dgraphs: [dgraph url]”.
Solution: This started happening for my new Endeca application after I changed the password for the Endeca Workbench “admin” user to something other than the default value of “admin”.
Setting the correct (updated) password for the admin user in the application’s config/script/WorkbenchConfig.xml file resolved the issue.
Credit to Dan O. from Thanx Media for getting this issue tracked down. Thanks Dan!