Common problems

This topic covers problems that commonly occur during startup and runtime. You can use the messageTypeValidate element to validate all the message types as the system starts. The element is set to TRUE by default. You should set this element to FALSE once the system has passed its acceptance tests.

Errors at startup time

When the Visual Modeler is started by the servlet container, it logs its progress through initialization. Look for these errors in the console window or event log.

Error Cause and Solution
InputStream: 24, 384: "</Comergent>" expected. A syntax error in one of the configuration files has caused the DataManager to fail to initialize. You must correct the syntax error. The InputStream line provides the exact location of the error.
Env/main:W1:DATASERVICES Primary Connection Failed: Io exception: Connection refused(DESCRIPTION 

=(TMP=)(VSNNUM=135290880)
(ERR=12505)
(ERROR_STACK=
(ERROR=(CODE=12505)(EMFI=4))))
The server has failed to connect to the database server. Perform the following checks:

Ping the database server machine; there may be a network failure. Enter the IP address of the machine to see whether the host name can be resolved.

If you can ping the database server machine, then check that the database connection information that you have entered in the DataSources.xml file is correct. If possible, use an alternate database connection method. If this fails, then either the database is down or you have incorrect connection information.
Primary Connection Failed: No suitable driver The server has failed to find a valid Driver class in its classpath. Check that any JDBC driver specified in the DataServices.xml file lies in one of the classpath directories or archive files. In particular, check that an appropriate JDBC driver has been specified to connect to the database server: For Oracle Servers, you may use oracle.jdbc.odbc.OracleDriver.
Cannot find file=web-inf/HostedPartner.xml The initialization servlet has failed to find one of the properties files referred to in the main Comergent.xml file. Check the names and paths to the properties files. In a UNIX installation, check for case-sensitive file names.
Failed to create a NameKeyTable. com.comergent.dcms.util.ICCException: [CMGT_E_SCHEMA_KEY_GEN_NOT_FOUND] error: " Schema Error - DataObject: Promotion ExternalObject: PromotionControl specifies KeyGenerator: ControlKey which does not exist." A problem lies in your definition of the XML schema. On startup, the Visual Modeler reads the schema files and attempts to load the schema as an internal data structure. Exceptions are most commonly thrown when the definition of an element is omitted from the schema.

In this example, the Visual Modeler has read the DsRecipes.xml file, and attempted to load the Promotion DataObject. This DataObject includes in its definition file, Promotion.xml, a reference to a KeyGenerator element called "ControlKey". Inspection of the DsKeyGenerators file shows that no KeyGenerator element called ControlKey is declared.
java.net.BindException: Address in use A process is already bound to one of the ports that the Visual Modeler is attempting to use. You must either stop the existing process that is using the port or use a different port.
com.comergent.dcm.util.ICCException: [CMGT_E_UNKNOWN_ELEMENT] error: "Element: Comment of DataObject: Comment is not in the DCMS schema" An error has occurred while the DataManager initializes the schema. Check the definition of business and data objects. Check that a header DsElement has been declared for the data object and that DsElements are declared for each data element.
Comergent Init Servlet: DataManager NOT initialized com.comergent.dcm.util.ICCException: [CMGT_E_SCHEMA_KEY_GEN_NOT_FOUND] error: "Schema Error - DataObject: OrderAddress ExternalObject: OrderAddress specifies KeyGenerator: OrderAddressKey which does not exist." You have declared a KeyGenerator in the data object definition, but it is not defined in the KeyGenerators.xml file. Make sure that you have modified the correct KeyGenerators.xml file: this is usually OracleKeyGenerators.xml or MsSqlKeyGenerators.xml. Also make sure that your DataServices.xml file points to the correct KeyGenerators.xml file.
2002.10.22 13:33:03:459 Env/Thread-2:ER:DATASERVICES JDBCService.restore Error: ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], [] 

java.sql.SQLException: ORA-00600:
 internal error code, arguments:
 [ttcgcshnd-1], [0], [], [], [], 
[], [], []
at oracle.jdbc.dbaccess.DBError.throw
SqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.
processError(TTIoer.java:208)
...
There is a mismatch between the Oracle database version (usually 8i or 9i) and the JDBC driver that is being used to connect from the Visual Modeler. Check the classpath that the servlet container is using and remove any references to JDBC driver JAR files that come before the oraclejdbc.jar file in debs_home/Sterling/WEB-INF/.
Env/main:ER:MSGT Illegal Unresolved Reference to a MessageType: contentFrame A MessageTypeRef element references a message type definition that does not exist.
Env/main:ER:MSGT
com.comergent.api.dcm.messageType.
MessageTypeInstantiationException:
Failed instantiating or locating 
com.comergent.apps.partnerMkt.blc.
MissingBLC in 
MessageType GenericLoginDisplay
 A message type failed validation: typically, this means that one of its elements is missing such as a missing BLC, controller class, or JSP page.
2003.08.05 15:35:28:359 Env/Thread-6:ER:CORE java.lang.NoClassDefFoundError 

java.lang.NoClassDefFoundError
 at com.comergent.dcm.authentication.
UserPasswordCredentials.verify
(UserPasswordCredentials.java:38)
 at com.comergent.dcm.authentication.
LoginController.execute
(LoginController.java:59)
On startup, the Visual Modeler has tried to re-instantiate a session stored when the servlet container was last stopped. Before starting the servlet container, make sure that you have deleted any stored sessions.

Errors at runtime

Some errors are listed here that have occurred infrequently in running instances of the Visual Modeler.

Error Cause and Solution
Running iPlanet, you see the following in your browser:

GX Error (GX2GX) socket result code missing!!!

 There is a mismatch between the web.xml and ias‑web.xml files. All servlets mentioned in web.xml must have a corresponding entry in the ias-web.xml file. Use the kguidgen utility to generate a GUID for the servlet.