3 added 404 characters in body
source | link

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

Digging the problem, it seems to not be a problem with, cause the symlink is a file: "FileAlreadyExistsException is thrown if the file exists and is directory. In this example then the file exists but is a sym link so the exception is correct." So it seems the solution has to be in the tridion side, changing the deployer behaviour. I don't know if it exists any hotfix related to this problem.

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

Digging the problem, it seems to not be a problem with, cause the symlink is a file: "FileAlreadyExistsException is thrown if the file exists and is directory. In this example then the file exists but is a sym link so the exception is correct." So it seems the solution has to be in the tridion side, changing the deployer behaviour. I don't know if it exists any hotfix related to this problem.

2 deleted 136 characters in body
source | link

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So maybe the solution is update the JVM, but in the last version of JDK 1.7u80 there are still references of this problem happening.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So maybe the solution is update the JVM, but in the last version of JDK 1.7u80 there are still references of this problem happening.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.

1
source | link

There is a known problem with certain versions of the Java virtual machine where this exception is thrown.

So maybe the solution is update the JVM, but in the last version of JDK 1.7u80 there are still references of this problem happening.

So my recomendation is to update to JDK 8 and preferably the latest version, because there are certain versions of the JDK 8 in which this problem still exists.