leonv created DERBY-5990:
----------------------------
Summary: new BasicDeamon(derby.rawStoreDaemon)
Key: DERBY-5990
URL: https://issues.apache.org/jira/browse/DERBY-5990
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.5.1.1
Environment: windows running embedded database
Reporter: leonv
I'm starting a java program that creates a new or opens an existing database:
jdbc:derby:/derbyDB/Test123;create=true
All works fine.
Now I start a 2nd instance of that same program connecting to the same DB.
At this point a new "derby.rawStoreDaemon" daemon is created every second.
After the timeout occurs and with 50 or more threads created I'm finally
getting the expected exception:
"Another instance of Derby may have already booted the database "
I do expect all the exceptions, but there should be no need to start more then
1 "derby.rawStoreDaemon", or at least let it die once the database is in use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
