I also could make the Default Connection Timeout on the db connection
string work, and setting the "correct" [mysqld] variables to legal
values that were high (as described at
http://opensimulator.org/wiki/0.7_Release#Before_you_upgrade ) also
did not change the 30 second Cmd time out on the migrations, so
something on the Opensim end and the way the data base operations are
done is timing out at 30 seconds as Alex has commented.
Note that a manual run of the add columns on the assets table in the
MySQL command line client on my setup worked fine. I only have 10000
assets and one add column for the assets table took just over 2
minutes. The second one took just over a minute. So a million assets
would likely take about 3 hours. I was on a reasonable powerful
Windows Vista dual core pentium processor system with 4GB of memory.
Sorry the threads on my replies get lost... its a result of getting
daily digests of mail rather than individual ones.
From: Frank Nichols <[email protected]>:
Agreed you "should" be able to use the connection string - however all
attempts to do that have failed. I did read some discussion about that in a
.net support forum and the conclusion was that it was by design that you
could not override the default command timeout using the connection string
argument. I am not a mysql person, so, I would be very happy to be wrong on
this - if someone can test it and show how to make the connection string
change work. Nebadon and I failed in several days of testing.
From Alex Ra <[email protected]>:
> You should be able to control the command timeout from the connection
> string:
>
> "Server=myServerAddress;Database=...;Default Command Timeout=20000;"
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
