Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
OSGi Fragments let affected Modules start/stop endlessly (7.3.2+)
Hello,
In the two newest Liferay CE Versions 7.3.2 and 7.3.3 we have a problem with some OSGi fragments:
When we deploy e.g. a blogs-web-fragment, asset-publisher-web-fragment or social-bookmarks-taglib-fragment, the log just shows endlessly, that the affected module hast started and then stopped. Of course the module is not available afterwards.
For some other module fragments we found out, that there is a new gradle property per module fragment named "compile.jsp.include", but this hat no impact no the fragments named above.
Are there any other properties to set for module fragments?
We really miss a documentation for this.
Greets
In the two newest Liferay CE Versions 7.3.2 and 7.3.3 we have a problem with some OSGi fragments:
When we deploy e.g. a blogs-web-fragment, asset-publisher-web-fragment or social-bookmarks-taglib-fragment, the log just shows endlessly, that the affected module hast started and then stopped. Of course the module is not available afterwards.
For some other module fragments we found out, that there is a new gradle property per module fragment named "compile.jsp.include", but this hat no impact no the fragments named above.
Are there any other properties to set for module fragments?
We really miss a documentation for this.
Greets
Is there any progress on this issue? We are facing the same problem...
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™