New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Startup error in 5.0.d configured w/o Lucene with new subsystem persister #132

Open
AFaust opened this Issue Dec 17, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@AFaust
Copy link
Contributor

AFaust commented Dec 17, 2018

BUG

Expected behavior

In a default Alfresco Community Edition 5.0.d install, the newest SNAPSHOT of OOTBee Support Tools with the subsystem persister feature can be installed and started without errors - there should be no interference since no properties have been persisted before (not supported in Community).

Actual behavior

The startup fails in a 5.0.d system that has been configured to use SOLR (which should be standard / the default) as the IndexConfigurationChecker bean is indirectly triggered by the new subsystem persistence mechanism and bemoans the non-existence of Lucene directories.

Steps to reproduce the behavior

  • setup Alfresco 5.0.d to use SOLR
  • install current OOTBee Support Tools 1.1.0.0-SNAPSHOT
  • startup

Additional details (analysis so far, log statements, references, etc.)

Tell us about your environment

Alfresco 5.0.d on Windows 10, Oracle JDK 1.8, Tomcat 7.0.47

@AFaust AFaust added the bug label Dec 17, 2018

@AFaust AFaust self-assigned this Dec 17, 2018

AFaust added a commit to AFaust/ootbee-support-tools that referenced this issue Dec 17, 2018

(OrderOfTheBee#132) Avoid implicit start during init
- Alfresco code will always (re)start a property backed bean when
  properties are set - even for non-updates
- issue remaining: implicit start for old persisted properties if
  subsystem should actually be inactive (relevant Alfresco code does not
  know / check enablement properties)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment