Hi all,
I have seen some random downtimes of my production server in the
monitoring. Then I found out that the lucee/tomcat/logs/catalina.log
is infested with funny errors ( occuring with a frequency about 1 per
minute):
Jul 06, 2015 4:04:56 PM com.microsoft.sqlserver.jdbc.TDSReader
readPacketWARNING: ConnectionID:498 ClientConnectionId:
e222769b-7530-4882-8007-04bbb6c35281 TDS header contained invalid packet
length:0; packet size:8000Jul 06, 2015 4:04:56 PM
com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDSSEVERE:
ConnectionID:498 ClientConnectionId: e222769b-7530-4882-8007-04bbb6c35281
got unexpected value in TDS response at offset:0
I have completely no idea what is it about or how to troubleshoot it, but
it looks quite suspicious and I don’t recall seing it before.
I have tried to google it and have seen some people attributing similar
symptoms to either a bad query, db driver or a specific JVM version, but
could not see any fix really.
I am using Windows Server 2008 R2, Lucee 4.5.1.022 on Tomcat 7.0.59 and
java 1.7.0_76, Microsoft SQL Server 11.00.3128 and Microsoft JDBC Driver
4.0 for SQL Server 4.0.2206.100 (JDBC 4.0).
Would anybody know what is going on here ?
Best Regards
Ivan
A client of mine is seeing the same thing. we get this regardless of
which drivers we are using (i.e. the built in Microsoft and JTDS drivers)
I have recommended to upgrade to this driver for the moment to see if we
still get the errors (under load)
If anyone else knows more I am all ears!
MD> Ivan Rotrekl mailto:Ivan_Rotrekl
6 July 2015 15:45
Hi all,
I have seen some random downtimes of my production server in the
monitoring. Then I found out that the
/lucee/tomcat/logs/catalina.log/ is infested with funny errors (
occuring with a frequency about 1 per minute):
/Jul 06, 2015 4:04:56 PM com.microsoft.sqlserver.jdbc.TDSReader readPacket
WARNING: ConnectionID:498 ClientConnectionId:
e222769b-7530-4882-8007-04bbb6c35281 TDS header contained invalid
packet length:0; packet size:8000
Jul 06, 2015 4:04:56 PM com.microsoft.sqlserver.jdbc.TDSReader
throwInvalidTDS
SEVERE: ConnectionID:498 ClientConnectionId:
e222769b-7530-4882-8007-04bbb6c35281 got unexpected value in TDS
response at offset:0
/
I have completely no idea what is it about or how to troubleshoot it,
but it looks quite suspicious and I don’t recall seing it before.
I have tried to google it and have seen some people attributing
similar symptoms to either a bad query, db driver or a specific JVM
version, but could not see any fix really.
I am using Windows Server 2008 R2, Lucee 4.5.1.022 on Tomcat 7.0.59
and java 1.7.0_76, Microsoft SQL Server 11.00.3128 and Microsoft
JDBC Driver 4.0 for SQL Server 4.0.2206.100 (JDBC 4.0).
Would anybody know what is going on here ?
Best Regards
Ivan
You received this message because you are subscribed to the Google
Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to lucee+unsubscribe@googlegroups.com
mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com
mailto:lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/2c1e6f88-4729-4e28-865c-10df00f2bb24%40googlegroups.com
https://groups.google.com/d/msgid/lucee/2c1e6f88-4729-4e28-865c-10df00f2bb24%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.
Thanks ! Well, even though you have seen the error regardles of the driver
used, you would still recommend upgrading to the jTDS driver ? OK, I will
try it and see if it gets better.
I am no expert, but was also wondering, if perhaps upgrading to JVM 1.8
could fix it. Maybe, would you mind checking your client’s JVM version ?
That could give us some idea also…
Regards Ivan
I am seeing same errors under load running CentOS 7 and Lucee. Did
upgrading to Java 1.8 help? We are planning this in the near future but
might push that up if it helps resolve this issue also.
Thanks
Grant
Well, I have moved to a completely new server since then. It is using
Lucee on JVM 1.8 and I have not seen the error there any more.
But I cannot say it was the JVM upgrade which fixed it, as I have
upgraded so many other things ( windows, tomcat, iis, hyper-v to physical
server and so on).
At the end I could get rid of various issues at once, so it worked for
me the best like this.
Regards
Ivan