We are having an issue with a Seam application deployed to a Glassfish server, connecting to a MS SQL Server 2008 R1.
The glassfish server suddenly started logging the following error:
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN
|_ThreadID=30;_ThreadName=httpSSLWorkerThread-8080-32;_RequestID=a1eaa1df-59f2-4eab-8f1f-aeeaf0915002;
|ConnectionID:24617: batch completion: Encountered unexpected unknown token (0x30)|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.Reader
|_ThreadID=30;_ThreadName=httpSSLWorkerThread-8080-32;_RequestID=a1eaa1df-59f2-4eab-8f1f-aeeaf0915002;
|ConnectionID:24617 got unexpected value in TDS response at offset:12|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN
|_ThreadID=42;_ThreadName=httpSSLWorkerThread-8080-38;_RequestID=86e50fbc-cde0-4ffe-a83e-4cca657f8669;
|ConnectionID:24617: FetchBufferTokenHandler: Encountered unexpected unknown token (0x30)|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.Reader
|_ThreadID=42;_ThreadName=httpSSLWorkerThread-8080-38;_RequestID=86e50fbc-cde0-4ffe-a83e-4cca657f8669;
|ConnectionID:24617 got unexpected value in TDS response at offset:12|#]
We had to stop this being logged through glassfish as it got to 30GB before we we're able to stop.
We have not been able to find any reason for what could have caused this.
Has anyone anywhere seen this before??!