topic 3.4.b 'Sorry, there seems to be a problem...' in Alfresco Archive

3.4.b 'Sorry, there seems to be a problem...'

dstannard — Thu, 04 Nov 2010 16:36:57 GMT

Hi,I'm having trouble getting Quick Start to respond. After installation & configuration I get the following apology when browsing to /wcmqs :"Sorry, there seems to be a problem with this part of the page. "I wonder if anyone can help me diagnose this?My Alfresco installation is 3.4.b (taken to

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Thu, 04 Nov 2010 16:43:23 GMT

Extra info.

If I now change the hostname referred to in the Quick Start Editorial space's metadata (in the share site) from localhost to myserver then the Quick Start site almost works - it now just refuses to allow admin/admin to log in and amend any content (the login dialog wont accept the details).

Sorry if this is all very longwinded, but I've tried to include as much info as I can.

Re: 3.4.b 'Sorry, there seems to be a problem...'

bremmington — Fri, 05 Nov 2010 17:32:31 GMT

Sorry for the delay in replying Dave - I've just returned from the DevCon in NYC.

The 3.4.b installer will have created the correct properties file. The location of this file is "shared/classes/alfresco/extension/wqsapi-custom.properties" rather than the location you mention. If this file has the correct values and you have edited the metadata of the "Quick Start Editorial" node as appropriate (host name and port number) then you will see the homepage of the WQS correctly. Note that the host name that you type into your browser must match the value of the host name property on the "Quick Start Editorial" folder.

Would you confirm that the homepage of the site is displaying?

With regards to logging in to the web editor to make changes, would you confirm that you chose a password of "admin" for your admin user when you ran the installer? Are those the credentials you use to log in to Share? Is the AWE webapp deployed in the same Tomcat instance as the repository webapp (alfresco.war) and the WQS webapp (wcmqs.war)?

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Mon, 08 Nov 2010 09:00:10 GMT

That's quite alright Brian, thanks for replying. I'll try to answer your questions:

The 3.4.b installer will have created the correct properties file. The location of this file is "shared/classes/alfresco/extension/wqsapi-custom.properties" rather than the location you mention.

Sorry, this was a typo - I am using wqsapi-custom.properties. It is currently configured as I described previously:
(/tomcat/shared/classes/alfresco/wqsapi-custom.properties)


wcmqs.api.alfresco=http://localhost:38080/alfresco
wcmqs.api.user=admin
wcmqs.api.password=admin
‍‍‍‍‍

If this file has the correct values and you have edited the metadata of the "Quick Start Editorial" node as appropriate (host name and port number) then you will see the homepage of the WQS correctly.

FYI - Here's my metadata for the quick start editorial node in the share site:


Host Name=localhost
Host Port=38080
web app context: wcmqs
isEditorial=true
Publish Target: Quick Start Live
‍‍‍‍‍‍‍

Note that the host name that you type into your browser must match the value of the host name property on the "Quick Start Editorial" folder.

Ah, here's I may be diverging - I've set the server up with "localhost" references and I'm hitting it across the WAN with a "http://myserver:38080/wcmqs".

However, if I remote-desktop to the server and try "http://localhost:38080/wcmqs" then still no joy.

Would you confirm that the homepage of the site is displaying?

You mean when I browse to "http://myserver:38080/wcmqs/" ?

No it does not. That's when I get "Sorry there seems to be a problem".

With regards to logging in to the web editor to make changes, would you confirm that you chose a password of "admin" for your admin user when you ran the installer?

Yes - admin/admin.

Are those the credentials you use to log in to Share?

Yes.

Is the AWE webapp deployed in the same Tomcat instance as the repository webapp (alfresco.war) and the WQS webapp (wcmqs.war)?

Yes.

Re: 3.4.b 'Sorry, there seems to be a problem...'

bremmington — Mon, 08 Nov 2010 09:38:28 GMT

That properties file is still not quite in the right place. It should be "shared/classes/alfresco/extension/wqsapi-custom.properties". However, this file should be created in the correct location by the installer, so if it isn't there then there is some kind of installation issue. With the currently nightly build I've not been able to find any problem of this kind.

