When using a network loadbalancer to route the http traffic between two or more DMZ servers- incoming requests do not show up in the logs, why?
Article ID: KB0091684
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Resolution:
This may be true when a machine hosting DMZ has multiple NICs (or multiple IP addresses), BC may not know the default hostname and client will receive an error that looks like 'No Host matches server name 10.102.104.217'.
In order to rectify this error the following properties need to be added to DMZ's tra and must have same value:
bw.plugin.http.server.defaultHost=10.102.104.217
tibco.clientVar.gatewayProperties/transports/public/HTTP/host=10.102.104.217
Note: Ipaddress needs to be set appropriately for every machine hosting DMZ.
This may be true when a machine hosting DMZ has multiple NICs (or multiple IP addresses), BC may not know the default hostname and client will receive an error that looks like 'No Host matches server name 10.102.104.217'.
In order to rectify this error the following properties need to be added to DMZ's tra and must have same value:
bw.plugin.http.server.defaultHost=10.102.104.217
tibco.clientVar.gatewayProperties/transports/public/HTTP/host=10.102.104.217
Note: Ipaddress needs to be set appropriately for every machine hosting DMZ.
Issue/Introduction
When using a network loadbalancer to route the http traffic between two or more DMZ servers- incoming requests do not show up in the logs, why?
Feedback
Yes
No
Powered by
