6 Replies Latest reply: Nov 28, 2012 3:11 AM by 965290 RSS

    urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.

    965290
      Hi All,

      I can see below exception in the Baseline logs, when i have checked the [ENDECA_CONF]/logs/shell which says "RROR: Failed to set app config. Make sure you can connect to http://server1:8006." however i am able to login to the server1. and also merchandising workbench is working fine on server1. please suggest, this is happening on production server.

      [11.27.12 12:33:51] FINEST: Querying for status of utility emgr_update_set_post_forge_dims
      [11.27.12 12:33:51] SEVERE: Utility 'emgr_update_set_post_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
      Occurred while executing line 41 of valid BeanShell script:
      [[

      38| if (ConfigManager.isWebStudioEnabled()) {
      39| ConfigManager.cleanDirs();
      40| Forge.getPostForgeDimensions();
      41| ConfigManager.updateWsDimensions();
      42| }
      43|
      44| // archive state files, index

      ]]

      [11.27.12 12:33:51] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.

      Caused by java.lang.reflect.InvocationTargetException
      sun.reflect.NativeMethodAccessorImpl invoke0 - null
      Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
      com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
      Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
      com.endeca.soleng.eac.toolkit.utility.Utility run - Utility 'emgr_update_set_post_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.

      [11.27.12 12:33:51] FINE: Removing flag update_lock
      [11.27.12 12:33:51] INFO: Released lock 'update_lock'.
        • 1. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
          Dan at Branchbird
          Is your baseline running on a different server than "server1"? I wonder if the server where you baseline is executing can't "see" server1 because of DNS settings. For example, you might be able to get to http://server1:8006 from your laptop, but the server where the baseline is running can't see that URL because of DNS settings or something in the host file. Can you confirm that the server can see server1 by doing a "wget http://server1:8006" from the command line of the server where the baseline is running?

          HTH,
          Dan
          http://branchbird.com
          • 2. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
            965290
            Hi,

            Baseline update is running on the same server and also this issue comes into the appconfig.xml, where baseline script is written. Webstudio code is throwing the exception and also when i check the logs i can see the below exception in Catalina.log. This Catalina.log is for workbench,/app/endeca/Workbench/workspace/logs

            27-Nov-2012 13:50:33 org.apache.tomcat.util.http.Parameters processParameters
            WARNING: Parameters: Invalid chunk ignored.
            28-Nov-2012 05:54:30 org.apache.catalina.core.StandardWrapperValve invoke
            SEVERE: Servlet.service() for servlet setAppConfig threw exception
            java.lang.OutOfMemoryError: Java heap space
            28-Nov-2012 05:54:30 org.apache.catalina.core.ApplicationContext log
            SEVERE: Web Studio exception_


            I am remove the logs and hope, this will solve the issue.

            Regards,
            Diwaker Kalla
            • 3. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
              965290
              Hi,

              The issue is coming from the webstudio. It's throwing the exception while checking the webstudio object. when i check the logs for the workbench, it can see below exception, this is because of heap space memory.So need to clean up the space. Here, i can see exception "SEVERE: Web Studio exception"

              27-Nov-2012 13:50:33 org.apache.tomcat.util.http.Parameters processParameters
              WARNING: Parameters: Invalid chunk ignored.
              28-Nov-2012 05:54:30 org.apache.catalina.core.StandardWrapperValve invoke
              SEVERE: Servlet.service() for servlet setAppConfig threw exception
              java.lang.OutOfMemoryError: Java heap space
              28-Nov-2012 05:54:30 org.apache.catalina.core.ApplicationContext log
              SEVERE: Web Studio exception


              Regards,
              Diwaker Kalla
              • 4. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
                Pravin Chikhale
                You can increase the heap size for Workbench in setenv.sh.
                You will find this file in <Endeca_installation>/Workbench/<version>/server/bin directory,

                - Pravin.
                • 5. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
                  965290
                  Hi Pravin,

                  I have increased MaxPermSize from 128m to 1024m(JAVA_OPTS="-Xmx1024m -XX:MaxPermSize=1024m) however it's same exception.


                  28-Nov-2012 08:43:47 org.apache.catalina.core.StandardWrapperValve invoke
                  SEVERE: Servlet.service() for servlet setAppConfig threw exception
                  java.lang.OutOfMemoryError: Java heap space
                  28-Nov-2012 08:43:47 org.apache.catalina.core.ApplicationContext log
                  SEVERE: Web Studio exception
                  java.lang.OutOfMemoryError: Java heap space
                  28-Nov-2012 08:43:47 org.apache.catalina.core.ApplicationDispatcher invoke
                  SEVERE: Servlet.service() for servlet jsp threw exception
                  java.lang.NullPointerException


                  Diwaker
                  • 6. Re: urgent: partail update stoppd: emgr_update_set_post_forge_dims' failed.
                    965290
                    Yes, this is solved after increasing the size MaxPermSize to 1024 MB.Many Thanks Pravin