On Sun, Sep 7, 2008 at 11:12 PM, Jon <[EMAIL PROTECTED]> wrote:
> No I'm stating that I had to reboot to get apache 'not running' on port 8080
> and it seemed unusual, because I ran the shutdown scripts.
Running the shutdown script doesn't guarantee anything -- there are
any number of reasons why
No I'm stating that I had to reboot to get apache 'not running' on port 8080
and it seemed unusual, because I ran the shutdown scripts. Has this problem
occured to anyone?
2008/9/8 Steve Ochani <[EMAIL PROTECTED]>
> >
> > 1.I´ve updated server.xml to change the default port from 8080 to
> > 80,
>
> 1.I´ve updated server.xml to change the default port from 8080 to
> 80, however, I´ve noted that restarting the server leaves apache
> tomcat listening on both ports 8080 and 80, until the server is
> rebooted.
>
Are you stating that you have to reboot twice?
Are you sure that it's tomcat tha
1. I've updated server.xml to change the default port from 8080 to 80,
however, I've noted that restarting the server leaves apache tomcat
listening on both ports 8080 and 80, until the server is rebooted.
Scripts executed
shutdown.sh
startup.sh
OS: RedHat Fedora 9 running Linux 2.6
