Hi Dave, OK, I fixed the failed test, so at least that problem is gone.
As for the in-memory DB issue, might you have forgotten to check out
roller-trunk/TestUtils? There's a good chance that might be why
"memory:" wasn't working for you, because switching back to non-memory
would require four files to be updated with the "memory:" removed, and
you mentioned below only flipping back two to get things to work:
grep -r "memory:" .
./app/src/test/resources/roller-jettyrun.properties:database.jdbc.connectionURL=jdbc:derby://localhost:3223/memory:rollerdb;create=true
./app/src/test/resources/roller-custom.properties:database.jdbc.connectionURL=jdbc:derby://localhost:3223/memory:rollerdb
./test-utils/src/main/java/org/apache/roller/weblogger/ant/StartDerbyTask.java:
"jdbc:derby://localhost:" + port + "/memory:rollerdb;create=true","APP",
"APP");
./test-utils/src/main/java/org/apache/roller/weblogger/ant/StopDerbyTask.java:
"jdbc:derby://localhost:" + port + "/memory:rollerdb";
Can you try a fresh check out of trunk into an empty directory and do an
mvn clean test there? If it still fails for you, feel free to just flip
the code back to regular DB for now.
Regards,
Glen
On 07/14/2013 04:21 PM, Dave wrote:
If I remove the string "memory:" from the two Roller property files in
test/src/resources then do not get that error and all test pass except for
the following:
Results :
Failed tests:
testUserLookups(org.apache.roller.weblogger.business.UserTest):
expected:<[userTest]User> but was:<[admin]User>
testRoleCRUD(org.apache.roller.weblogger.business.UserTest): expected:<2>
but was:<1>
Tests run: 130, Failures: 2, Errors: 0, Skipped: 0
Still digging...
- Dave
On Sun, Jul 14, 2013 at 4:11 PM, Dave <[email protected]> wrote:
I'm going to investigate now, but just in case anybody else knows what's
up...
--- ROOT CAUSE ---
java.sql.SQLNonTransientConnectionException: The connection was refused
because the database memory:rollerdb was not found.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
Thanks,
Dave
