...
- <host> - the URL for the web server on which you deployed database.war.
- <port> - port where the container is listening for http requests. This defaults to 8082 if the database connector was deployed in the tomcat bundle or port 8081 if you are running the Database Connector in Standalone mode.
- <queryset name> - queryset name defined in the database connector configuration file.
- <query name> – query name defined in the database connector configuration file.
Logfiles
Excerpt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
The database connector logging output is very helpful for troubleshooting database SQL issues. This example shows the log entry generated when browsing with an incorrect query name.
The database connector logs version information for each datasource definition as it makes initial contact with your database(s).
To log the actual SQL statement, arguments, number or rows returned and success status, set logging level to INFO. There are different logfiles for the Standalone and tomcat bundle installations. Standalone modeThere are four logfiles in <db-home>\database\database-connector-2.5.x\logs
Turning on DEBUG level logging
Tomcat bundleThe database connector writes all output to a single logfile <frevvo-home>\tomcat\logs\database-connector.YYYY-MM-DD.log Turning on DEBUG level logging
Switch the Database Connector log in JSON formatLogging output defaults to text format. To switch to JSON format, add thisproperty to the frevvo-config.properties for the frevvo-tomcat bundle or to dbconnector.properties file for the standalone bundle.
|
Common Problems
Doc Post Failure
If the a submission doesn't reach the Database Connector or when certain database operations fail, will
- Flag the submission with an error in the Submissions Table
- Send Doc Post Failure notification email(s) reporting information about the error to all tenant administrators or flow admins (if configured)
...
Example 1:
The email reports a Connection refused error - To resolve, verify the URL to your database connector is correct in business rules or Doc URI's
<< Add a screen image of the Submissions UI with error icon and on-hover >>
Emails with information about the failure will be sent when certain database operations fail.
Example 2:
All DBC SQL operations are performed within a database transaction. When the following SQL errors cause the transaction to be rolled backoccur, flags the submission with an error and generates Doc Action Failure emails to the tenant/flow admin(s) :
- An update statement updates ) rows and autocreate is false
- A query with autocreate=true is missing a create statement
- A query when autodelete is true and is missing the delete statement
- A query with the Delete statement and the delete Key is not defined
- A delete statement where the specified delete key cannot be found in the retreived retrieved resultset
- Browsing the URL to generate the schema for querysets
- Updates do not trigger errors due to several valid use cases for update failures ex: autocreate=true
- When calling a queryset If any one of the SQL operations (except Update) fails
- For example: When calling a querySet with 1 or more autocreate or autodelete=true,
- internally the DBC is likely to execute multiple SQL statements
- :
- It will try to delete all rows that were deleted from the form
- resultSet that were originally in the
- resultSet retrieved from the database.
- It will try to update rows from the form
- resultSet - and if autocreate is true and the update fails, it will execute an insert for each update failure.
- Browsing the URL to generate the schema for querysets
Updates do not trigger errors due to several valid use cases for update failures
...
ex: autocreate=true
Log entries for the error are captured in the database-connector.YYYY-MM-DD.log
Code Block |
---|
2017-10-26 13:46:05.828 ERROR mycompany 93f95ebc-6a85-4426-a015-eb34a1c96042 17048 --- [http-nio-8082-exec-8] c.f.connectors.database.QueryResource : Create operation not defined for query BIRT/createOrder
2017-10-26 13:46:05.829 INFO mycompany 93f95ebc-6a85-4426-a015-eb34a1c96042 17048 --- [http-nio-8082-exec-8] org.restlet.Component (2011499821) : 2017-10-26 13:46:05 127.0.0.1 - 127.0.0.1 8082 POST /database/BIRT/createOrder - 404 328 535 6 http://localhost:8082 Jakarta Commons-HttpClient/3.1 - |
Live Forms tomcat running on non-default port
...