Page 1 of 1

DBWatcher issue

Posted: Mon Feb 13, 2006 6:25 pm
by Zebranky
Hades' Autobic DBWatcher will run fine for a while, then start producing messages like this in the cmd window:

Code: Select all

SQLException: Communication link failure: java.net.SocketException, underlying cause: Software caused connection abort: recv failed

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: Software caused connection abort: recv failed

STACKTRACE:

java.net.SocketException: Software caused connection abort: recv failed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(Unknown Source)
        at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1391)
        at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1538)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1929)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1167)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1278)
        at com.mysql.jdbc.MysqlIO.sqlQuery(MysqlIO.java:1224)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:2248)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:2196)
        at com.mysql.jdbc.Statement.execute(Statement.java:906)
        at l404.autobic.DBEnforcer.run(DBEnforcer.java:145)
        at l404.watcher.DBCheckerThread.checkLine(DBCheckerThread.java:277)
        at l404.watcher.DBCheckerThread.run(DBCheckerThread.java:302)
        at l404.watcher.DBCheckerThread.main(DBCheckerThread.java:537)


** END NESTED EXCEPTION **


SQLState: 08S01
VendorError: 0
I have to ^C it to start it working again, and then it eventually breaks again... any ideas?

Posted: Mon Feb 13, 2006 7:11 pm
by terryrayc
ya it does that. I have to restart mine once a day. It's probably a memory leak. It's on my list of things to check...but I'm not sure if the current source code is out there for it at all.

Posted: Mon Feb 13, 2006 7:27 pm
by Themicles
Wish that was something I had the power to look nito. Alas, I'm not a Java programmer...

All I can really say is that I've never had problems with DBWatcher, or the AutoBic/ELC modules for it. If you haven't already, try the package on the alternate FTP .

Posted: Mon Feb 13, 2006 10:30 pm
by Psyco
You running on windows or linux?

Posted: Mon Feb 13, 2006 10:34 pm
by Final Shinryuu
Psyco wrote:You running on windows or linux?
Hades is running on Windows.

Posted: Tue Feb 14, 2006 12:31 am
by JollyOrc
I got the same thing...

Posted: Tue Feb 14, 2006 2:26 pm
by Psyco
are you running mysql on the same box as the watcher or on a different box?

Posted: Tue Feb 14, 2006 2:55 pm
by JollyOrc
windows, same box. NWN is also running on that box.

Posted: Tue Feb 14, 2006 3:31 pm
by Zebranky
Same setup for Hades as JO described.

Posted: Tue Feb 14, 2006 9:21 pm
by Themicles
Tairis has MySQL, DBWatcher (With both AutoBIC and ELC), and NWServer with NWNX all on the same box. Also of note is that this is my main PC and at any given time, it has anything from TV tuner card software, to a high end game running.

Tairis is running Java 2 Runtime Environment 1.3.1_04.

Tairis has never seen any errors from DBWatcher except configuration errors.

Posted: Tue Feb 14, 2006 9:21 pm
by Psyco
The problem appears to be that your connection to mysql fails, and as the watcher is constantly checking the database for new jobs it throws that error pretty much as soon as the link fails.

What version of mysql are you running, and what version of the java mysql connector are you running?

You have the exact same setup as my test box at home which has never had this problem, so your specific setup should not be a problem.

Posted: Tue Feb 14, 2006 9:28 pm
by Themicles
Psyco wrote:What version of mysql are you running, and what version of the java mysql connector are you running?
Since Tairis' doesn't experience this, I'll answer the question as well to see if it helps anyone.

Tairis is currently running MySQL 4.0.20a-nt-max on Windows 2000.
The connector in use is the same as is in the package on the alternate FTP server.

EDIT: In case it helps any, I also have Tairis connecting to the DB through ODBC.

Posted: Tue Feb 14, 2006 10:20 pm
by Zebranky
MySQL 4.1.16-nt, same DBWatcher package as Tairis (I think).
We have a direct MySQL connection, though, not ODBC.

Posted: Tue Feb 14, 2006 11:20 pm
by Themicles
Zebranky wrote:MySQL 4.1.16-nt, same DBWatcher package as Tairis (I think).
We have a direct MySQL connection, though, not ODBC.
And Catara?

Psyco, you too, are you doing ODBC or direct?

Tairis does ODBC for service reasons. I run Tairis as a system service using srvany.exe. There are a number of issues with doing this. One of which is that I can't access any external connections, only local ones. Yes, MySQL is local in the case. But I may move it to another machine. In order for the GUI to show on my desktop, I have to run the service as LocalSystem. LocalSystem has NO network rights at all. To get network rights, I'd have to run it as any other account, but that wont allow the GUI to show on the desktop. Other services get around that by making the GUI a seperate executable that connects to the service.

Posted: Wed Feb 15, 2006 2:25 pm
by Psyco
- Direct connection, not ODBC
- I am using the latest watcher, this is the one that allows wings to be added and is currently running on avlis, pretty sure noone else has a copy of this one yet.
- mysql connector version 3.0.16 (sheesh, seems i am out of date there)
- mysql server 4.1
- windows 2000
- all running on the same box

Posted: Wed Feb 15, 2006 5:59 pm
by Themicles
Psyco wrote:- Direct connection, not ODBC
- I am using the latest watcher, this is the one that allows wings to be added and is currently running on avlis, pretty sure noone else has a copy of this one yet.
- mysql connector version 3.0.16 (sheesh, seems i am out of date there)
- mysql server 4.1
- windows 2000
- all running on the same box
Only similarity between the two "working" setups (Tairis and Psyco's test server) seems to be Windows 2000. Not conclusive, but anyone have any ideas along those lines that could prove or disprove this?

Posted: Wed Feb 15, 2006 10:12 pm
by Zebranky
Themicles wrote:anyone have any ideas along those lines that could prove or disprove this?
Hades is running on Win2K Pro. :P

Posted: Wed Feb 15, 2006 10:40 pm
by Themicles
Zebranky wrote:
Themicles wrote:anyone have any ideas along those lines that could prove or disprove this?
Hades is running on Win2K Pro. :P
Well, damn, there goes that.

Hrm... *continues thinking about the issue*

Posted: Thu Feb 16, 2006 2:51 am
by JollyOrc
I've shown the error message to a friend of mine who happens to be a java coder for a living...


I'm bound to have forgotten the exact details, but he says that the error message indicates that there are conflicting connections to the db and / or threads within the watcher that aren't closed properly.