[
https://issues.apache.org/jira/browse/JCR-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-943.
-------------------------------
Committed the schema file in revision 541614. Thanks for the contribution!
The commit failure was caused by another issue (JCR-913) that was fixed in
trunk just yesterday. The failure can also be worked around by manually
creating the journal schema.
> SQL Server support in clustering module
> ---------------------------------------
>
> Key: JCR-943
> URL: https://issues.apache.org/jira/browse/JCR-943
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3
> Environment: SQL Server 2000 SP3, JTDS 1.2 driver
> Reporter: Hemanta Gupta
> Assigned To: Jukka Zitting
> Priority: Minor
> Fix For: 1.4
>
> Attachments: mssql.ddl
>
>
> I realize the clustering module doesn't specifically support SQL Server yet
> (there's no mssql.ddl), but I still tried to run the repository against SQL
> Server with clustering enabled in the hope that the default schema
> (default.ddl) would suffice. Apparently, it doesn't (unless I'm doing
> something very wrong), since I kept getting the following error whenever a
> write operation was attempted:
> 2007-05-25 14:48:06,757 WARN
> [org.apache.jackrabbit.core.journal.DatabaseJournal] Error while rolling back
> connection: You cannot rollback with autocommit set!
> 2007-05-25 14:48:06,757 ERROR
> [org.apache.jackrabbit.core.cluster.ClusterNode] Unable to commit log entry.
> org.apache.jackrabbit.core.journal.JournalException: Unable to append
> revision 1090.
> at org.apache.jackrabbit.core.journal.DatabaseJournal.append
> at
> org.apache.jackrabbit.core.journal.AppendRecord.update(AppendRecord.java:242)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode$WorkspaceUpdateChannel.updateCommitted(ClusterNode.java:530)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:725)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:855)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:326)
> at
> org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:313)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:302)
> at
> org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemStateManager.java:306)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1214)
> at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:849)
> Caused by: java.sql.DataTruncation: Data truncation
> at
> net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:379)
> at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781)
> at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224)
> at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628)
> at
> net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525)
> at
> net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487)
> at
> net.sourceforge.jtds.jdbc.JtdsPreparedStatement.execute(JtdsPreparedStatement.java:475)
> at
> org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:183)
> at org.apache.jackrabbit.core.journal.DatabaseJournal.append
> ... 58 more
> However, I think I got things working by using a modified version of
> default.ddl, with the only change being the type of the REVISION_DATA field
> (varbinary -> IMAGE).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
