CORBA 2.6.1 Programmer's Reference

name is too large. This field is generated by NonStop CORBA. This error can indicate a serious
error. Capture the ior and contact your service provider.
1624 - Object key error. Bad subdev name name
User Action: This error occurs during demarshalling of a file system profile if the subdevice field
is too long. This field is generated by NonStop CORBA. This error can indicate a serious error.
Capture the ior and contact your service provider.
1628 - Process must be named error
User Action: This error occurs when an application specifies the fs_server protocol and the
process is not (Guardian) named. Verify that the process is named. For example, to run the process
with a name of $XYZ, the user would (from an OSS shell) issue the command:
run -name=/G/xyz $JAVA_HOME/bin/java
1629 - Class loading error
User Action: This error occurs during the dynamic loading of a class file. The detailed error
message explains the exact problem.
1630 - IO error
User Action: This error occurs when there is an I/O error. The detailed error message specifies
which I/O operation failed.
1631 - demarshalled invalid policy list length, demarshalled invalid string length, demarshalled invalid
wstring length, demarshalled invalid encap length, demarshalled invalid repository id length,
demarshalled invalid operation length, demarshalled invalid principal length, demarshalled invalid
sequence length
User Action: This error occurs if a demarshalled length is larger than reasonable. Verify that the
data is not corrupt.
1632 - Skeleton threw unknown exception or org.omg.CORBA.portable.UnknownException
User Action: This warning (for unknown exception) or informational (for UnknownException)
message occurs when a skeleton throws an exception that is unexpected. For example,
java.lang.NullPointerException might be thrown by a skeleton. For an unkown
exception, analyze the logged stack trace and determine whether the skeleton needs to be
corrected. For an UnknownException, the message is informational.
1633 - (ZDOM-ORB-ERR33)
User Action: During the instantiation of the Java ORB, Java classes may internally be instantiated
using the Class.forName method. If the instantiation of the class fails, one of the following three
text messages (followed by the class name) is posted reporting the problem: "Class Not Found",
"Illegal Access Exception for Class", or "Instantiation Exception for Class". These messages might
indicate a problem with the JORB CLASSPATH not containing the class required for
instantiation, or a Java packaging access problem.
1634 - Persistent object key, but configured profile has a port number of zero
User Action: This warning occurs when a persistent object reference is marshalled with a