• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

8.0.1 BUGS >> Tomcat5 crash don't work

crnunez

Regular Pleskian
Hello,
View the logs:

Install package java-1.4.2-sun
Install package jaf
Install package jakarta-commons-collections
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-collections-3.1-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-el
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-el-1.0-4jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-launcher
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-launcher-0.9-3jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-logging
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-logging-1.0.4-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-beanutils
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-beanutils-1.7.0-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-digester
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-digester-1.7-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-pool
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-pool-1.2-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-dbcp
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-dbcp-1.2.1-3jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package java-1.4.2-gcj-compat-devel
Install package javamail
Install package jta
Install package regexp
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/regexp-1.3-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package tomcat5-servlet-2.4-api
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tomcat5-servlet-2.4-api-5.0.30-8jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-fileupload
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-fileupload-1.0-3jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package tyrex
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tyrex-1.0.1-3jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-taglibs-standard
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-taglibs-standard-1.1.1-4jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package bcel
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/bcel-5.1-5jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package xml-commons
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/xml-commons-1.3.02-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package xml-commons-apis
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/xml-commons-apis-1.3.02-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package cryptix
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/cryptix-3.2.0-5jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package cryptix-asn1
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/cryptix-asn1-20011119-5jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package puretls
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/puretls-0.9-0.b5.1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package oro
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/oro-2.0.8-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-validator
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-validator-1.1.4-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package struts
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/struts-1.2.7-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-discovery
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-discovery-0.3-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-httpclient3
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-httpclient3-3.0-0.rc4.1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package wsdl4j, xerces-j2, xml-commons-resolver
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/wsdl4j-1.5.1-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package ant
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/ant-1.6.2-3jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package tomcat5-jasper
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tomcat5-jasper-5.0.30-8jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package xalan-j2
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/xalan-j2-2.7.0-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package log4j
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/log4j-1.2.12-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package axis
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/axis-1.2.1-2jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package mx4j
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/mx4j-3.0.1-1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package jakarta-commons-modeler
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/jakarta-commons-modeler-1.1-4jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package tomcat5
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tomcat5-5.0.30-8jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
/usr/bin/build-jar-repository: error: could not find jaas Java extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find jdbc-stdext Java extension for this JVM
/usr/bin/build-jar-repository: error: could not find jndi Java extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
Install package tomcat5-admin-webapps
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tomcat5-admin-webapps-5.0.30-8jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Install package tomcat5-webapps
warning: /root/psa/PSA_8.0.1/update-rpm-RedHat-el4-i386/tomcat5-webapps-5.0.30-8jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID c431416d
Try to install following packages with transaction on librpm:
package dummy_obsoleter_tomcat4-webapps-1.2.3.4
package psa-tomcat-configurator-8.0.1-rhel4.build80060615.20.noarch
package dummy_obsoleter_tomcat4-1.2.3.4
package dummy_obsoleter_tomcat4-admin-webapps-1.2.3.4
Committing changes...
Preparing packages for installation...
psa-tomcat-configurator-8.0.1-rhel4.build80060615.20
Checking for the system groups and users necessary for Tomcat...
Checking for the group 'tomcat'...
Trying to add group 'tomcat'... done

Checking for the user 'tomcat'...
Trying to add user 'tomcat'... done

Trying to find JAVA_HOME variable in the /usr/share/tomcat5/conf/tomcat5.conf...
JAVA_HOME variable is already in the /usr/share/tomcat5/conf/tomcat5.conf and has correct value (/usr/lib/jvm/java)
Trying to replace TOMCAT_USER variable in the /usr/share/tomcat5/conf/tomcat5.conf... done
Making chown and chmod under JDK stuff
Trying to set up Tomcat permissions... done
Stopping tomcat4: [ OK ]waiting for processes to exit
waiting for processes to exit
waiting for processes to exit
waiting for processes to exit
waiting for processes to exit
waiting for processes to exit
waiting for processes to exit
warning: /etc/tomcat4/tomcat4.conf saved as /etc/tomcat4/tomcat4.conf.rpmsave
warning: /etc/tomcat4/tomcat-users.xml saved as /etc/tomcat4/tomcat-users.xml.rpmsave
warning: /etc/tomcat4/server.xml saved as /etc/tomcat4/server.xml.rpmsave
warning: /etc/rc.d/init.d/tomcat4 saved as /etc/rc.d/init.d/tomcat4.rpmsave
*************************
When I attempt to start tomcat:


