[ACCEPTED]-how can change derby to READ/WRITE mode-derby

Accepted answer
Score: 10

The reason I got the SQL error was due to 6 a lock file owned by root. I found it in 5 the .artifactory/derby directory, it was called db.lck, and removing 4 it got artifactory to start up just fine 3 again.

We run artifactory under Tomcat, and 2 the .artifactory directory was in the home 1 directory of the user that started Tomcat.

Score: 1

I cleaned up disk but I didn't reboot my 3 java process which connected to derby. I 2 killed the process and restarted it, derby 1 is in read/write mode.

More Related questions