it happened on 3 different machines (2*win2000 1*win2003)
we have a big logger running at the same time and it tells nothing partiular
about the disk activity.
else i have had a mysql 4.0.x + 4.1.0 beta at home taking a lot of requests
for a quite a long time now (requests are performed thru php, not java this
time), and no crash ever occured.
that's why i was asking for a possible ConnectorJ issue. I'm gonna read its
changelog, who knows...
f.
- Original Message -
From: Victor Pendleton [EMAIL PROTECTED]
To: 'fabien marsaud' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 2:51 PM
Subject: RE: table crash (error127) using v4.0.15 JDBC
Are the crashes occurring on the same machines? Or random machines? Can
you
track the disk activity at the time the table is being marked as corrupt?
Are you tracking the database activity?
-Original Message-
From: fabien marsaud [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 5:52 AM
To: [EMAIL PROTECTED]
Subject: table crash (error127) using v4.0.15 JDBC
Hi
I'm working with mysql 4.0.15 for some software of ours and we are
experiencing a random table crash.
we have 30 MyISAM tables in our database and we're using JDBC to connect
to
them.
Sometimes, very rarely, one of the tables crashes. It has nothing special
compared to the other tables (int, varchars, datetimes and a blob), and
it's
one of the least accessed. We checked all the requests, they all work
separately. I may add that 6 processes are accessing the base at the same
time but only one of them is accessing the table that crashes, and there
are
always at least 5 seconds between each request on this table. for the
whole
base, there are 1 to 5 requests per second.
It seems it's a very random bug. Never crashed buring the development,
twice
during the tests, then not during some time, then once during some tests
at
the custommers', and until now, never during the production phase, whereas
there are far more requests than during the tests...
I know how to repair the tables, but our software being realtime, it's a
bit
annoying to have to stop everything, repair and restart. Even dropping and
creating the table again can lead to a further crash.
Well so here is my question : i'm wondering whether the crashes could come
from our version of the ConnectorJ : mysql-connector-java-2.0.14-bin.jar
??
nota bene : we couldn't use the 3.0.8 version at the moment we began
coding
because it had an annoying java access-rights bug (that seems corrected on
the 3.0.9).
Another possibility is some issue with using some toad-like mysql manager
at
the same time as the 6 processes...could be.
If any of you has experienced a compatibility issue related to mysql 4 and
connector 2, please be so kind as telling me.
Thanks
Fabien
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
