> -----Original Message-----
> From: Christopher Schultz [mailto:chris@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,
>
> 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
> >> updating to last version
> >
> > Well, your boss is wrong and foolish then. Since this is for a
> medical
> > application of some sort, it is even /more/ imperative that you
> > upgrade. There have been /numerous/ security issues discovered and
> > fixed in Tomcat 6 in the last 6 years. By not upgrading, you are
> > exposing all of that sensitive medical information to those security
> > issues. You are putting your medical application at /greater/ risk by
> > not upgrading.
>
> +1
>
> If you are operating within the US, you can be criminally liable in
> cases where you are knowingly running under insecure configurations.
>
> Something is definitely wrong, because port 8000 is open but not
> responding at all. My experience was that the connection was opened,
> but stalled forever.
>
> If that's happening for you, too, take a thread dump to find out what
> Tomcat is doing.
>
> - -chris
Mehdi's last post indicates that he has at least one, if not several, severe configuration
issues.
Most likely, the app is never even starting -- though tomcat is setting up the connector on
port 8080.
Mehdi, you need to address the errors being presented in the log file you posted.
Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|