Problem:
- Product Name: VisiBroker
- Product Version: 6.5 & 7.0
- Product Component: Object Activation Daemon (OAD) , oadutil
- Platform/OS Version: Windows XP, 2003
Why does oadutil throws "KEYSTONE: Uncaught Exception - st_StringTooLong" ?
Resolution:
Irrespective of VisiBroker installation directory location length, the oadutil in version 5.2.1 used to work without any issues. But in version 6.5 and 7.0, if the product installed directory is lengthy like C:\\mydir\\myapp_dir\\software\\vb7.0, then oadutil have issues in parsing the value of CLASSPATH variable (CLASSPATH value can be seen in oad output window when ran in debug mode "oad -v" ). This causes oadutil to throw "KEYSTONE: Uncaught Exception - st_StringTooLong".
This problem has been observed only when running applications with BOA implementation along with specific options passed to oadutil.
oadutil picks up all the jar file names from the vbj.config and passes them as value to CLASSPATH variable. Issue can be resolved by reducing the length of CLASSPATH value by combining multiple jar files into one jar and then removing combined jar file names in the vbj.config file. Issue can also be resolved by setting %VBROKERDIR% to a location with a shorter name such as C:\\VB70.
#Security
#VisiBroker