Is anything appearing in the log files (alfresco.log or webquickstart.log)? The error that you originally posted is due to the host name of the request (myserver) not matching the host name configured in the repo (localhost). What happens when you make the request to localhost from a browser running on the server itself? Am I right in assuming that the wcmqs.war is deployed in the same Tomcat instance as alfresco.war?

If I now change the hostname referred to in the Quick Start Editorial space's metadata (in the share site) from localhost to myserver then the Quick Start site almost works - it now just refuses to allow admin/admin to log in and amend any content (the login dialog wont accept the details).

What does "almost works" mean here? It sounds like the page displays correctly but the login to the Web Editor fails - is that right?

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Wed, 17 Nov 2010 09:32:03 GMT

That properties file is still not quite in the right place. It should be "shared/classes/alfresco/extension/wqsapi-custom.properties"

Sorry, my bad, that's precisely where it is.

Am I right in assuming that the wcmqs.war is deployed in the same Tomcat instance as alfresco.war?

Yes, that is correct.

(Although it's probably hard to determine from my garbled instructions above, I actually just ran the service installer and changed port numbers when instructed.)

What does "almost works" mean here? It sounds like the page displays correctly but the login to the Web Editor fails - is that right?

Correct.

What happens when you make the request to localhost from a browser running on the server itself?

I remote desktop to the server and make a request to http://localhost:38080/wcmqs/


Error
Sorry, there seems to be a problem! Please try again later.
‍‍‍‍

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Wed, 17 Nov 2010 09:41:17 GMT

Log messages

Connecting to http://localhost:38080/wcmqs from the server itself…

(there's no errors/warnings in alfresco.log)

webquickstart.log:


09:38:32,447 DEBUG [org.alfresco.wcm.client.impl.SectionFactoryCmisImpl] About to run CMIS query: select  f.cmis:objectId, f.cmis:name, t.cm:title, t.cm:description, f.cmis:objectTypeId, f.cmis:parentId, f.ws:sectionConfig, f.ws:excludeFromNavigation, f.ws:topTags, f.ws:topTagCounts , o.ws:orderIndex as ord from ws:section as f join cm:titled as t on t.cmis:objectId = f.cmis:objectId join ws:ordered as o on o.cmis:objectId = f.cmis:objectId where (in_tree(f, 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') or f.cmis:objectId = 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') order by ord
09:38:32,540 DEBUG [org.alfresco.wcm.client.impl.SectionFactoryCmisImpl] About to run CMIS query: select  f.cmis:objectId, f.cmis:name, t.cm:title, t.cm:description, f.cmis:objectTypeId, f.cmis:parentId, f.ws:sectionConfig, f.ws:excludeFromNavigation, f.ws:topTags, f.ws:topTagCounts , o.ws:orderIndex as ord from ws:section as f join cm:titled as t on t.cmis:objectId = f.cmis:objectId join ws:ordered as o on o.cmis:objectId = f.cmis:objectId where (in_tree(f, 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') or f.cmis:objectId = 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') order by ord
09:38:32,587 DEBUG [org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver] Resolving exception from handler [org.alfresco.wcm.client.controller.GenericTemplateAssetController@f6169e]: org.alfresco.wcm.client.exception.PageNotFoundException
09:38:32,587 ERROR [org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver] org.alfresco.wcm.client.exception.PageNotFoundException
org.alfresco.wcm.client.exception.PageNotFoundException
   at org.alfresco.wcm.client.controller.GenericTemplateAssetController.handleRequestInternal(GenericTemplateAssetController.java:72)
   at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
   at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
   at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:771)
   at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:716)
   at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:647)
   at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:552)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
   at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
   at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
   at org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:213)
   at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:171)
   at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145)
   at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92)
   at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:381)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
   at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859)
   at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
   at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1555)
   at java.lang.Thread.run(Thread.java:619)
