> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Sunday, August 04, 2013 9:23 AM
> To: Tomcat Users List
> Subject: Re: Help about my problem
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 8/3/13 9:39 AM, Nick Williams wrote:
>
> On Aug 3, 2013, at 1:55 AM, Mehdi Yousefi wrote:
>
>> Hi Thanks for your attention it is up on port 8000 but dident
>> respond this is for some medical use and the boss did not accept
>> a risk of
On Aug 3, 2013, at 1:55 AM, Mehdi Yousefi wrote:
> Hi
> Thanks for your attention
> it is up on port 8000
> but dident respond
> this is for some medical use and the boss did not accept a risk of
> updating to last version
Well, your boss is wrong and foolish then. Since this is for a medical
Hi
Thanks for your attention
it is up on port 8000
but dident respond
this is for some medical use and the boss did not accept a risk of
updating to last version
my log after startup is
Aug 2, 2013 9:49:42 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The Apache Tomcat Native libra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mehdi,
On 8/2/13 7:27 PM, Mehdi Yousefi wrote:
> Hi i have use Tom-Cat ver 6.0.10 and i have only one web site on
> this my problem is when i try to connect to web server on localhost
> or network computers browser status is changing to "connecting
> From: Mehdi Yousefi [mailto:mmeh...@gmail.com]
> Subject: Help about my problem
> i have use Tom-Cat ver 6.0.10
It's Tomcat, not Tom-Cat. Version 6.0.10 is over six years old and should not
be used by anyone these days. Doing so is irresponsible, given the number of
bug fixes and security
