• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Troubles with Tomcat

  • Thread starter ducatimonster90
  • Start date
D

ducatimonster90

Guest
I have purchased a VPS with the Plesk Power Pack from StartLogic about three months ago.
Last week I started using Tomcat and noticed immediately that the service did not start.
From the log I have noticed there is aproblem with a jar file, the error exactly says:

-------------------------------------------------------------------------------------------------------
Bootstrap: Class loader creation threw exception
java.lang.IllegalArgumentException: addRepositoryInternal: repository='file:/var/lib/tomcat5/common/lib/[jta].jar'
at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:957)
at org.apache.catalina.loader.StandardClassLoader.<init>(StandardClassLoader.java:153)
at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:207)
at org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:163)
at org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:104)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:196)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402)
Caused by: java.util.zip.ZipException: No such file or directory
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:65)
at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:944)
-------------------------------------------------------------------------------------------------------

I solved temporally the problem recreating the symbolic link:

/var/lib/tomcat5/common/lib/[jta].jar

to the following file:

/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0/jta.jar

and so the service is correctly started from an ssh shell, but as I start or stop it from the Plesk interface, the symbolic link I fixed, is newly pointing to the wrong file or folder!

It seems that Plesk runs a script recreating all links in the:

/var/lib/tomcat5/common/lib/

folder, changing all my fixes!

I have asked the StartLogic support team for help, but they say they givo no support for specific problems on VPS because they are ment to be self managed! But why should I have no support if the service has never started correctly since i bought the Plesk Power Pack?

Could somebody give me a hint?

Thanks in advance!
 
Try installing a link in /usr/share/java to the jta.jar file. I experienced a similar problem with jdbc-stdext and fixed it by putting a link in /usr/share/java that points to the proper file in /usr/lib/jvm-exports/...
 
Thanks

while I was waiting for a reply from StartLogic, I installed a new version of Tomcat on my Virtual Private Server. And now it works but only if run manually!

I will try the solution you posted ;O) and find a way to reconfigure Plesk...

Bye
 
Back
Top