Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Apache+Tomcat connector error : Error registering Catalina

 
Manish Hatwalne
Ranch Hand
Posts: 2591
Android Firefox Browser Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am having strange problem in the Apache-Tomcat connector that we have for our system. It is a huge complex system that we are running on Tomcat 5.0.28 and Apache 2.3 with mod_jk connector. For several complex reasons including legacy code, we can't upgrade Tomcat. The code runs fine, except that often we see these errors in the Tomcat logs -




I have looked up similar posts and they all suggest soem manual erro while starting another instance of Tomcat, but that is not the case for us. This suggests that there is an error while creating another instance of Tomcat by connector/Apache. And I am really wondering what or who is creating this another instance? We used to see it less frequently earlier, but now it has become more frequent (after memory upgrade) and often resulting in OutOfMemory error crashing our server. Here are the relevant configurations from Tomcat & Apache -

Tomcat

Apache


Can anyone help me understand what is causing this error so frequently (more than 20/25 times in a single day)? Moreover, how can I fix it? How can one tweak these configurations to handle the load? Besides the huge Tomcat application, our Apache server handles several PHP/Wordpress blogs.
Any pointers on this one would be highly appreciated!

TIA,
- Manish
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18096
50
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I sincerely hope that someone is making a concentrated effort on getting you migrated up from Tomcat 5.0. There are significant differences in the JVM characteristics that start at 5.5 and continue on from there. I don't know that Tomcat 5.0 is even supported anymore and even in places like the JavaRanch, you're not going to find much remaining expertise for anything that old.

From what I can see, there seems to be a serious scrambling of something internal to Tomcat causing it to attempt to create a duplicate copy of one of Tomcat's MBeans. That's not normal behavior. Without a lot more details, I can only guess at one of 2 possibilities:

1. You have some really messed up configuration options in Tomcat.

2. That new memory is defective.
 
Manish Hatwalne
Ranch Hand
Posts: 2591
Android Firefox Browser Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim Holloway wrote:I sincerely hope that someone is making a concentrated effort on getting you migrated up from Tomcat 5.0. There are significant differences in the JVM characteristics that start at 5.5 and continue on from there. I don't know that Tomcat 5.0 is even supported anymore and even in places like the JavaRanch, you're not going to find much remaining expertise for anything that old.

From what I can see, there seems to be a serious scrambling of something internal to Tomcat causing it to attempt to create a duplicate copy of one of Tomcat's MBeans. That's not normal behavior. Without a lot more details, I can only guess at one of 2 possibilities:

1. You have some really messed up configuration options in Tomcat.

2. That new memory is defective.


Well, there are no non-default configurations in Tomcat besides the one I have given above. Migration would be great - but we cannot consider it as of now for several reasons, our legacy code is the biggest hurdle for this and it fails with Tomcat 5.5!
I am digging deeper into this now.
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18096
50
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
An oft-abused saying in IT is "If it ain't broke, don't fix it".

Which is silly. When you're talking software, it's common that it is broke, and you don't know it yet. I almost ended up in Chicago one day on a panic basis because of a case like that.

Related to this is the fact that software often breaks due to changes from the outside. My hastily-scheduled trip was fallout from a change to the OS that unearthed a really sloppy application bug that up until then had been able to tinker with memory that it didn't own.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic