LogManager error of type GENERIC_FAILURE using OpenCL with Java

Wilson Net
Wilson Net used Ask the Experts™
on
Hi, after windows update on 2018-09-10, OpenCL faild to start on java application with the following error:

LogManager error of type GENERIC_FAILURE: Failed to move file C:\Servidor\JBossWF\standalone\log\server.log to C:\Servidor\JBossWF\standalone\log\server.log.2018-09-08.
java.nio.file.FileSystemException: C:\Servidor\JBossWF\standalone\log\server.log -> C:\Servidor\JBossWF\standalone\log\server.log.2018-09-08: El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso.

	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)

Open in new window


the file dont exist but it appear to be locked, what could be cause this error?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Software Engineer
Commented:
It looks like the error is referring to the source file, not the destination file.

It's trying to move the "C:\Servidor\JBossWF\standalone\log\server.log" file, but that file is in use, so it can't be moved.
Wilson NetJava Devs

Author

Commented:
you're right, the first WAR is taking the file on the new version, lockit it, and the second can't use it.

i fix it change the log filename in log4j2.xml

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial