AEM 5.6 403 after initial install: error in org.apache.sling.servlets.get.DefaultGetServlet. | Community
Skip to main content
0
0sum
October 16, 2015
Solved

AEM 5.6 403 after initial install: error in org.apache.sling.servlets.get.DefaultGetServlet.

  • October 16, 2015
  • 7 replies
  • 2395 views

I have just completed installing AEM 5.6 under weblogic 10.3.5 on a 64bit Centos system, however after the initial install I am only able to access crxde and the sling pages.

I am hoping this is a simple issue even though I have been extremely hard pressed to find any information via google engineering, anyhow this is the error I am seeing:

Forbidden (403)

The requested URL /aem-quickstart-5.6.1 resulted in an error in org.apache.sling.servlets.get.DefaultGetServlet.

Request Progress:

0 (2013-09-20 17:10:26) TIMER_START{Request Processing} 0 (2013-09-20 17:10:26) COMMENT timer_end format is {<elapsed msec>,<timer name>} <optional message> 0 (2013-09-20 17:10:26) LOG Method=GET, PathInfo= 0 (2013-09-20 17:10:26) TIMER_START{ResourceResolution} 0 (2013-09-20 17:10:26) TIMER_END{0,ResourceResolution} URI=/aem-quickstart-5.6.1 resolves to Resource=JcrNodeResource, type=rep:root, superType=null, path=/ 0 (2013-09-20 17:10:26) LOG Resource Path Info: SlingRequestPathInfo: path='/', selectorString='null', extension='null', suffix='null' 0 (2013-09-20 17:10:26) TIMER_START{ServletResolution} 0 (2013-09-20 17:10:26) TIMER_START{resolveServlet(JcrNodeResource, type=rep:root, superType=null, path=/)} 0 (2013-09-20 17:10:26) TIMER_END{0,resolveServlet(JcrNodeResource, type=rep:root, superType=null, path=/)} Using servlet org.apache.sling.servlets.get.DefaultGetServlet 0 (2013-09-20 17:10:26) TIMER_END{0,ServletResolution} URI=/aem-quickstart-5.6.1 handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet 0 (2013-09-20 17:10:26) LOG Applying Requestfilters 0 (2013-09-20 17:10:26) LOG Calling filter: org.apache.sling.bgservlets.impl.BackgroundServletStarterFilter 0 (2013-09-20 17:10:26) LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter 0 (2013-09-20 17:10:26) LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter 0 (2013-09-20 17:10:26) LOG Calling filter: com.adobe.granite.optout.impl.OptOutFilter 0 (2013-09-20 17:10:26) LOG Calling filter: org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter 0 (2013-09-20 17:10:26) TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0} 0 (2013-09-20 17:10:26) LOG Using org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for extension=null 0 (2013-09-20 17:10:26) LOG Applying Error filters 0 (2013-09-20 17:10:26) LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter 0 (2013-09-20 17:10:26) TIMER_START{handleError:status=403} 1 (2013-09-20 17:10:26) TIMER_END{1,handleError:status=403} Using handler org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet 1 (2013-09-20 17:10:26) TIMER_END{1,Request Processing} Dumping SlingRequestProgressTracker Entries
ApacheSling/2.2 (WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Feb 3 16:30:47 EST 2011, Java HotSpot(TM) 64-Bit Server VM 1.6.0_45, Linux 2.6.32-358.el6.x86_64 amd64)

I would greatly appreciate any suggestions on what I should be looking for.

Thanks

0sum

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Initial i was suspecting context root with dot caused the issue & verified locally with  aem-quickstart-5.6.1 and works.

By default accessing the root should call redirect servlet & then root mapping.  In your log I do not see that instead it calls get servlet & looks like all bundles are not installed. Can you verify all bundles are installed following [1].

[1]   http://dev.day.com/content/dam/day/onlinetool/COI.html

7 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

is your context root itself is  aem-quickstart-5.6.1  ?

0
0sumAuthor
October 16, 2015

I would like to point out the following urls work:

http://xx.xx.xx.xx:4502/aem-quickstart-5.6.1/crx/de/index.jsp

http://xx.xx.xx.xx:4502/aem-quickstart-5.6.1/system/console/

0
0sumAuthor
October 16, 2015

This is the path to the crx folder:

/opt/Oracle/Middleware/user_projects/domains/cq-test/crx-quickstart-author

this is the path to the .war file:

/opt/Oracle/Middleware/user_projects/domains/cq-test/aem-quickstart-5.6.1.war

does the context path need to contain the full path to either the war file or crx folder?

this is the current contect path:

Context Root:

/aem-quickstart-5.6.1

 

thanks for your interest

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Initial i was suspecting context root with dot caused the issue & verified locally with  aem-quickstart-5.6.1 and works.

By default accessing the root should call redirect servlet & then root mapping.  In your log I do not see that instead it calls get servlet & looks like all bundles are not installed. Can you verify all bundles are installed following [1].

[1]   http://dev.day.com/content/dam/day/onlinetool/COI.html

0
0sumAuthor
October 16, 2015

Many thanks for providing that tool, looks like it will come in very handy once I get a better understanding.

0
0sumAuthor
October 16, 2015

Here is the json from my instance, your tool has suggested that almost half of my bundles are deleted, what does this term infer half of them are missing?

As I cannot provide the json to you via the forum here is the summary:

Bundles Added:1, Bundles Deleted:152, Matched Bundles:156, Mismatch in bundles version:0

Can you explain these categories please?

 

Thank you :)

Sham_HC
Sham_HC
Level 10
October 16, 2015

Initial install is not complete.  Your log should tell why it was failed. Please file daycare ticket and get official help. 

Terms & ConditionsAccessibility statement

Loading footer...