Troy,
   Thanks for looking into it. I think I said this in an earlier email 
but here are the issues I faced: 

1. _*Install issues. *_

    * Make sure you do not choose any tomcat package while creating the
      installation
    * xml-commons-jaxp-1.3-apis will be missing. So use YUM to get that.
    * As soon as you install the above, jdk 1.5 will disappear
    * So go back and use YUM to get JDK1.5.0_14. Then check that java is
      still there by going to /usr/java/jdk1.5.0_14/ and make sure these
      are real files and not dummy links pointing to nowhere.
    * Set your JAVA_HOME environment variable

2. _*Running Tomcat*_ - Now try to start tomcat. It will appear to start 
but the process wont run and there will be errors in the log file.

      The behavior is exactly as described by the following bugs against 
Fedora Core and RHEL . Tomcat will appear to start but the process wasnt 
running.

     http://forums.fedoraforum.org/showthread.php?p=802366
     https://bugzilla.redhat.com/show_bug.cgi?id=234286
     https://bugzilla.redhat.com/show_bug.cgi?id=227721  <- RHEL

3. So after Step 1 above, I went to tomcat, downloaded the zip file to 
get around Problem #2

Thanks,
Sri





Troy Dawson wrote:
> Troy Dawson wrote:
>> Diego García wrote:
>>> Hi Sri ;)
>>>
>>>
>>>
>>> I checked that I have jdk/jre installed, tried to manually configure
>>> JAVACMD variable, but still Tomcat refuses to start… Maybe a distro
>>> issue? SL 5.1 was released only a month ago… Of course I can install
>>> Tomcat from sources but that’s not a good/fast solution; in RHEL and
>>> Fedora this is simple as installing it with “Add/Remove Packages” or
>>> yum. Other distros (Debian, OpenSuse, CentOS…) also work like a 
>>> charm in
>>> this case.
>>>
>>>
>>>
>>> We have to fix such errors in order to increase usability of SL5.1, I
>>> don’t think any non-IT people will use it if they encounter such 
>>> problems.
>>>
>>>
>>>
>>> Cheers,
>>>
>>>       Diego
>>>
>>>
>>
>> Hi,
>> I'm just letting you know that this didn't go on deaf ears.
>> Tomcat has been a pain in the rear because of the java issue.
>> Actually, java has been the pain in the rear, and because tomcat is 
>> based on
>> java, it too is very painful.
>> Anyway, we just had another security update for tomcat, and it is my 
>> goal to
>> get it to work in S.L. 5.  It's probrubly too late for you, but for 
>> the next
>> person who comes along, I'm going to get this bug squashed.
>> Troy
>
> OK, one part in making sure I get it right is being able to reproduce 
> the problem.
> I am not a tomcat user, and to me it's looking like it's starting.
> How can I tell if it's broken?
>
> Troy