10 Replies Latest reply on Apr 25, 2005 5:31 PM by Maciej Leszczynski

    WebDav problem on Linux

    Viet Master

      the CMS service should start before that the servlet of the CMS webdav access.

      could you go in the JMX console and tell the status of the service porta:service=CMS, i.e the value of the StateString attribute.

        • 1. Re: WebDav problem on Linux
          Maciej Leszczynski Newbie

          "StateString" is "Registered"

          • 2. Re: WebDav problem on Linux
            Viet Master

            something prevents the service to start on your installation perhaps it is the database ?

            could you tell me the status of the mbean :

            jboss.jca:service=DataSourceBinding,name=PortalDS

            • 3. Re: WebDav problem on Linux
              Maciej Leszczynski Newbie

              PortalDS's "StateString" is "Started" and login is ok (some portlets which needs login work ok)

              • 4. Re: WebDav problem on Linux
                Roy Russo Master

                Is it only the frontend of the CMS thats not working? What do you see in the adminCMSPortlet?

                • 5. Re: WebDav problem on Linux
                  Maciej Leszczynski Newbie

                   

                  "roy.russo@jboss.com" wrote:
                  Is it only the frontend of the CMS thats not working? What do you see in the adminCMSPortlet?

                  adminCMSPortlet is blank, everything else seems to work ok - everything what do not use webdav. I have some other portlets written on my own and those portlets are also blank (if I'm logged in).

                  • 6. Re: WebDav problem on Linux
                    Maciej Leszczynski Newbie

                    full stack trace when calling adminCMSPortlet first time:

                    [org.jboss.portal.core.impl.preferences.MappedPreferenceStore] Preference set not found for instance.portal.AdminCMSPortlet.AdminCMSPortletInstance
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (0,instance)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child instance
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (1,portal)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child portal
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (2,AdminCMSPortlet)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child AdminCMSPortlet
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (3,AdminCMSPortletInstance)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child AdminCMSPortletInstance
                    [org.jboss.web.localhost.Engine] StandardContext[/webdav]webdav: Could not initialize domain
                    org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (No such file or directory)
                    at org.apache.slide.common.Domain.selfInit(Domain.java:783)
                    at org.apache.slide.common.Domain.accessNamespace(Domain.java:234)
                    at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:263)
                    at javax.servlet.GenericServlet.init(GenericServlet.java:211)
                    at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:195)
                    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
                    at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:687)
                    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:144)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
                    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
                    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
                    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
                    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
                    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
                    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
                    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
                    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
                    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
                    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
                    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
                    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
                    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
                    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
                    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
                    at java.lang.Thread.run(Thread.java:534)
                    [org.jboss.web.localhost.Engine] StandardContext[/webdav]Marking servlet webdav as unavailable

                    and next times:
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceStore] Preference set not found for instance.portal.AdminCMSPortlet.AdminCMSPortletInstance
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (0,instance)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child instance
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (1,portal)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child portal
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (2,AdminCMSPortlet)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child AdminCMSPortlet
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Using for 1/ name (3,AdminCMSPortletInstance)
                    [org.jboss.portal.core.impl.preferences.MappedPreferenceSet] Found for 1/ child AdminCMSPortletInstance
                    [org.jboss.web.localhost.Engine] StandardWrapperValve[webdav]: Servlet webdav is currently unavailable

                    • 7. Re: WebDav problem on Linux
                      Maciej Leszczynski Newbie

                      Hello again,
                      do you need any other info which may be helpful with this problem?
                      Thanks.

                      • 8. Re: WebDav problem on Linux
                        Maciej Leszczynski Newbie

                        When I'm trying to invoke ip:8080/webdav on linux I have following exception:

                        [org.jboss.web.localhost.Engine] StandardWrapperValve[webdav]: Servlet webdav is currently unavailable
                        [org.jboss.portal.server.impl.invocation.InvocationImpl] Incoming request with id null
                        [org.jboss.portal.core.invocation.ContentTypeInterceptor] Found markup=html_web_4_0, ua=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322), devicedID=goodaccess_ver1_submsiepocketpc
                        [org.jboss.portal.core.invocation.ContentTypeInterceptor] Found mimeType type text/html for markup=html_web_4_0
                        [org.jboss.portal.server.servlet.CommandServlet] Exception in command invocation
                        org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (No such file or directory)
                        at org.apache.slide.common.Domain.selfInit(Domain.java:783)
                        at org.apache.slide.common.Domain.getDefaultNamespace(Domain.java:213)
                        at org.jboss.portal.core.portlet.cms.CMSPortlet.getNAT(CMSPortlet.java:292)
                        at org.jboss.portal.core.portlet.cms.CMSPortlet.processAction(CMSPortlet.java:145)
                        at org.jboss.portlet.JBossPortlet.processAction(JBossPortlet.java:228)
                        at org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeActio

                        • 9. Re: WebDav problem on Linux
                          Maciej Leszczynski Newbie

                          I think this is the reason why CMS is not starting:

                          [org.jboss.system.ServiceCreator] Created bean: portal:service=CMS
                          [org.jboss.system.ServiceController] recording that portal:service=CMS depends on jboss.cache:service=InvalidationManager
                          [org.jboss.system.ServiceConfigurator] considering InvalidationManagerName with object name jboss.cache:service=InvalidationManager
                          [org.jboss.system.ServiceConfigurator] GroupName set to cms in portal:service=CMS
                          [org.jboss.system.ServiceConfigurator] Config set to [slide: null] in portal:service=CMS
                          [org.jboss.system.ServiceController] Creating service portal:service=CMS
                          [org.jboss.system.ServiceController] waiting in create of portal:service=CMS waiting on jboss.cache:service=InvalidationManager

                          • 10. Re: WebDav problem on Linux
                            Maciej Leszczynski Newbie

                            yes, that's it: missing "cache-invalidation-service.xml" in server\default\deploy

                            thank you for your time.