Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.3.2.1
-
None
-
None
-
Important
Description
Hi,
I get the issue on 2 separate Windows machines: Windows 7 64-bit and Windows 2012.
In each case, the Java version is the latest update of JDK 7 (jdk7u80). It happens with both 32-bit and 64-bit versions of the JDK.
Procedre:
- Unzip James files on the disk
- Launch cmd.exe as Administrator
- Go in James' bin directory, and launch run.bat
James doesn't start, and the phoenix.log file contains this:
ERROR 2015-10-27 12:50:14.903 [Phoenix.] (): There was an error running phase "startup" for Block named "users-store". (Reason: Component named "users-store" failed to pass through the Starting stage. (Reason: org.apache.avalon.framework.configuration.ConfigurationException: destination>>URL).).
org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: Component named "users-store" failed to pass through the Starting stage. (Reason: org.apache.avalon.framework.configuration.ConfigurationException: destination>>URL).
at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:354)
at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:226)
at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:530)
at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:478)
at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:409)
at org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:180)
at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:260)
rethrown from
org.apache.avalon.framework.configuration.ConfigurationException: destination>>URL
at org.apache.james.userrepository.UsersFileRepository.configure(UsersFileRepository.java:134)
at org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:201)
at org.apache.james.core.AvalonUsersStore.initialize(AvalonUsersStore.java:130)
at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
at org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:200)
at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:530)
at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:478)
rethrown from
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:414)
at java.io.File.getCanonicalPath(File.java:618)
at java.io.File.getCanonicalFile(File.java:643)
at org.apache.james.userrepository.UsersFileRepository.configure(UsersFileRepository.java:132)
at org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:201)
at org.apache.james.core.AvalonUsersStore.initialize(AvalonUsersStore.java:130)
Upon exit, there's an additional warning because files in the work directory cannot be deleted:
WARN 2015-10-27 12:50:15.028 [Phoenix.] (): Error deleting Work Directory "D:\James\work\james-1445946613419". (Reason: File D:\James\work\james-1445946613419\SAR-INF\lib\mailet-api-2.3.jar unable to be deleted.)
java.io.IOException: File D:\James\work\james-1445946613419\SAR-INF\lib\mailet-api-2.3.jar unable to be deleted.
at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:743)
at org.apache.avalon.excalibur.io.FileUtil.cleanDirectory(FileUtil.java:910)
at org.apache.avalon.excalibur.io.FileUtil.deleteDirectory(FileUtil.java:866)
at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:735)
at org.apache.avalon.excalibur.io.FileUtil.cleanDirectory(FileUtil.java:910)
at org.apache.avalon.excalibur.io.FileUtil.deleteDirectory(FileUtil.java:866)
at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:735)
This is a very blocking issue for me as I rely on James in production environments, so I can't just use the previous version with a security issue in it.
Thanks
Vincent