Runtime Exception (Persistant Server ID is not set) occurs while running a VisiBroker 7.0 CORBA Server application in JBuilder Enterprise 2006
Problem:
Runtime Exception (Persistant Server ID is not set) occurs while running a VisiBroker 7.0 CORBA Server application in JBuilder Enterprise 2006
Resolution:
Product Name: BAS 6.6/ VisiBroker 7.0
Product Component: Integration with Borland JBuilder 2006 Enterprise
Platform/OS Version: Windows XP Professional
Purpose of Document:
?Runtime Exception (Persistant Server ID is not set) occurs while running a VisiBroker 7.0 CORBA Server application in JBuilder Enterprise 2006?, the purpose of this article is to explain the cause of this exception and how it can be prevented.
Problem Description:
While running a CORBA server using VisiBroker 7.0 with JBuilder 2006, what causes the following exception to occur and how this can be resolved?
com.sun.corba.se.impl.orb.ORBDataParserImpl getPersistentServerId
WARNING: "IOP00910206: (INITIALIZE) Persistent server ID is not set"
org.omg.CORBA.INITIALIZE: vmcid: SUN minor
code: 206 completed: Maybe
at
com.sun.corba.se.impl.logging.ORBUtilSystemException.persistentServeridNotSet(ORBUtilSystemException.java:3587)
This may appear due to several reasons, so first advice is to follow the steps described in Borland Help-->Developing Enterprise Applications-->Using JBuilder"s CORBA Tools-->Configuring VisiBroker stand-alone. If everything is setup as described in the reference but problem still persists then the most probable cause is that the installation directory for BAS/Visibroker got spaces in its path.
Entering spaces as part of the directory path for JBuilder in the installer, will cause JBuilder to throw this exception when running CORBA applications after the installation. The space displays correctly in the JBuilder text box of the installer. However, after the JBuilder installation, the directory name will have a broken path in place of the first space entered.
Solution/Workaround:
Do not use spaces or currency symbols in the path names when installing the BAS 6.6 or VisiBroker 7.0, if you later want to integrate it with the JBuilder Enterprise 2006. Though the above was tested in BAS 6.6 or VisiBroker 7.0, but this rule may be applicable to all BES/BAS/VisiBroker Installations.
Other points to remember:
For exception "org.omg.CORBA.NO_IMPLEMENT: This is a locally constrained object", set the following runtime parameter:
-Djava.endorsed.dirs= \lib\endorsed
Also, please do remember to set the runtime parameter for the license i.e.
-Dborland.enterprise.licenseDir= \var
-Dborland.enterprise.licenseDefaultDir= \license
Also, do remember to point to the VisiBroker installation (and not BAS) as BAS 6.6 installation can not be used for any Visibroker-based CORBA app deployment, as the license is now separated.
Author: Chetna Bakshi
