| Summary | How many listen ports are used by Orbix services? |
|---|---|
| Article Number | 16549 |
| Environment | All Supported Operating Systems Orbix 6.3.4 |
| Question/Problem Description | How many listen ports are used by Orbix services? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | Each Orbix service (locator, node daemon, naming service, etc) is opening a service specific listener port. Further it can allocate several listener ports used for internal communication, the communication with the node daemon, for the PSS communication, etc. Ports not explicitly configured are kernel-assigned and can change from run to run. |
| Workaround | |
| Notes | Below is a typical example of port usage for Orbix services in a configuration repository based domain with Naming Service and Notification Service configured: CRF (itconfig_rep) Port POAs 33292 RootPOA 33293 it_pss_db 33294 it_ots_lite_transaction_factory_poa 33295 CFR specific, config change listener 3077 CFR specific Locator (itlocator) Port POAs 33607 RootPOA 33608 it_pss_db 33609 it_ots_lite_transaction_factory_poa 3075 Locator specific Node daemon (itnode_daemon) Port POAs 33610 RootPOA 33611 Node daemon specific, activator plugin POA 33612 it_pss_db 33613 it_ots_lite_transaction_factory_poa 3079 node daemon specific Naming Service (itnaming) Port POAs 33615 RootPOA 33616 it_pss_db 33617 it_ots_lite_transaction_factory_poa 3083 Naming Service specific Notification Service (itnotify) Port POAs 33618 RootPOA 33625 Notification specific, channel-0, consumer-0, supplier-0 3089 Notification specific, EventChannelFactory |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#Orbix
#KnowledgeDocs
