Kbase 19559: Apptivity solving "Cannot locate Name Service" with Netscape
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/1/2000 |
|
Apptivity solving "Cannot locate Name Service" with Netscape Communicator 4.7 browser
This document applies to: Apptivity
Version and Release Number: 3.x
When running a deployed Apptivity Java application in a Netscape Communicator 4.7 browser an error :
Connection error - "Could not locate Name Service" may appear
while the same Application runs fine with an Internet Explorer
(e.g. IE 5) browser .
Increasing the debug level inside Netscape's Java console
the produced stack trace says:
org.omg.CORBA.NO_PERMISSION[minor=12121,completed=NO,reason=test.dev.net]
The reason of the problem is the different security implementation of Netscape and IE
causing Netscape following the rule that an Applet has no permission to read local
files to stop with that security exception if the Applet tries to read the IP-Address from
the hosts file e.g. on etc/hosts.
The solution for the problem is to :
1. change the property inside the deployed <project>.properties file from using the host name e.g.:
apptivity.naming.host=test.dev.net
to contain the the appropriate IP address instead e.g.:
apptivity.naming.host=192.123.123.123
2. Change the host name property for starting the Distribution Manager e.g.:
-Dapptivity.dmanager.host=test.dev.net
to use the appropriate IP address instead e.g.:
-Dapptivity.dmanager.host=192.123.123.123
3. Change the host name properties for the Component Manager startup to e.g.:
-Dapptivity.cmanager.host=192.123.123.123
and
-Dapptivity.naming.host=192.123.123.123
in the same way.
References To Written Documentation or Other
KnowledgeBase Documents:
KB 18348
KB 19527
KB 19406
KB 18155
KB 18469
KB 18595