No column name was specified for column 1 of 'x'. (#14)

Wojciech Kapcia (Tigase) opened 1 decade ago

2015-02-25 13:33:32.472 [in_0-message-archive]  JDBCMessageArchiveRepository.archiveMessage()  WARNING: Problem adding new entry to DB: <message from="user1_tovlp70206@x/1296724038-tigase-43" xmlns="jabber:client" to="user1_tovlp70206@x/1296724038-tigase-43" id="2xqrzp0211" type="chat"><body>d0kjzs0209</body></message>
2015-02-25 13:33:37.015 [in_0-message-archive]  MessageArchiveComponent.listCollections()  SEVERE: Error listing collections
tigase.db.TigaseDBException: Cound not retrieve collections
        at tigase.archive.db.JDBCMessageArchiveRepository.getCollections(JDBCMessageArchiveRepository.java:504)
        at tigase.archive.MessageArchiveComponent.listCollections(MessageArchiveComponent.java:307)
        at tigase.archive.MessageArchiveComponent.processActionPacket(MessageArchiveComponent.java:257)
        at tigase.archive.MessageArchiveComponent.processPacket(MessageArchiveComponent.java:111)
        at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1424)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: No column name was specified for column 1 of 'x'.
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
        at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
        at tigase.archive.db.JDBCMessageArchiveRepository.getCollectionsCount(JDBCMessageArchiveRepository.java:676)
        at tigase.archive.db.JDBCMessageArchiveRepository.getCollections(JDBCMessageArchiveRepository.java:471)
        at tigase.archive.MessageArchiveComponent.listCollections(MessageArchiveComponent.java:307)
        at tigase.archive.MessageArchiveComponent.processActionPacket(MessageArchiveComponent.java:257)
        at tigase.archive.MessageArchiveComponent.processPacket(MessageArchiveComponent.java:111)
        at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1424)

Activities

Andrzej Wójcik (Tigase) commented 1 decade ago

Need more details about build of Message Archiving component as this stacktrace do not match latest source code (number of lines with method invocations from stacktrace are pointing to different places is source code than it should).

I suppose this is older version of Message Archiving and JDBC storage support was changes since then so this might be fixed already. I would suggest to update installation to newest version if possible.

Wojciech Kapcia (Tigase) commented 1 decade ago

Thank you, it looks like the mentioned installation wasn't correctly deployed/updated as there is a version mismatch between server and MA.

componentInfo{Title=Tigase XMPP Server, Version=7.0.0-SNAPSHOT-b3799/45c26c0f (2015-02-19/01:13:39), Class=tigase.server.XMPPServer}
Loading component: message-archive :: componentInfo{Title=Tigase Message Archiving Component, Version=1.1.0-SNAPSHOT-b53/20e4c2c0, Class=tigase.archive.MessageArchiveComponent}

Type	Bug
Priority	Normal
Assignee	Artur Hefczyc
RedmineID	2793

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-message-archiving#14