More "SQLDataException: data exception: string data, right truncation" errors

[ne...@halloleo.hailmail.net]

Hi there

I get now & then a crash in daemon ZAP. In the log (and on the console) I find the following stack trace:

2014-03-11 16:26:46,623 WARN  ProxyListenerLog - data exception: string data, right truncation
java.sql.SQLDataException: data exception: string data, right truncation
    at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
    at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
    at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
    at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(Unknown Source)
    at org.parosproxy.paros.db.TableHistory.write(Unknown Source)
    at org.parosproxy.paros.db.TableHistory.write(Unknown Source)
    at org.parosproxy.paros.model.HistoryReference.<init>(Unknown Source)
    at org.parosproxy.paros.extension.history.ProxyListenerLog.addHistory(Unknown Source)
    at org.parosproxy.paros.extension.history.ProxyListenerLog.access$000(Unknown Source)
    at org.parosproxy.paros.extension.history.ProxyListenerLog$1.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:744)
Caused by: org.hsqldb.HsqlException: data exception: string data, right truncation
    at org.hsqldb.error.Error.error(Unknown Source)
    at org.hsqldb.error.Error.error(Unknown Source)
    at org.hsqldb.types.BinaryType.castOrConvertToType(Unknown Source)
    at org.hsqldb.types.BinaryType.convertToType(Unknown Source)
    at org.hsqldb.StatementDML.getInsertData(Unknown Source)
    at org.hsqldb.StatementInsert.getResult(Unknown Source)
    at org.hsqldb.StatementDMQL.execute(Unknown Source)
    at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
    at org.hsqldb.Session.execute(Unknown Source)
    ... 9 more

I'm using ZAP on WIndows & Enterprise under Java 7 started via the command line

java -Xmx1024m -XX:PermSize=256M -jar zap.jar -daemon

Any idea what this could cause?

Many thanks, Leo

[Simon Bennetts]

I'm guessing you received a particularly large response.
ZAP used to be able to handle 'unlimited' response bodies, but when we updated to a more recent version of hqlsdb we had to specify the maximum column sizes.
The request body column looks like it can be up to 16Mb.
Could one of your responses have been larger than that?

We should'nt fail in any case - I've raised an issues for it: https://code.google.com/p/zaproxy/issues/detail?id=1072 and will start a discussion on the dev group as to how we should handle this.

Thanks for reporting this,

Simon

[ne...@halloleo.hailmail.net]

This could be the case: I was pointing python's install tools at ZAP: When easyinstall searches its repositories it might use bigger chunks.

HTH, Leo