Sorry for the late reply but I got bogged down by a customer going live.
Here is the stack trace:
[ 122101] ERROR - plication.impl.ApplicationImpl -
org.apache.sling.ide.io.ConnectorException:
/content/dam/aembase/asset.jpg/jcr:content/renditions/cq5dam.web.1280.1280.jpeg
java.lang.RuntimeException: org.apache.sling.ide.io.ConnectorException:
/content/dam/aembase/asset.jpg/jcr:content/renditions/cq5dam.web.1280.1280.jpeg
at
com.headwire.aem.tooling.intellij.communication.AbstractDeploymentManager.publishModule(AbstractDeploymentManager.java:192)
at
com.headwire.aem.tooling.intellij.communication.ServerConnectionManager.deployModule(ServerConnectionManager.java:493)
at
com.headwire.aem.tooling.intellij.communication.ServerConnectionManager.deployModules(ServerConnectionManager.java:478)
at
com.headwire.aem.tooling.intellij.action.DeployToServerAction$1$1.run(DeployToServerAction.java:99)
at
com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:951)
at
com.headwire.aem.tooling.intellij.action.DeployToServerAction$1.run(DeployToServerAction.java:68)
at
com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:563)
at
com.intellij.openapi.progress.impl.CoreProgressManager$2.run(CoreProgressManager.java:142)
at
com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:446)
at
com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:392)
at
com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:54)
at
com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:127)
at
com.intellij.openapi.progress.impl.ProgressManagerImpl$1.run(ProgressManagerImpl.java:126)
at
com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:366)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at
org.jetbrains.ide.PooledThreadExecutor$1$1.run(PooledThreadExecutor.java:55)
Caused by: org.apache.sling.ide.io.ConnectorException:
/content/dam/aembase/asset.jpg/jcr:content/renditions/cq5dam.web.1280.1280.jpeg
at
com.headwire.aem.tooling.intellij.communication.AbstractDeploymentManager.execute(AbstractDeploymentManager.java:347)
at
com.headwire.aem.tooling.intellij.communication.AbstractDeploymentManager.publishModule(AbstractDeploymentManager.java:137)
... 19 more
Caused by: org.apache.sling.ide.transport.RepositoryException:
javax.jcr.ItemExistsException: Cannot add child node
'cq5dam.web.1280.1280.jpeg' to
/content/dam/aembase/asset.jpg/jcr:content/renditions: colliding with
same-named existing node.
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:80)
at
org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:45)
at
com.headwire.aem.tooling.intellij.communication.AbstractDeploymentManager.execute(AbstractDeploymentManager.java:336)
... 20 more
Caused by: javax.jcr.ItemExistsException: Cannot add child node
'cq5dam.web.1280.1280.jpeg' to
/content/dam/aembase/asset.jpg/jcr:content/renditions: colliding with
same-named existing node.
at
org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkCollision(ItemStateValidator.java:594)
at
org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkAddNode(ItemStateValidator.java:392)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.addNodeState(SessionItemStateManager.java:435)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:245)
at
org.apache.jackrabbit.jcr2spi.operation.AddNode.accept(AddNode.java:79)
at
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
at org.apache.jackrabbit.jcr2spi.NodeImpl.createNode(NodeImpl.java:1454)
at org.apache.jackrabbit.jcr2spi.NodeImpl.addNode(NodeImpl.java:186)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.createNode(AddOrUpdateNodeCommand.java:176)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:99)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:85)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:68)
... 22 more
The delay in the save() does prevent the issue. That said I am not sure if it
is related to the DAM as my test projects are
just that. I’ll keep you posted if I find other scenarios where it does fail.
- Andy
> On Feb 18, 2016, at 12:15 AM, Robert Munteanu <[email protected]> wrote:
>
> Hi Andy,
>
> On Wed, 2016-02-17 at 19:41 -0500, Andreas Schaefer Sr. wrote:
>> Hi
>>
>> During the development of the IntelliJ plugin I ran into some random
>> failures to deploy.
>> Looking deeper I save that the failure is happening when
>> session.save() is called and
>> to my surprise a slight delay (Thread.sleep(100)) does fix it on my
>> Mac.
>>
>> The code is in JcrCommand inside the impl-vlt module. This is the
>> change that make it
>> work for me:
>>
>> @Override
>> public Result<T> execute() {
>>
>> Session session = null;
>> try {
>> session = repository.login(credentials);
>>
>> T result = execute0(session);
>>
>> try {
>> Thread.sleep(100);
>> } catch(InterruptedException e) {
>> }
>> session.save();
>>
>> return JcrResult.success(result);
>> The exception I see is a ItemExistsException and was thrown for a
>> folder and rendition file in the DAM.
>
>
> Can you add a stack trace? Does this only happen for DAM assets +
> renditions?
>
> Robert
