January 25, 2010 at 8:19 am
Developer complaints this errors in the app log and they see connection time out issues
INFO | jvm 1 | 2010/01/22 01:36:05 | ##########################################################
INFO | jvm 1 | 2010/01/22 01:36:05 | Connection to the Database is lost. Trying to reconnect to the Database
INFO | jvm 1 | 2010/01/22 01:36:05 | Please Wait ...
INFO | jvm 1 | 2010/01/22 01:41:08 | Reconnected to the database
INFO | jvm 1 | 2010/01/22 01:41:08 | ##########################################################
INFO | jvm 1 | 2010/01/22 14:52:26 | ##########################################################
INFO | jvm 1 | 2010/01/22 14:52:26 | Connection to the Database is lost. Trying to reconnect to the Database
INFO | jvm 1 | 2010/01/22 14:52:26 | Please Wait ...
INFO | jvm 1 | 2010/01/22 14:57:28 | Reconnected to the database
INFO | jvm 1 | 2010/01/22 14:57:28 | ##########################################################
I found some errors on sql log below.
This below massages i found very frequently in logs Not really sure why they are showing up
1 transactions rolled back in database 'XXX' (). This is an informational message only. No user action is required.
10 transactions rolled forward in database 'XXX' (). This is an informational message only. No user action
is required.
This below massages i found in logs Not that frequent ONE LOG Daily suspecting some disk contention issues on the server ,But not sure how can i relate app log errors and these massages.
Message
SQL Server has encountered 307 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [\XXX.mdf] in database [XXX] (). The OS file handle is 0x0000000000000848. The offset of the latest long I/O is: 0x000007d1e70000
January 25, 2010 at 1:02 pm
Well this is a bit of a logical guess, but the I/O messages you are getting indicate the server is really busy with I/O or has bigger I/O problems.
Regardless,
I suspect your server is getting so busy it does not respond to the user requests and the app detects this and that is why you get the failures.
Deal with the I/O issue and everything else may then be fine.
January 25, 2010 at 1:08 pm
This is probably a IO sub system issues. I assume your Database Files and Log Files are all on same disks/Volumes. so the IO on your system is more than that your Disks can handle so the other IO's have to wait.
When we moved to a SAN most of our issues were resolved.
Maninder
www.dbanation.com
January 26, 2010 at 8:21 am
I agree that there are some definite IO issues on this server if you are seeing that many slow IO alerts being logged, but have you also checked to make sure that the database is not set to Auto_Close, it appears that the database is being re-opened frequently which shouldn’t be the case if Auto_Close is set to off.
January 26, 2010 at 8:46 am
Thanks ,i will take a look into I\O Subsystem and update with my findings.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply