Kbase 19406: Apptivity: Security Exception w/Deployed App in Netscape
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/03/2000 |
|
This document applies to: Apptivity Server and Runtime
Version and Release Number: 3.x
When running a deployed Apptivity Java application in a Netscape browser, you may encounter an error dialog indicating that the browser cannot connect to an unsigned applet, with a button to abort. Your application will not be allowed to run.
One possible cause of this error is the security exception org.omg.CORBA.NO_PERMISSION.
The CORBA NO_PERMISSION exception is thrown if the client attempts to execute a request which it does not have permission to perform. It contains a minor code, which gives more detailed information about what caused the exception, and a completion status. It may also contain a "reason" string describing the exception.
You can check for this exception by enabling the browser's Java console. The default debug level of the Java console is 1; using a debug level of 2 (by typing "2" while in the Java console) will allow the return of more information on this exception, including its minor code, completion status, and reason, in the following format:
org.omg.CORBA.NO_PERMISSION[minor=<code>,completed=<YES/NO>,reason=<string>]
This exception has been seen with minor=12121,completed=NO,reason=<IP address of host> where the project's apptivity.naming.host property is set to an IP address that is not listed in the etc\hosts file on the host where the Name Service can be found.
An application that encounters this exception in Netscape may run without error in Microsoft Internet Explorer (IE).
References To Written Documentation or Other KnowledgeBase Documents:
Kbase 18155 - Better Java security exception debugging info from Netscape
Kbase 19559 - Apptivity solving "Cannot locate Name Service" with Netscape
Deploying Apptivity Applications Version 3, Appendix A - Configuration Properties