database schema synchronization ( hasDDL="false") issue - Sequoia-3.0-beta2
----------------------------------------------------------------------------
Key: SEQUOIA-967
URL: https://forge.continuent.org/jira/browse/SEQUOIA-967
Project: Sequoia
Type: Bug
Versions: Sequoia 3.0 beta2
Environment: operating system-linux redhat, databse -PostgreSQL 8.0.3,
Jboss4/Hibernate/JDBC application. I'm using one controller with
sequoia-3.0-beta2 and two backends(backend1 & backend2) running with PostgreSQL
8.0.3.
Reporter: Rakitha Suranga
Priority: Blocker
Hi,
I'm using sequoia-3.0-beta2 and I disabled database schema synchronization
(hasDDL="false") since it's happening for each and every transcription. I think
system is very slow because of this reason (schema synchronization happening
for each and every transcription). It is taking long lime for save data to
database when going through sequoia-3.0-beta2.
The issue is now I can't start controller since following error.
----------------------------------------------------------------------------------
20:00:33,177 ERROR controller.xml.DatabasesParser Xml document has not been
validated.
20:00:33,178 ERROR controller.xml.DatabasesParser Attribute "hasDDL" is not
declared for element "DatabaseSchema".
20:00:33,180 WARN controller.core.Controller Loading of virtual databases
configuration file failed (because of Virtual database Xml configuration file
is not valid.).
org.xml.sax.SAXException: Virtual database Xml configuration file is not valid.
at
org.continuent.sequoia.controller.xml.DatabasesParser.readXML(DatabasesParser.java:316)
at
org.continuent.sequoia.controller.core.Controller.addVirtualDatabases(Controller.java:220)
at
org.continuent.sequoia.controller.core.Controller.loadXmlConfiguration(Controller.java:553)
at
org.continuent.sequoia.controller.core.ControllerConfiguration.setUpVirtualDatabase(ControllerConfiguration.java:372)
at
org.continuent.sequoia.controller.xml.ControllerParser.configureVirtualDatabase(ControllerParser.java:564)
at
org.continuent.sequoia.controller.xml.ControllerParser.startElement(ControllerParser.java:308)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1672)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
at
org.continuent.sequoia.controller.xml.ControllerParser.readXML(ControllerParser.java:121)
at
org.continuent.sequoia.controller.xml.ControllerParser.readXML(ControllerParser.java:171)
at
org.continuent.sequoia.controller.xml.ControllerParser.readXML(ControllerParser.java:200)
at
org.continuent.sequoia.controller.core.ControllerConfiguration.setUpByXml(ControllerConfiguration.java:232)
at
org.continuent.sequoia.controller.core.ControllerConfiguration.setup(ControllerConfiguration.java:288)
at
org.continuent.sequoia.controller.core.ControllerConfiguration.getController(ControllerConfiguration.java:314)
at
org.continuent.sequoia.controller.core.Controller.main(Controller.java:752)
20:00:33,184 ERROR controller.core.Controller Failed to send file to Sequoia
controller: org.continuent.sequoia.common.exceptions.ControllerException:
Loading of virtual databases configuration file failed (because of Virtual
database Xml configuration file is not valid.).
org.continuent.sequoia.common.exceptions.ControllerException: Loading of
virtual databases configuration file failed (because of Virtual database Xml
configuration file is not valid.).
Here is part of my virtualdatabase file:
---------------------------------------------------
<DatabaseSchema useStoredProcedures="true" useViews="false"
gatherSystemTables="false" hasDDL="false">
</DatabaseSchema>
1.Do we have hasDDL attribute for sequoia-3.0-beta2 version?
2.If it is yes how we can use it?
3.If it is no do we have any alternative way for disable schema synchronization?
4.Is there any identified reason for slowness when going through
sequoia-3.0-beta2?
I really appreciate if anybody can explain above queries.
Thanks
Rakitha
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
