Common Errors and Common Fixes
During development and usage of GDFR there may be a few common problems. Below are the errors and likely/suggested fixes.
Database Lockup / Not Responding
Sometimes the DBXML database enters what it calls "PANIC MODE" and will completely lock up. It can also lock up if, for some reason, it runs out of locks. To alleviate this problem make sure your server is shut down and no JVMs are accessing the database files. Then run the recovery script which is found in
deploy/scripts/run-recovery.sh. See also Database Recovery.
Mash-Up Displays Say "Loading ..."
The most common cause of this is the index used to look up a referenced record. Every mash-up display has a specific
.js file that controls what indexes are used. They are named according to the Collection, so the Formats mashup is called
formatsUI.js while the Agents mashup is
agentsUI.js. These are all found in the scripts directory under
tomcat/webapps/webservices. In the source tree you can find them under
conf/tomcat/webapps/webservices/scripts. To determine which index name should be used, open the Collections Collection record for the section that's not working. For example, if "Documents Authored" is stuck, open the record
Record Should Be Valid, But Is Declared Invalid
xml2record.xsl for a given Collection is incorrect or doesn't match
edit.xsl properly, then records can be formed incorrectly. The best way to see exactly why it's invalid is to remotely debug the application. In the class
CollectionBL.java, in both add and update, validation is done. Put a breakpoint right before validation occurs and inspect the value of the
decodedBytes. Copy this and paste it into an XML editor and attempt to validate it against the schema. The problem can be either that
xml2record.xsl has elements in the wrong order, or that the names listed in
xml2record.xsl don't match up correctly with the HTML form element names created in the corresponding
Cannot Find Declaration of Element ....
This happens when the validation tool cannot located the declared schema of a record. The schemas used for validation are stored within the application, specifically in the Schemas Collection. This means either the schema was not loaded properly, or the server is not responding. Verify that the schema is present and that the server is running and that Apache and Tomcat are operating correctly. The most common time for this to happen is immediately after the server is (re-)started.