Tag Info

Hot answers tagged

3

Are you sure your server isn't configured to listen only on localhost (lo) interface? Look for its configuration and have it listen on all interfaces. The default startup script for Jboss has the following line to specify which IP address Jboss should bind itself to JBOSS_BIND_ADDR=${JBOSS_HOST:+"-b $JBOSS_HOST"} You can either edit this line or if ...


2

Lower numbered ports - lower than 1024 tend to be restricted to root users - the best/simplest way to get around this is to forward port 80 to 8080 internally at iptables or at the network's firewall, rather than at the application level.


2

Are you sure you haven't enabled the Firewall? sudo ufw disable This might be a security risk you can choose to ignore. If you want to configure your firewall later, check this documentation of ufw.


1

JEE artifacts such as JSP/ servlets / EJB run in a container. JEE defines strict guidelines on what a container is and how it is supposed to behave. For example tomcat is a servlet container. servlet container or for that matter any container provides for respective artifacts to run. Tomcat is only servlet container. it has the capability to run servlets. ...


1

for example in Terminal: sudo find / -name jboss will list all files/dirs starting with jboss


1

Web findings: The SiteMinder Application Server Agent protects resources on Java application servers that follow the Java 2 Enterprise Edition standard. These resources can be Java servlets, JavaServer Pages (JSPs), and Enterprise JavaBeans (EJBs). When a user requests a resource from an application server, the Agent intercepts ...


1

You could use Apache HTTP Server with the mod_proxy_balancer module.


1

You can use use Nginx !! Install nginx and add config file !!! http { upstream myproject { server 127.0.0.1:8000; server 127.0.0.1:8001; } server { listen 80; server_name localhost; location / { proxy_pass http://myproject; } } }



Only top voted, non community-wiki answers of a minimum length are eligible