I am getting this in my logs, looks to be coming from Jive SBS 3.0.5 code:
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar []; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.
at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:97)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:607)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:641)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:666)
at com.jivesoftware.base.database.dao.JiveJdbcOperationsTemplate.queryScrollable(JiveJdbcOperationsTemplate.java:60)
at com.jivesoftware.community.impl.dao.RecentContentDAOImpl.getContent(RecentContentDAOImpl.java:353)
at com.jivesoftware.community.impl.dao.RecentContentDAOImpl.getRecentUserConatinerContent(RecentContentDAOImpl.java:330)
at com.jivesoftware.community.impl.dao.RecentContentDAOImpl.getRecentContent(RecentContentDAOImpl.java:116)
at com.jivesoftware.community.impl.RecentContentManagerImpl$1.run(RecentContentManagerImpl.java:166)
at com.jivesoftware.util.task.TaskEngine$TaskEngineWorker.run(TaskEngine.java:497)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source)
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:100)
at org.logicalcobwebs.proxool.ProxyStatement.intercept(ProxyStatement.java:57)
at $java.sql.Statement$$EnhancerByProxool$$5fd17b50.executeQuery(<generated>)
at org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStatement(JdbcTemplate.java:648)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:591)
... 8 more
Joel,
Any idea what action you are performing that is creating this error in the logs? Or does this happen on every page load?
-Curtis
I also noticed this the first time after logging in to our upgraded 3.0.4 -> 3.0.5 dev site. We're running the RPM w/the bundled Postgres installation. I'm not sure why it's occurring, and haven't yet spent much time trying to figure it out. If you'd like me to take a look, please let me know if there are any steps (e.g. turning up logging) that I should do before trying to reproduce.
This exception gets thrown when the server is started. I am 99% sure that I haven't even hit the site by the time this happens.
Now that I think back, you're right - it did happen when starting the server. Here's the log line immediately preceding the stack trace:
2009-07-04 23:00:30,232 [Task Engine Worker 1] ERROR com.jivesoftware.community.impl.RecentContentManagerImpl - Failed to initialize RecentContentManager:
I was able to reproduce this just a second ago, went ahead and filed a bug: CS-13991
Doesn't look like it causes any issues with the display of the recent content, but we will check into it further.
-Curtis
Joel,
With the most recent release of the support platform you can now see the status of all related cases via the 'Case Product Issues' widget that is located on the right of this discussion. At the moment the issue is still pending review from a product manager / developer.
-Curtis
Jive combines collaboration software, community software & social networking software into the leading SBS solution.
© Copyright 2000–2009 Jive Software. All rights reserved.
915 SW Stark St., Suite 400, Portland, OR 97205