Skip to main content

BES5.2.1 Failure# 1250 vbroker.naming.iorFile causes OBJECT_NOT_EXIST during naming service startup

  • February 16, 2013
  • 0 replies
  • 0 views

Problem:

  • Product Name: Borland Enterprise Server
  • Product Version: 5.2.1
  • Product Component: Naming Service
  • Platform/OS Version: All
  • JDK/Compiler Version: 1.4.1, 1.3.1

Setting the property vbroker.naming.iorFile in a nameservice config file will cause
NameService to throw OBJECT_NOT_EXIST exception.

Resolution:

This is a product failure in the JNDI portion of the NameService that
initializes the serial:// context used for storing Datasources and JMS objects
used by Borland Enterprise Server.

Workarounds:

Omit vbroker.naming.iorFile from the config file and pass as a java system
property e.g.

> nameserv -J-Dvbroker.naming.iorFile =/tmp/ns.ior -config ns.config NameService

If not using the serial context, as in a pure CORBA environment, remove asrt.jar
from CLASSPATH. When asrt.jar is not in the CLASSPATH, the NameService will skip
initialization of the serial:// context and avoid this error.


#Security
#VisiBroker