How to bind all network interfaces to the configured HTTP channel port number.
Article ID: KB0086113
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
By default only one network interface listens to the port specified in the HTTP channel. How to bind all network interfaces to the configured HTTP channel port number?
Environment:
===========
TIBCO BusinessEvents 4.x/5.x
All Operating Systems
Symptoms:
=========
HTTPConnection binds to a single network interface only ("telnet <ipaddress> <port>" )
Cause:
======
This is the normal behaviour for channel serverType "BUILD-IN". (localhost as the hostname binds to the loopback address).
Resolution:
========
Change the serverType to "TomCat" in the channel configuration.
Note: Update the threading model to use "Caller" threads (Shared Queue not supported with serverType TomCat).
Description:
===========
By default only one network interface listens to the port specified in the HTTP channel. How to bind all network interfaces to the configured HTTP channel port number?
Environment:
===========
TIBCO BusinessEvents 4.x/5.x
All Operating Systems
Symptoms:
=========
HTTPConnection binds to a single network interface only ("telnet <ipaddress> <port>" )
Cause:
======
This is the normal behaviour for channel serverType "BUILD-IN". (localhost as the hostname binds to the loopback address).
Resolution:
========
Change the serverType to "TomCat" in the channel configuration.
Note: Update the threading model to use "Caller" threads (Shared Queue not supported with serverType TomCat).
Issue/Introduction
How to bind all network interfaces to the configured HTTP channel port number.
Feedback
Yes
No
Powered by
