-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Mark,
On 8/24/16 3:34 PM, Mark Thomas wrote: > On 24/08/2016 17:56, Toews, Timothy wrote: >> Hello all: >> >> I am new to this list as of half an hour ago. I am concurrently >> searching the archives for a potential solution to the error >> message I have included below. This error happens on a daily >> basis for our office, attempting to login to a server where we >> store files that document our site processes and procedures. Any >> and all help is appreciated. Thanks in advance > > 4.1.29 ? You know that version was released in 2003 right? (No, > that isn't a typo.) Hey! There's someone out there running an older version of Tomcat than I am! Timothy, I tip my crown to you, sir, as I pass it -- the crown -- to you. I'm kidding. Well, no, I'm not, but I'm not trying to make fun of you. A few years ago when I joined this list, I was running Tomcat 4.1.x and everyone was furrowing their brows at me. I pain-stakingly went through the upgrade cycle from 4.1 -> 5.5 -> 6.0 -> 7.0 -> 8.0. It only took me ... a few years. We only just had a software release this summer (northern hemisphere) on Tomcat 8. Then these jokers had to go and release Tomcat 8.5. But now I'm a committer. And I feel your pain. You don't care about all the jokes and "hey, man, you need to upgrade"... you just want to solve your problem. Well, I'm going to tell you that "just solving your problem" is not really an option for a number of reasons. In super-compact form, here's a list of reasons why: 1. Publicly-disclosed security vulnerabilities 2. Near-zero support Also, if you are running Tomcat 4.1, you probably also have some seriously old versions of things like Java. If you don't have a recent version of Java, then you can't support things like TLS. TLS support was added to Java in version 1.4 when JSSE was integrated into the standard Java Runtime packages. (Before then, it was an add-on). Older Java versions have wonderful flaws like this one: http://www.exploringbinary.com/java-hangs-when-converting-2-225073858507 2012e-308/ I would encourage you to think very seriously about migrating your system to Tomcat 8.0.x running on Java 1.8. In many cases, all you have to do is copy your application's WAR file (or exploded WAR directory... whatever you've got in your webapps/ directory) into a Tomcat 8 auto-deployment directory and your app will just work. It's also possible that a bunch of things won't work. But we can help you if you choose to take this route. > At this point, this looks more like an application bug that a > Tomcat bug. Agreed. There's probably more in the log file that was initially posted. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJXvhlrAAoJEBzwKT+lPKRYseoQAKf18tig84G1kupLDQ7VHiwE auqQThPlHeOJRv9j0BJD/ZFnx+bjTj6Nku3SlpkcZ3ckHcUas2Nkfb4dMVQCP7b7 gZjzEADbl8PqzqbzDggTIISgyw8nftGBIEo4zIOSY9aPWiiS/X5FtgQB1SGq9Gxn UFg+9RmbD7vjHQL/15oC7/RYyKZIsMc1vDmfrBvhoSb2pzj8YS/yc5/omIpasazW Z+idKzHwrLs40mnA2JwgSecXUR9xQLgYUTW9mx8tshAQup9XCNbnJ4VRLH+2IzCm Z3U/6nfOJ/xFfRt4gzBVKQ+Rbe6gIJFfVCzXIYQtMba6X5JDCvwIeebygfKsAzP6 rEH2W3OJUQnxcInFNveyY9cWWEviwkyvDWu2HS59IXvCs4LHaVPNe4ux1JhVLrI3 UCkSQa/+q318i+9vEPjWfCYsS7wjtxZCUnUz03ExDhp1Orj93tuhOk8oYI7Q+OHj VJ9kYlDUiyvMZsMZy1PlL5u+UUdJ7t2nbDKKBkKCV1vvwTM1Y1YGyDIYIcsBFD1v fZ0GqmeWhxLSKQwpZoDF/Mg2EVt120isgr8PifnTlBO2JfzG2wrtEKVEh64/oYDn 5RFnl9+5vH+4PFczHA8vje8DLzMdfZwf1aGQYQWky1fdFqvQ8DlvzvrVEKQTJk5e AFpfBZJ3exqQeNyxPH8U =Vjxs -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
