Tomcat 8.0 64-bit server does not start and does not receive an error from Catalina.bat

Question

I cannot start the 64-bit Tomcat 8.0 server. I also have katalina.bat. I get the message below.

01-Oct-2014 10:22:11.415 SEVERE [main] org.apache.catalina.startup.Bootstrap.ini
tClassLoaders Class loader creation threw exception
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
    at java.io.WinNTFileSystem.canonicalize0(Native Method)
    at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
    at java.io.File.getCanonicalPath(File.java:618)
    at java.io.File.getCanonicalFile(File.java:643)
    at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:165)
    at org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:201)
    at org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:146)
    at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:256)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)

Could you advise?

Answer 1

Had a similar problem with Tomcat 8 and Java 8 on Windows 8, and after a short conversation I noticed that it CATALINA_HOMEwas installed as " CATA_HOME=c:\mydir\tomcat.8.0\"

I just changed it to CATA_HOME=c:\mydir\tomcat.8.0"and it fixed all the problems. I never thought the end of the slash would cause a problem, but there you ... did it !!!

Answer 2

, - catalina.properties. : ...,"${catalina.home}/lib/*.jar,${catalina.base}/../lib/*.jar" ...,"${catalina.home}/lib/*.jar "," ${catalina.base}/../lib/*.jar".

Answer 3

. CATALINA_HOME, : : CATALINA_HOME = D:\\\Apache\Apache-Tomcat-7.0.37-Windows-x64\Apache-7.0.37-\

: CATALINA_HOME = D:\\\Apache\Apache-Tomcat-7.0.37-Windows-x64\Apache-7.0.37-

VOILA! .

Answer 4

. .properties server.loader=C:\aaconfigs\appconfigs,C:\aaconfigs\appParams. . server.loader=C:/aaconfigs/appconfigs,C:/aaconfigs/appParams., .

, .

Answer 5

I managed to solve this problem by deleting the server and creating a new one . Much easier than trying to diagnose what went wrong.

Answer 6

I had the same problem and I just deleted the server from my workspace and added a new one, did not receive the error again. Now it works fine.