More detail is definitely needed. In particular, you
might look at what has changed in the application (not
just the context file).
Also, what else has changed in the environment?
Typically, questions such as 1) "this used to work,
but now it doesn't" and 2) "there must be a bug in
Tomcat" don't get answered.
1) Computer performance changes for a reason. Even if
the reason is not well-understood, the performance
changes for a reason. Tracking change in an
environment is the key to understanding sudden
behavior changes. Good system configuration
management, software release management, software
configuration management, and change management
processes are required.
2) Many questions of this ilk have to do with not
understanding the Tomcat documentation. Tomcat
documentation is typical of complex software
documentation. This type of documentation is
"descriptive" documentation as opposed to "task"
documentation. Even though the Tomcat documentation
does try to contain some tasks, most of the material
is descriptive. This places the responsibility of
creating tasks on the user.
In short, in order to use Tomcat you will need to
spend some time organizing the descriptive
documentation into task documentation suited for your
specific task. This requires more understanding of a
software package than just plug and play.
As far as your particular problem goes, I would use
the following steps to investigate.
a) Determine the last known time a Tomcat restart was
accomplished in a reasonable amount of time (define
reasonable).
b) Note ALL changes to the environment that have been
made since that time. These changes include (but are
not limited to):
i) Application changes
ii) Server changes
iii) Changes to the program that interface to the
application
iv) Network changes
Test each change (one by one if possible). That which
is left, even if not understood is the problem.
If you're looking for a quick fix to a general problem
like this, there is none that I know of.
Again, in the future good change and configuration
management along with a careful recording of metrics
will make performance problem resolution much easier.
Just my two cents . . . .
/mde/
> >-----Original Message-----
> >From: Biernesser, Beth
> >Sent: Tuesday, March 14, 2006 7:33 AM
> >To: 'Tomcat Users List'
> >Subject: Tomcat taking too long to cycle through
> and come back up
> >
> >Does anyone have any idea why tomcat would take 13
> minutes to cycle
> >through and come back up? The process gets stuck
> on this line:
> >
> >INFO: Processing Context configuration file URL
>
>file:/usr/local/tomcat-5.0.25/conf/Catalina/localhost/appname.xml
> >
> >I really didn't think the process was going to come
> back up, but it
> >finally did. However, I need to figure out what is
> taking all of the
> >time to try to eliminate it. Has anyone run into
> this problem?
> >
> >P.S. the context file (appname.xml file) has not
> been modified since
> >it's implementation, and we have only experienced
> this problem recently.
> >Before, the tomcat process would typically take
> only a few minutes to
> >process and come back up. Thanks for any
> ideas/suggestions/help!
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> >For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
> >
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
