Muc error

below is the content of error.log, what’'s wrong with the Jive Messenger? And how to resolve this?

[org.jivesoftware.messenger.muc.spi.MUCPersistenceManager.loadRoomsFromDB(MUCPer sistenceManager.java:479)

]

java.sql.SQLException: [SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 2.

at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)

at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)

at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)

at com.microsoft.jdbc.base.BaseResultSet.getString(Unknown Source)

at org.jivesoftware.messenger.muc.spi.MUCPersistenceManager.loadRoomsFromDB(MUCPer sistenceManager.java:474)

at org.jivesoftware.messenger.muc.spi.MultiUserChatServerImpl.start(MultiUserChatS erverImpl.java:758)

at org.jivesoftware.messenger.XMPPServer.startModules(XMPPServer.java:313)

at org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:202)

at org.jivesoftware.messenger.XMPPServer.(XMPPServer.java:117)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.messenger.starter.ServerStarter.start(ServerStarter.java:82)

at org.jivesoftware.messenger.starter.ServerStarter.main(ServerStarter.java:46)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Hey semico,

Thanks for the bug report. It seems that the MSSQL JDBC driver is a little picky. For more information about this bug follow this link http://support.microsoft.com/kb/824106. I will try to fix it before we release JM 2.1.4 which is about to happen.

Thanks,

– Gato

Just an update. The problem has been fixed and the bug fix will be available in the next release and nightly build.

Thanks,

– Gato