09:38:32,587 DEBUG [org.alfresco.wcm.client.impl.SectionFactoryCmisImpl] About to run CMIS query: select  f.cmis:objectId, f.cmis:name, t.cm:title, t.cm:description, f.cmis:objectTypeId, f.cmis:parentId, f.ws:sectionConfig, f.ws:excludeFromNavigation, f.ws:topTags, f.ws:topTagCounts , o.ws:orderIndex as ord from ws:section as f join cm:titled as t on t.cmis:objectId = f.cmis:objectId join ws:ordered as o on o.cmis:objectId = f.cmis:objectId where (in_tree(f, 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') or f.cmis:objectId = 'workspace://SpacesStore/8fb2bc2a-235a-4e25-aa60-bd32d788ee3e') order by ord
09:38:32,634 DEBUG [org.alfresco.wcm.client.interceptor.CmisSessionInterceptor] *** / 359ms
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Wed, 17 Nov 2010 09:59:03 GMT

Brian,

From what you are saying I think that I have the wrong thing in my "Quick Start Editorial" folder metadata.

I think I should change the host name from "localhost" to "myserver" (even though all components are running on the same server, so I would have expected localhost to be the correct entry 🙂

This change now enables me to see the demo wcmqs web site from my desktop PC, hooray!

Now, I try to edit one of the articles, logging in as admin/admin and it just redisplays the login box.

There are no errors in either log.

Re: 3.4.b 'Sorry, there seems to be a problem...'

bremmington — Wed, 17 Nov 2010 10:00:56 GMT

Sorry, I'm becoming slightly confused. Perhaps there is some confusion about how WQS resolves URLs. Does this part of the Dev Guide help at all: http://wiki.alfresco.com/wiki/Web_Quick_Start_Developer_Guide#Request_URL_handling

Basically, if you have set the metadata on the "Quick Start Editorial" node to have a host name of "myserver", then the site will only be resolved if the requested URL is addressed to "myserver". "localhost" will fail to resolve to the website.

Re: 3.4.b 'Sorry, there seems to be a problem...'

bremmington — Wed, 17 Nov 2010 10:08:06 GMT

Ah, right. Good.

So, the problem is now a failure to authenticate through the Web Editor. I've not seen this before, so it may take a little while to track down what's happening. This may seem an odd question, but what browser (type and version) are you using?

Re: 3.4.b 'Sorry, there seems to be a problem...'

dstannard — Wed, 17 Nov 2010 10:38:02 GMT

Firefox 3.6.9 and IE 7.0

Re: 3.4.b 'Sorry, there seems to be a problem...'

bremmington — Wed, 17 Nov 2010 11:28:02 GMT

OK. I don't have FF 3.6.9, but the authentication is certainly working fine in FF 3.6.12.

There are a few places to prod to try to work out what's happening on your system. Perhaps first increasing the log level in the web editor application would be an idea. You should see in the "webapps/awe/WEB-INF/classes" folder a file named "log4j.properties". Open this file in your favourite text editor and alter the lines:


# Spring
log4j.logger.org.springframework=warn
# Turn off Spring remoting warnings that should really be info or debug.
log4j.logger.org.springframework.remoting.support=error
log4j.logger.org.springframework.util=error
log4j.logger.org.springframework.extensions.webscripts.ScriptLogger=warn

# WEF
log4j.logger.org.springframework.extensions.webeditor=info

# Alfresco
log4j.logger.org.alfresco=error
log4j.logger.org.alfresco.repo.jscript.ScriptLogger=warn
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

to read:


# Spring
log4j.logger.org.springframework=warn
# Turn off Spring remoting warnings that should really be info or debug.
log4j.logger.org.springframework.remoting.support=debug
log4j.logger.org.springframework.util=debug
log4j.logger.org.springframework.extensions.webscripts.ScriptLogger=debug

# WEF
log4j.logger.org.springframework.extensions.webeditor=debug

# Alfresco
log4j.logger.org.alfresco=debug
log4j.logger.org.alfresco.repo.jscript.ScriptLogger=debug
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Then restart Tomcat and try the process of logging in through the web editor (via the WQS site) again. Does anything appear in the alfresco.log file (or the Tomcat console)?