Deploying VDB To Teiid When a LoadBalancer is present

[flora_dim]

We have configured a httpd loadbalancer infront of the WildFly cluster such that requests to management console at localhost:9990 are mapped to http://wildfly:90. It is possible to access the admin console via http://wildfly:90/ . However when trying to deploy a VDB via the web console it gives an "Unexpected HTTP Response 415". However the same VDB can be successfully deployed by accessing the admin console at http://wildfly:9990/

Also we are trying to use the CLI tool to deploy the VDB. However when trying to run ./jboss-cli.sh controller=wildfly:90 and then connect it gives the following error.

The controller is not available at wildfly:90: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://wildfly:90. The connection failed: WFLYPRT0053: Could not connect to http-remoting://wildfly:90. The connection failed: Invalid response code 404

However ./jboss-cli.sh controller=wildfly:9990 works without any issues and we are able to connect to the remote controller.

I would appreciate it if you could help us resolve this issue. ( We are using WildFly 10.0.0 with Teiid 9.2.2)

Thank you.

[rareddy]

Seems like you still have issues with your load balancer proxy settings, Teiid is just another component in the WildFly system. It looks to me that your host mapping is fine but port mapping is not. Whatever configuration you did for port forwarding need to be looked at.

[flora_dim]

Hi Ramesh,

I replaced httpd with NGINX as the load balancer. Now by accessing  http://127.0.1.1:90/console/  I can deploy a VDB through the web interface.

However I need to deploy the VDB via CLI tool. When I try ./jboss-cli.sh --controller=127.0.0.1:90 and then issue connect it produces the following error.

Server at 127.0.0.1:90 does not support http-remoting

I would appreciate if you can explain to me if the approach of introducing a loadbalancer infront of Teiid and then calling loadbalaner's URL in jboss-cli.sh 's controller parameter correct.

If not what are the alternative ways using which I can deploy a VDB via a loadbalancer, so that I only communicate with the 80 or 433 port of the loadbalancer and loadbalancer handles deployment of VDB s via 9990 port?

Thank you.

[van.halbert]

It looks like ur using different IP addresses:   127.0.0.1:90  versus 127.0.1.1:90

[flora_dim]

Hi Van,

http://127.0.0.1:90/console too is working fine. Problem arises when trying to connect to the controller via CLI.

Thank you

[rareddy]

try ./jboss-cli.sh --controller=wildfly:90