-
Notifications
You must be signed in to change notification settings - Fork 3
Description
"SQL exception value too long" experienced on Noark 5 excratoin:
Acos WebSak 6.8 Noark 5 v4.0
Acos Avlevering 1.1 Noark 5 v4.0
Even though Noark 5 v4.0 is not implemented in noark-extraction-validator yet, the extractor should still validate towards v3.1 as the command line call specifies.
Added the noark-extraction-validator console log in text and output as attached .txt.
Added 2 screenshots: showing end of last row registration P11 loependeJournal.xml integrity and the excel error tab E1 "The Storage writer is not listening. Most probably the writer thread encountered an unexpected error. Please verify the logs for more information".
C:\prog\noark-extraction-validator>"C:\Program Files\Java\jdk1.8.0_111\bin\java" -jar noark-extraction-validator-0.2.0-SNAPSHOT.jar noark53 -extraction "E:\uttrekk-n5\01" -output-dir "E:\uttrekk-n5\01-rapport\20171103_13.17.4525" -ignore-non-compliant-xml 1>"E:\uttrekk-n5\01-rapport\20171103_13.17.4525\dn5v_log.txt"
Exception in thread "Thread-2" com.documaster.validator.exceptions.StorageException: Storage writer encountered an unexpected error
at com.documaster.validator.storage.core.StorageWriter.run(StorageWriter.java:77)
Caused by: java.sql.SQLException: Value too long
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.setParameter(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.setObject(Unknown Source)
at com.documaster.validator.storage.database.DatabaseStorage.writeItem(DatabaseStorage.java:142)
at com.documaster.validator.storage.core.StorageWriter.run(StorageWriter.java:64)

