Recently, when a product is installed and deployed for the first time, the background throws the following exception: Causedby: java. SQL. SQLException: Schema
Recently, when a product is installed and deployed for the first time, the background throws the following exception: Caused by: java. SQL. SQLException: Schema
Recently, when a product is installed and deployed for the first time, the background throws the following exception:
Caused by: java. SQL. SQLException: Schema 'root' does not exist
At org. apache. derby. impl. jdbc. SQLExceptionFactory. getSQLException (Unknown Source)
At org. apache. derby. impl. jdbc. SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA (Unknown Source)
... 72 more
Caused by: ERROR 42Y07: Schema 'root' does not exist
At org. apache. derby. iapi. error. StandardException. newException (Unknown Source)
At org. apache. derby. impl. SQL. catalog. DataDictionaryImpl. getSchemaDescriptor (Unknown Source)
At org. apache. derby. impl. SQL. compile. QueryTreeNode. getSchemaDescriptor (Unknown Source)
At org. apache. derby. impl. SQL. compile. QueryTreeNode. getSchemaDescriptor (Unknown Source)
At org. apache. derby. impl. SQL. compile. FromBaseTable. bindTableDescriptor (Unknown Source)
At org. apache. derby. impl. SQL. compile. FromBaseTable. bindNonVTITables (Unknown Source)
At org. apache. derby. impl. SQL. compile. FromList. bindTables (Unknown Source)
At org. apache. derby. impl. SQL. compile. SelectNode. bindNonVTITables (Unknown Source)
At org. apache. derby. impl. SQL. compile. DMLStatementNode. bindTables (Unknown Source)
At org. apache. derby. impl. SQL. compile. DMLStatementNode. bind (Unknown Source)
At org. apache. derby. impl. SQL. compile. CursorNode. bindState
The exception is caused by the absence of Schema named "ROOT". Because the database uses the derby database and has a client tool on hand, unable to verify the problem. Or Google.
Keyword: Caused by: ERROR 42Y07: Schema 'root' does not exist, the result contains a xd Introduction"ContinuumThis is a blog post (Author: jiangshachina, address :). The author mentioned this problem and gave a clear explanation:
2.3 start Continuum
Assume that Continuum has been installed, but it has not been run. To run Continuum, double-clickContinuum_Home \ bin \ win32 \ run. batFile. For the first running, some errors will be reported:
......
Warn rdbms-Error initialising derby schema: Schema 'sa 'does not exist
ERROR 42Y07: Schema 'sa 'does not exist
......
This is normal, because the Continuum background uses the Apache Derby database. Before the first running, some tables and data required by Continuum do not exist. However, Continuum initializes the data. These errors will not occur when Continuum is started for 2nd times.
In this way, I started the product again and found the exception information in the background, which is continuously thrown out. It seems that the service is running and will be restarted after the background does not throw exceptions.
The background is normal !!!