Hi Chev,
I have a very similar problem, in my case nginx as a reverse proxy runs on a different instance than glassfish, but both then on a vmware esxi server.
Ex: nginx at 192.168.1.12 and glassfish 192.168.1.7. Its network interfaces are virtual, as there is no physical connection, I believe that the network connection is not the problem.
Everything works very well for a few days, then users start to complain about the damn "Bad Gateway" message. and when that happens in the nginx logs we have several:
"[error] 578654 # 578654: * 1055921 connect () failed (111: Connection refused) while connecting to upstream, client: 177.101.119.220, server: ...."
Apparently it seems that the glassfish is refusing the connection, I just restart the glassfish and everything works again, for a few days. It looks like something you mentioned, some limit of the glassfish being reached, but I don't have a very deep knowledge to investigate this type of thing. I know that memory and CPU usage are not the main problem as VMs are over-sized.
The strange thing is that when the "Bad Gatey" problem occurs via a proxy, I try to directly access the application on glassfish through its 192.168.1.7 and everything works.
Ja tentei muitas coisa que achei na internet e nada parece resolver.
Do you have any tip?
I have a very similar problem, in my case nginx as a reverse proxy runs on a different instance than glassfish, but both then on a vmware esxi server.
Ex: nginx at 192.168.1.12 and glassfish 192.168.1.7. Its network interfaces are virtual, as there is no physical connection, I believe that the network connection is not the problem.
Everything works very well for a few days, then users start to complain about the damn "Bad Gateway" message. and when that happens in the nginx logs we have several:
"[error] 578654 # 578654: * 1055921 connect () failed (111: Connection refused) while connecting to upstream, client: 177.101.119.220, server: ...."
Apparently it seems that the glassfish is refusing the connection, I just restart the glassfish and everything works again, for a few days. It looks like something you mentioned, some limit of the glassfish being reached, but I don't have a very deep knowledge to investigate this type of thing. I know that memory and CPU usage are not the main problem as VMs are over-sized.
The strange thing is that when the "Bad Gatey" problem occurs via a proxy, I try to directly access the application on glassfish through its 192.168.1.7 and everything works.
Ja tentei muitas coisa que achei na internet e nada parece resolver.
Do you have any tip?