folder handler did not accept xxx.js (500)

[dragon2A]

Hi Team,

As part of my Touch UI upgrade work am adding client libs in an existing maven project. I am trying to build the project after adding the client libs folder I am receiving this exception. I am adding the complete stack trace. I need help to resolve this one. 

org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage Error during install.

java.lang.IllegalStateException: folder handler did not accept

02.06.2017 16:43:47.732 *INFO* [qtp400565249-3367] org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage Extracting eahelp Content Package:xxxxx.ui.apps:2.0.51-SNAPSHOT

02.06.2017 16:43:47.828 *ERROR* [qtp400565249-3367] org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage Error during install.

java.lang.IllegalStateException: folder handler did not accept xx/xxx/components/clientlib/listener.js

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:928)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:801)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:841)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:841)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:841)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:841)

  at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:841)

  at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:415)

  at org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.extract(ZipVaultPackage.java:234)

  at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:423)

  at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.install(JcrPackageImpl.java:392)

  at com.day.jcr.vault.packaging.impl.JrVltJcrPackageAdapter.install(JrVltJcrPackageAdapter.java:107)

  at com.day.crx.packmgr.impl.servlets.ServiceServlet.doInstall(ServiceServlet.java:330)

  at com.day.crx.packmgr.impl.servlets.ServiceServlet.upload(ServiceServlet.java:403)

  at com.day.crx.packmgr.impl.servlets.ServiceServlet.doService(ServiceServlet.java:155)

  at com.day.crx.packmgr.impl.AbstractServlet.service(AbstractServlet.java:52)

  at com.day.crx.packmgr.impl.MainServlet.doService(MainServlet.java:148)

  at com.day.crx.packmgr.impl.MainServlet.service(MainServlet.java:125)

  at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:85)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:79)

  at com.adobe.granite.license.impl.LicenseCheckFilter.doFilter(LicenseCheckFilter.java:308)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.felix.http.sslfilter.internal.SslFilter.doFilter(SslFilter.java:89)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.sling.security.impl.ReferrerFilter.doFilter(ReferrerFilter.java:290)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:129)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.sling.featureflags.impl.FeatureManager.doFilter(FeatureManager.java:116)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.sling.engine.impl.log.RequestLoggerFilter.doFilter(RequestLoggerFilter.java:75)

  at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)

  at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)

  at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:124)

  at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:61)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)

  at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)

  at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)

  at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)

  at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)

  at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)

  at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)

  at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)

  at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)

  at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)

  at org.eclipse.jetty.server.Server.handle(Server.java:499)

  at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)

  at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)

  at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)

  at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

  at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

  at java.lang.Thread.run(Thread.java:745)

I am using content-package-maven-plugin:0.0.24 this maven plug-in .

Thanks In Advance

[dragon2A · Accepted solution]

I am able to resolve it by deleting the empty folders in client lib folder which are listeners.js.dir and js.txt.dir but I still have one doubt is this expected behavior? Do we really need to delete these folders to install the app package?

what's the expected behavior?

Thanks

[anvesh4564]

Thank you, this worked for me, I have deleted all the .dir files under my compononent folder and ran maven build, was able to deploy code

[prajjain]

After deleting empty folders under client lib its working for me. It looks like AEM will parse for empty folders while installing package on AEM server, so we are getting 500 error for this call while deploying the package as part of maven build.

@dragon2A  Thanks!!

[VeenaVikraman]

Yes, as per my understanding , there is a particular set of allowed folders or node types. When any non allowed content is present in the package, it throws a similar exception. Basically .dir files/folders are not an allowed type for the folders in the content package.

Thanks

Veena

[rampai]

Hi.

Is there some configuration that can be applied to ignore .dir folders right away in maven build?

Thanks,

Ram

[arunpatidar]

yes, you can handle include/exclude using filter.xml

Jackrabbit Filevault - Workspace Filter

<filter root="/tmp">

  <exclude pattern=".*\.dir"/>

</filter>

Note : If the first pattern is include, then the default is exclude and vice versa.