On Mar 11, 2013 9:00 PM, "Alan Orth" <[email protected]> wrote:
>
> Helix,
>
> Ah, so you're right. For the record, I had been comparing our configs to
those in the dspace-3.0 release in preparation for upgrading from 1.8. I
pulled over some new syntax changes, including what I thought were defaults
in the new config file, such as db.maxconnections. Defining them as listed
in 3.0's dspace.cfg[1] resulted in a build error:
Glad that solved it for you. What do you mean by defining them as listed.
What's in your dspace.cfg and what in your build.properties?
> BUILD FAILED
> /home/aorth/src/git/DSpace/dspace/target/dspace-3.0-build/build.xml:88:
Property db.maxconnections was circularly defined.
>
> ... so I left it blank (or commented it out, I can't remember now).
That's how I ended up with the weird Cocoon crashes.
There's an important difference between those two, as the warning says.
> Anyways, I'm now up and running. If you think it's worth it, I'll submit
a bug report / pull request so we can hopefully stop others from running
into this same error?
I agree this is unfortunate, but I don't think this can be easily solved
properly.
The original issue introducing this feature is here:
https://jira.duraspace.org/browse/DS-1208
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
