Ron McLeod wrote:Was the old version running on port 8081, or was it maybe running two instances of Tomcat - one for the UI and one for the document server?
Since you haven't found a reference to port 8081 in the running code, could there be a reference to port 8081 in the document metadata?
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:Welcome to the JavaRanch, Phil!
I think port 8081 is favored for appliance servers such as what you're describing. It's not an official standard or anything, but I think it's popular for that. You can use the "netstat -lnp" command on Linux to find what process owns port 8081, though.
Tomcat 5 is just as dead ad Tomcat 4. The absolute oldest Tomcat you should port to if you don't want to see everything break again in short order is Tomcat 6. Currently, I think Tomcat 9 is in Beta and Tomcat 8 is in primary production.
To find the ports that Tomcat uses, look at its conf/server.xml file and search for "port=". Port 8080 is the default http port, port 8005 is the control port, port 8009 is the AJP proxy port and port 8443 is the SSL (https) port.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:One other possibility might be that a proxy server (IIS, Apache, Nginx etc.) could be the one actually listening on port 8081 and forwarding to Tomcat. Or, on systems using a system like Linux iptables, port forwarding might happen at the device level.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:It could be.
There are 2 ways to reference port 8081 in Apache. If your config file is set to Listen on 8081, you've found the likely culprit (a netstat -lnp on Linux should show "apache2" or "httpd" as the port owner).
If your config file is using mod_proxy, though, then that's just set for Apache to send TO port 8081, and it's serving as a frontend for Tomcat.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:I don't think the Windows version of netstart can tell you what process owns a port.
Ron McLeod wrote:
Tim Holloway wrote:I don't think the Windows version of netstart can tell you what process owns a port.
With Windows its the -b option for netstat.
Phil has a Solaris platform - I don't think there is a netstat option to show the pid in Solaris.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.