SOLVED
Repoinit frequently giving issues on server restart
1 Accepted Solution
Correct answer by
set properties on /endkeyword
# using "end" instead of "endS" below causes parsing to fail
set endS to one
set two to endS
end
set properties on /forcedMultiValue
set singleMultiValue{String[]} to "single"
set singleLongMultiValue{Long[]} to 1243
end
The documentation shares 2 ways, in which we can set property.
- "set endS to one" this give us result
- set singleMultiValue{String[]} to "single" to a String[]. But, what we are getting is a String.
There is a discrepancy in forcibly using Arrays for a Single value.
Aanchal Sikka
Hello @Vani1012
Thanks for sharing your insights. It would definitely be a good improvement.
Since, this is a suggestion and not a question, requesting you to please post it as an idea, in "Ideas" Tab.
Aanchal Sikka
Hello @Vani1012
The repo-init scripts are meant to work during server start. If you are noticing error, you would need to fix them.
We shouldn't need to remove and put them back in.
- Arre these custom scripts?
- If yes, please share the errors logs.
-Why do we need to alter values with repo-init? (Single->Multi)
For now, we need to make sure, paths are available, before setting ACL or adding property.
The proper jcr:primaryType need to be used for creating nodes, as these can't be altered later
Aanchal Sikka
It will be difficult to debug with only configs. In original post you mentioned about exceptions, can you possibly share the same?
Aanchal Sikka
Hello @Vani1012
You should raise the bug for that array enforcement is not happening for single values.
set properties on /content/dam/techrevelaemsite/jcr:content
set cq:conf{String} to /conf/techrevelaemsite
set jcr:title{String} to "Techrevel AEM Site"
set test4{String[]} to "Techrevel AEM Site"
end
As per [0], following should create forced multi values.
set properties on /forcedMultiValue
set singleMultiValue{String[]} to "single"
set emptyMultiValue{String[]} to
set singleLongMultiValue{Long[]} to 1243
set emptyLongMultiValue{Long[]} to
end
[0]: https://sling.apache.org/documentation/bundles/repository-initialization.html
This would have avoided the exception in first place.
Which version of AEM are you using currently? Can you possibly try with latest Service pack?
Aanchal Sikka
Correct answer by
set properties on /endkeyword
# using "end" instead of "endS" below causes parsing to fail
set endS to one
set two to endS
end
set properties on /forcedMultiValue
set singleMultiValue{String[]} to "single"
set singleLongMultiValue{Long[]} to 1243
end
The documentation shares 2 ways, in which we can set property.
- "set endS to one" this give us result
- set singleMultiValue{String[]} to "single" to a String[]. But, what we are getting is a String.
There is a discrepancy in forcibly using Arrays for a Single value.
Aanchal Sikka
@Vani1012 Do you find the suggestions from users useful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity.
Kautuk Sahni
Related Conversations