Usage: tomcat5 {start|stop|restart|condrestart}
[root@ns init.d]# ./tomcat5 status
Usage: tomcat5 {start|stop|restart|condrestart}
[root@ns init.d]# ./tomcat5 start
Starting tomcat5: lock file found but no process running for pid 4150, continuing
/usr/bin/rebuild-jar-repository: error: could not find jdbc-stdext Java extension for this JVM
/usr/bin/rebuild-jar-repository: error: could not find jndi Java extension for this JVM
/usr/bin/rebuild-jar-repository: error: All detected jars were not found for this jvm
/usr/bin/rebuild-jar-repository: error: could not find jaas Java extension for this JVM
/usr/bin/rebuild-jar-repository: error: All detected jars were not found for this jvm
[ OK ]
[root@ns init.d]#

This OK is FALSE, tomcat never START.

Please Plesk guys look at:

http://www.google.com/search?sourceid=navclient&hl=es&ie=UTF-8&rls=GGLG,GGLG:2005-36,GGLG:en&q=usr%2Fbin%2Fbuild%2Djar%2Drepository%3A+error%3A+could+not+find+jaas+Java+extension+for+this+JVM

PLEASE, ANY HAVE ANY SOLUTION/COMMENTS? Thanks!
 
In short,

Please 8.0.1 doon't have this rpm dependencies for Tomcat5:

/usr/bin/build-jar-repository: error: could not find jaas Java extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find jdbc-stdext Java extension for this JVM
/usr/bin/build-jar-repository: error: could not find jndi Java extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm


Can any submit the link for these RPM's? Does Plesk Staff has any idea?
 
After the 8.0.1-update toomcat was completely wrecked. I posted a support-ticket to PLESK and it took them nearly 24 hours to even start looking at it. After working for 2 hours on our server they gave up...

Tomcat worked fine with 8.0.0, but was completely screwed up after the 8.0.1-update, and even SW-soft themselves can't fix it...

It's now been over 12 hours since they mailed me to say that they weren't able to fix and that they had escalated my ticket, but they still haven't worked any more on it. We're losing customers over this... :-(

Have anyone found a solution to the tomcat-problems? The server is running RHEL4.
 
We have the same OS RHEL4, then I suppose that solution is the same.

SWSoft Support at this moment is looking this issue, and the solution in my case was:

I have logged in to the server and foun that there were some broken links to unexistent jar files that caused tomcat startup script fails. I have corrected it, and now tomcat is running.

Replace:
/var/run/tomcat4.pid with /var/run/tomcat5.pid

in the /usr/local/psa/etc/modules/watchdog/monitrc and /usr/local/psa/etc/modules/watchdog/monitrc.tpl files. Then I restarted the watchdog.

The unique fact is that only Support to know the fully solution.

Plesk 8.0.2 should will to have this solution for RHEL4...

Regards.
 
Can you tell us the exact version of Tomcat that you got running, and may be a few lines describing what you did to install / fix it ? Would be greatly appreciated.

(Facing the same requirement on RHEL4 / Plesk 8 having Tomcat 4.x and needing to go 5.x).
 
Hi,

I had that kind of problem and managed to solve the issue.

In my case, I have Plesk 8.0.1 (running on a Fedora Core 4 server) and Tomcat refused to start. After a quick look into Tomcat log (in /var/log/tomcat5/catalina.out), I saw that Tomcat didn't find a [jta].jar. Here is the piece of log :

java.lang.IllegalArgumentException: addRepositoryInternal: repository='file:/var/lib/tomcat5/common/lib/[jta].jar'
at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:957)


First I deleted that link (/var/lib/tomcat5/common/lib/[jta].jar) and then I've changed of JVM. I used :

$ sudo /usr/sbin/alternatives --config java

Then I choose another JVM (/usr/lib/jvm/jre-1.4.2-gcj/bin/java).

I hope it can help.
 
Hi all,

Thanks for all of you for discussing on that case. And I really want to say thank so much to janiko because after I follow your instruction, the Tomcat in My Plesk is working well.

Pisey
 
Back
Top