Hi, I'm getting the same thing. My database server is a physical SQL server, and my application (or enterprise server) is virtual. All Windows. We're on JDE 9.0. It doesn't happen very often, but I've seen it 3 or 4 times over the past few months. And it only seems to cause problems for the scheduler kernel. The other kernels show the same problem (database disconnect) in the log file, but seem to recover on their own. But after the error occurs, our scheduler sometimes errors out when trying to launch a job, but not always. So it will fail to launch one UBE, then a few hours later it will successfully launch one, then fail again. Strange indeed. My only resolution is to manually kill the scheduler process using the PID on the windows server, then restart it in JDE.
Here's an excerpt from one of my log files:
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.014000Jdbodbc.c8437
ODB0000163 - wSQLExecute failure. rc=-1
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.045000Jdbodbc.c8437
ODB0000164 - STMT:00 [08S01][10054][2] [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.060000Jdbodbc.c8437
ODB0000164 - STMT:01 [08S01][10054][2] [Microsoft][SQL Server Native Client 10.0]Communication link failure
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.076000Jdb_drvm.c1128
JDB9900401 - Failed to execute db request
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.076001Jtp_cm.c1347
JDB9900255 - Database connection to F91300 (System - 900) has been lost.
2344/2452MAIN_THREAD Wed Sep 21 16:02:03.139000Jtp_cm.c1301
JDB9900256 - Database connection to (System - 900) has been re-established.