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
RE: Error on deploy react portlet
Good morning to everyone.
I had created a portlet with yeoman and liferay-js-generator. I follow all steps that documentation says.https://help.liferay.com/hc/en-us/articles/360029147411-Installing-the-JS-Generator-and-Generating-a-Bundle
When i deploy my portlet get these errors:
However, the portlet seems to work fine.
My environment is:
It worries me, that this represents future problems in my application.
Thanks a lot.
I had created a portlet with yeoman and liferay-js-generator. I follow all steps that documentation says.https://help.liferay.com/hc/en-us/articles/360029147411-Installing-the-JS-Generator-and-Generating-a-Bundle
When i deploy my portlet get these errors:
Caused by: java.lang.ArrayIndexOutOfBoundsException
2020-07-16 11:28:36.100 INFO [fileinstall-D:/Liferay72/liferay-ce-portal-7.2.0-ga1/osgi/modules][BundleStartStopLogger:39] STARTED p1-js_1.0.0 [2322]
2020-07-16 11:28:36.103 ERROR [Framework Event Dispatcher: Equinox Container: c0df4f92-58a1-4673-993e-9b0de3cade1f][Framework:93] FrameworkEvent ERROR
java.lang.RuntimeException: org.osgi.framework.InvalidSyntaxException: Filter ended abruptly: (osgi.extender
at org.apache.aries.spifly.ConsumerBundleTrackerCustomizer.addingBundle(ConsumerBundleTrackerCustomizer.java:39)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:475)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:1)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:230)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:137)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:129)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:191)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
at org.eclipse.osgi.container.Module.start(Module.java:467)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:428)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1264)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1237)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316)
Caused by: org.osgi.framework.InvalidSyntaxException: Filter ended abruptly: (osgi.extender
at org.eclipse.osgi.internal.framework.FilterImpl$Parser.parse(FilterImpl.java:1462)
at org.eclipse.osgi.internal.framework.FilterImpl.newInstance(FilterImpl.java:147)
at org.eclipse.osgi.internal.framework.FilterImpl.newInstance(FilterImpl.java:143)
at org.osgi.framework.FrameworkUtil.createFilter(FrameworkUtil.java:81)
at org.apache.aries.spifly.ConsumerHeaderProcessor.findRequirement(ConsumerHeaderProcessor.java:268)
at org.apache.aries.spifly.ConsumerHeaderProcessor.processRequireCapabilityHeader(ConsumerHeaderProcessor.java:197)
at org.apache.aries.spifly.ConsumerHeaderProcessor.processHeader(ConsumerHeaderProcessor.java:80)
at org.apache.aries.spifly.BaseActivator.addConsumerWeavingData(BaseActivator.java:102)
at org.apache.aries.spifly.ConsumerBundleTrackerCustomizer.addingBundle(ConsumerBundleTrackerCustomizer.java:37)
... 20 more
Caused by: java.lang.ArrayIndexOutOfBoundsException
However, the portlet seems to work fine.
My environment is:
Liferay CE 7.2 GA1 with tomcat.
PostgreSQL database metadata.
It worries me, that this represents future problems in my application.
Thanks a lot.
Good morning.
The portlet seems work fine.
But always show that error on deploy.
Any suggestion?
Thank you!
The portlet seems work fine.
But always show that error on deploy.
Any suggestion?
Thank you!
Could you search in all the files in your portlet for "osgi.extender"?
Hi Cristoph.
I found these string in:
I found these string in:
D:\nodeJS\react-projects\p1\node_modules\liferay-npm-bundler\src\jar\index.js y D:\nodeJS\react-projects\p1\node_modules\liferay-npm-bundler\lib\jar\index.jsthe code in src\jar\index.js:
if (project.jar.requireJsExtender) {
let filter; const minimumExtenderVersion = getMinimumExtenderVersion(); if (minimumExtenderVersion) {
filter =
`(&` +
`(osgi.extender=liferay.frontend.js.portlet)` +
`(version>=${minimumExtenderVersion})` +
`)`;
} else {
filter = `(osgi.extender=liferay.frontend.js.portlet)`;
} manifest.addRequireCapability('osgi.extender', filter);
}
the code in lib\jar\index.js:
if (project_1.default.jar.requireJsExtender) {
let filter;
const minimumExtenderVersion = getMinimumExtenderVersion();
if (minimumExtenderVersion) {
filter =
`(&` +
`(osgi.extender=liferay.frontend.js.portlet)` +
`(version>=${minimumExtenderVersion})` +
`)`;
}
else {
filter = `(osgi.extender=liferay.frontend.js.portlet)`;
}
manifest.addRequireCapability('osgi.extender', filter);
}
Thanks!
Srikanth Reddy Sanivarapu, modified 5 Years ago.
Regular Member
Posts: 203
Join Date: 11/15/08
Recent Posts
Did you find the reason for this message on react NPM module? I am also facing the same issue. Thanks.
Hi! I had to migrate all my portal and aplications to liferay 7.2.1 GA2. It seems a bug in 7.2.0 GA1 version.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™