possible bug when loading content with many files from bundle

[Ioan Eugen Stan <ie...@netdava.com>]

Hello,

I've been playing around with sling, migrating our setup and content and
I think I have discovered a bug when loading content into sling.

I'm using a sling-starter project and sling-started-content. I've
updated started-contnet to include some frontend dependencies downloaded
with npm.

The content jar size is 9mb and  contains an extra ~ 3300 files and 330
folders.

When I start sling-starter I get 403 page with the bellow error.

I believe there is a time-out loading the content or the content takes
more than 1-5 minutes to load so that is why things break.

At a minimum, I do belive the logging can be improved to know if the
content is loading or not or maybe I just need to switch to debug.

I have created a branch to reproduce the bug [1]. Use the following steps:

---

git clone
https://github.com/netdava/sling-org-apache-sling-starter-content.git

cd  sling-org-apache-sling-starter-content && git co 
content-loading-bug-improvement

mvn clean install

----

Once the content is built, go to a sling-starter project and in
sling.txt update version like this
"org.apache.sling/org.apache.sling.starter.content/1.0.1-loadbug"

-----

Forbidden (403)

The requested URL / resulted in an error in
org.apache.sling.servlets.get.DefaultGetServlet.
Request Progress:

      0 TIMER_START{Request Processing}
      6 COMMENT timer_end format is {<elapsed microseconds>,<timer
name>} <optional message>
     20 LOG Method=GET, PathInfo=null
     39 TIMER_START{handleSecurity}
   2731 TIMER_END{2688,handleSecurity} authenticator
org.apache.sling.auth.core.impl.SlingAuthenticator@54b78198 returns true
   6147 TIMER_START{ResourceResolution}
   7266 TIMER_END{1108,ResourceResolution} URI=/ resolves to
Resource=JcrNodeResource, type=sling:OrderedFolder, superType=null,
path=/content
   7297 LOG Resource Path Info: SlingRequestPathInfo: path='/content',
selectorString='null', extension='null', suffix='/'
   7299 TIMER_START{ServletResolution}
   7318 TIMER_START{resolveServlet(/content)}
   7468 TIMER_END{146,resolveServlet(/content)} Using servlet
org.apache.sling.servlets.get.DefaultGetServlet
   7481 TIMER_END{180,ServletResolution} URI=/ handled by
Servlet=org.apache.sling.servlets.get.DefaultGetServlet
   7510 LOG Applying Requestfilters
   7522 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   7534 LOG Calling filter:
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
   7541 LOG Applying Componentfilters
   7582 TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
   7601 LOG Using
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to
render for extension=null
   7687 LOG Applying Error filters
   7699 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   7713 TIMER_START{handleError:status=403}
   8362 TIMER_END{646,handleError:status=403} Using handler
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
   8916 TIMER_END{8914,Request Processing} Dumping
SlingRequestProgressTracker Entries
----

[1]
https://github.com/netdava/sling-org-apache-sling-starter-content/tree/content-loading-bug-improvement


Regards,

Eugen

Re: possible bug when loading content with many files from bundle

[Ioan Eugen Stan <ie...@netdava.com>]

Hello Bertrand,

I've added https://issues.apache.org/jira/browse/SLING-7726 to track
this. Maybe I will have some time and fix it as well.


Regards,

Eugen


On 04.06.2018 13:20, Bertrand Delacretaz wrote:
> Hi,
>
> On Sat, May 26, 2018 at 12:20 PM, Ioan Eugen Stan <ie...@netdava.com> wrote:
>> ...I have created a branch to reproduce the bug [1]...
> Best is to track this in jira so it doesn't fall through the cracks.
> Let us know if you lack jira access rights.
>
> -Bertrand

Re: possible bug when loading content with many files from bundle

[Bertrand Delacretaz <bd...@apache.org>]

Hi,

On Sat, May 26, 2018 at 12:20 PM, Ioan Eugen Stan <ie...@netdava.com> wrote:
> ...I have created a branch to reproduce the bug [1]...

Best is to track this in jira so it doesn't fall through the cracks.
Let us know if you lack jira access rights.

-Bertrand