File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Tomcat and the fly likes Problem migrating to tomcat-6.0.36 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Problem migrating to tomcat-6.0.36" Watch "Problem migrating to tomcat-6.0.36" New topic

Problem migrating to tomcat-6.0.36

chris andrey

Joined: Dec 04, 2012
Posts: 2
Hi All,

I was hoping to get a help with my issue in migrating to tomcat-6.0.36. At the moment, we are currently running tomcat 5.5.35 under Centos 5.7 & it has been running fine, however since 5.5 is now no longer supported, we need to migrate to version 6 for security reason.

I have done the following as part of the upgrade:
- downloaded tomcat-6.0.36.tar.gz (core)
- upgrade the JDK into 1.6.0 release 32
- upgrade Bitronix Transaction Manager to BTM 2.1.0 (following the guide listed in:
- upgrade the Tomcat Connector to the latest version, which is 1.2.37

When we start tomcat, it generate the following exception:

Dec 5, 2012 3:16:53 PM lifecycleEvent
INFO: Starting Bitronix Transaction Manager
Dec 5, 2012 3:16:53 PM logVersion
INFO: Bitronix Transaction Manager version 2.1.0
Dec 5, 2012 3:16:53 PM buildServerIdArray
INFO: JVM unique ID: <tomcat-btm-node-sbb-int010>
Dec 5, 2012 3:16:53 PM init
INFO: reading resources configuration from /usr/local/tomcat-instances/sbb_internal/conf/
Dec 5, 2012 3:16:53 PM run
INFO: recovery committed 0 dangling transaction(s) and rolled back 0 aborted transaction(s) on 3 resource(s) [ReportingDB, ExternalDB, InternalDB] (restricted to serverId 'tomcat-btm-node-sbb-int010')
Dec 5, 2012 3:16:53 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Dec 5, 2012 3:16:53 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.36
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.apache.catalina.startup.Bootstrap.start(
at org.apache.catalina.startup.Bootstrap.main(
Caused by: java.lang.NoSuchMethodError: org.apache.tomcat.util.IntrospectionUtils.setProperty(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;)V
at org.apache.jk.server.JkMain.setBeanProperty(
at org.apache.jk.server.JkMain.processProperty(
at org.apache.jk.server.JkMain.processProperties(
at org.apache.jk.server.JkMain.start(
at org.apache.jk.server.JkCoyoteHandler.start(
at org.apache.catalina.connector.Connector.start(
at org.apache.catalina.core.StandardService.start(
at org.apache.catalina.core.StandardServer.start(
at org.apache.catalina.startup.Catalina.start(

Anyone can suggest any idea as to where the exception is generated from? Really appreciated any help I can get in troubleshooting this issue. Thanks guys
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17417

Welcome to the JavaRanch, Chris!

You appear to be out of sync between your compile libraries and your run libraries. If you have added any jars to the TOMCAT_HOME/lib directory, you should reconsider them. You've probably noticed that Tomcat 6 has 1 lib directory instead of Tomcat 5's 3 lib directories, but that's not really important.

An IDE is no substitute for an Intelligent Developer.
chris andrey

Joined: Dec 04, 2012
Posts: 2
Hi Tim,

Thanks for the quick response, are you able to specify which library that was out of sync from the above error message. At first I thought it was the case with the tomcat connector, hence I recompile a new one, but it might not be the issue here.

To make things even complicated, we have 2 application server that runs on similar setting, I manage to start tomcat on 1 of the server successfully but not on the other. I copied the exact same tomcat package, same libraries, same JRE & it is running the same application code, not sure why they are behaving differently since they are basically running on the same environment (from tomcat perspective).
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17417

Well, the offender appears to be the Coyote connector, but it all appears to be in the middle of stuff that should be core Tomcat code, so I have to wonder if somehow your copy of Tomcat isn't damaged. Or you have something really weird going on in Tomcat's CLASSPATH.
I agree. Here's the link:
subject: Problem migrating to tomcat-6.0.36
It's not a secret anymore!