6 Replies Latest reply: Oct 30, 2012 10:37 AM by Stéphane RSS

    Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench

    DevReddy
      Hi ,

      I am getting the below error while connecting to Workbench.

      HTTP Status 404 -

      --------------------------------------------------------------------------------

      type Status report

      message

      description The requested resource () is not available.


      --------------------------------------------------------------------------------

      Apache Tomcat/6.0.20

      I have checked that both HTTP Service (8888) & Tools service (8006) services are running. Not sure what was the reason. Could some one help me?

      Thanks
      DEV
        • 1. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
          sabdelhalim
          Hi,
          I suppose everything went fine when you installed Experience Manager ...(were environment variables (path) set correctly after install ?)
          did you check in the \PlatformServices\Tools\Server\bin the content of the folder there are some configuration files there (check the setclasspath, set env)
          what release of E Manager is that ?
          did it work already ?
          did you run an intialize services ?
          hope that helps
          regards
          Saleh
          • 2. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
            Dan at Branchbird
            Reddy,

            What URL are you using to access Workbench? Do you see any errors in the workbench log file (/Endeca/Workbench/workspace/logs/catalina.<date_stamp>.log) ?

            Dan
            Branchbird
            • 3. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
              953835
              netstat -na | grep ":<port-you-are-trying-to-talk-to>"

              Do you see the word "LISTEN"?
              • 4. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
                Stéphane
                Hi,

                I've got the same problem, no way to display Workbench (http://localhost:8006)
                I saw that the "Endeca Tools Services" doesn't succeed to start.

                I've got in the catalina log:
                Oct 30, 2012 3:57:32 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
                +WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.+
                Oct 30, 2012 3:57:33 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
                +WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.+
                Oct 30, 2012 3:57:33 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
                +WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.+
                Oct 30, 2012 3:57:33 PM org.apache.coyote.http11.Http11Protocol init
                INFO: Initializing Coyote HTTP/1.1 on http-8006
                Oct 30, 2012 3:57:33 PM org.apache.catalina.startup.Catalina load
                INFO: Initialization processed in 2604 ms
                Oct 30, 2012 3:57:33 PM org.apache.catalina.core.StandardService start
                INFO: Starting service Standalone
                Oct 30, 2012 3:57:33 PM org.apache.catalina.core.StandardEngine start
                INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
                Oct 30, 2012 3:57:57 PM org.apache.coyote.http11.Http11Protocol start
                INFO: Starting Coyote HTTP/1.1 on http-8006
                Oct 30, 2012 3:57:57 PM org.apache.catalina.startup.Catalina start
                INFO: Server startup in 24127 ms
                Oct 30, 2012 3:57:57 PM org.apache.catalina.core.StandardServer await
                SEVERE: StandardServer.await: create[8084]:
                java.net.BindException: Address already in use: JVM_Bind
                +     at java.net.PlainSocketImpl.socketBind(Native Method)+
                +     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)+
                +     at java.net.ServerSocket.bind(ServerSocket.java:319)+
                +     at java.net.ServerSocket.<init>(ServerSocket.java:185)+
                +     at org.apache.catalina.core.StandardServer.await(StandardServer.java:373)+
                +     at org.apache.catalina.startup.Catalina.await(Catalina.java:647)+
                +     at org.apache.catalina.startup.Catalina.start(Catalina.java:607)+
                +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
                +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
                +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
                +     at java.lang.reflect.Method.invoke(Method.java:597)+
                +     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)+
                +     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)+
                Oct 30, 2012 3:57:57 PM org.apache.coyote.http11.Http11Protocol pause
                INFO: Pausing Coyote HTTP/1.1 on http-8006
                Oct 30, 2012 3:57:58 PM org.apache.catalina.core.StandardService stop
                INFO: Stopping service Standalone
                Oct 30, 2012 3:57:59 PM org.apache.coyote.http11.Http11Protocol destroy
                INFO: Stopping Coyote HTTP/1.1 on http-8006


                Someone got an idea?
                Thanks a lot,
                Stéphane

                ps: when I start the batch initialize_services, I also have an error:

                +[10.30.12 16:09:42] INFO: [ITLHost] Starting shell utility 'emgr_update_get_ws_settings'.+
                +[10.30.12 16:09:45] SEVERE: Utility 'emgr_update_get_ws_settings' failed. Refer to utility logs in [ENDECA_CONF]/logs/sh+
                ell on host ITLHost.
                Occurred while executing line 5 of valid BeanShell script:
                +[[+

                +2|+
                +3| if (ConfigManager.isWebStudioEnabled()) {+
                +4| log.info("Updating IAP Workbench configuration...");+
                +5| ConfigManager.updateWsConfig();+
                +6| log.info("Finished updating IAP Workbench.");+
                +7| }+
                +8|+

                +]]+

                +[10.30.12 16:09:45] SEVERE: Caught an exception while invoking method 'run' on object 'InitialSetup'. 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_get_ws_settings' failed. Refer to utility logs
                +in [ENDECA_CONF]/logs/shell on host ITLHost.+

                in logs/shell I've got:
                ERROR: Failed to get instance configuration from IAP Workbench.

                Edited by: Stéphane on 30 oct. 2012 08:10
                • 5. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
                  Dan at Branchbird
                  Stephane,

                  Workbench runs using an embedded version of Apache Tomcat. The ports that Apache Tomcat needs to start/stop are defined in \Endeca\Workbench\workspace\conf\server.xml. If you look in this file, you'll note that Workbench, as a web application running on Tomcat, is configured to grab port 8084 as its Shutdown port.

                  The error is occurring because another process on the server already has control of this port, 8084. Endeca's Platform Services also runs on Tomcat, but OOTB it is configured to use different ports than Workbench so there shouldn't be any port contention. I would investigate what other processes you have running and what ports they're using.

                  Thanks,
                  Dan
                  Branchbird.com
                  • 6. Re: Apache Tomcat/6.0.20 - HTTP Status 404 - error while connecting Workbench
                    Stéphane
                    You're right!!!
                    I have a McAffee Service running on port 8084.
                    I re-installed WorkBench changing shutdown port to 8085 and it's OK.

                    Thanks a lot!