i'm trying to configure haproxy on a red hat 7.1 machine (haproxy 1.5.4)

to proxy a few nodejs instances.

if i try to access on port 80 (haproxy frontend) it returns error 503 if i try to access on port 3000 (node app service), it returns ok

here my haproxy configuration:

global
    log         127.0.0.1 local2
    chroot      /var/lib/haproxy
    pidfile     /var/run/haproxy.pid
    maxconn     4000
    user        haproxy
    group       haproxy
    daemon
    stats socket /var/lib/haproxy/stats
defaults
    mode                    http
    log                     global
    option                  httplog
    option                  dontlognull
    option http-server-close
    option forwardfor       except 127.0.0.0/8
    option                  redispatch
    retries                 3
    timeout http-request    10s
    timeout queue           1m
    timeout connect         10s
    timeout client          1m
    timeout server          1m
    timeout http-keep-alive 10s
    timeout check           10s
    maxconn                 3000
frontend  main *:80
    default_backend             app
backend app
    balance     roundrobin
    server  app1 127.0.0.1:3000 check

Any guidance is welcome.

i have glassfish 4.1 running and checked the JK-Listener option on http-listener-2:

also i already installed apache (sudo yum install httpd) and created the following file on /etc/httpd/conf.d:

/etc/httpd/conf.d/ajp.conf

ProxyPass /painel ajp://localhost:8181/painel

ProxyPassReverse /painel ajp://localhost:8181/painel

But all that i got trying to use the ajp protocol was the 503 http error.

What i am missing?

if i change the protocol from ajp to http and port to 8080, it works. But the idea was to use the ajp.

Any help is welcome.

I have a t1.micro amazon instance and that machine have very scarce resources. I need for the moment to run glassfish3.1.1 (due to complete JEE6 support) on those conditions. Any guidance is welcome.

Using the default configuration (-Xmx512m) jvm halts at bootstrap since the SO have only ~ 620MB of total ram.

By setting -Xmx256m the server launches but it does not open the admin console.

Any help to fix it or to manage the server by other ways is welcome.

I want to install 2 individual websphere server (AppServer option in the installer) and later install the deployment manager and federate those server under it to make then a cluster.

Any help is welcome.

I already figured how to use wasservice[1] to up nodeagent and my faulty server1 (which wasn't starting on machine startup), and installed IBM HTTP Server, yet it's not in cluster.

Thanks in advance.

[1]http://pastebin.com/peihzsHY