[
https://issues.apache.org/jira/browse/SM-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454703#comment-17454703
]
Freeman Yue Fang commented on SM-4968:
--------------------------------------
The discussion I posted is from [email protected] mailing list
(https://lists.apache.org/[email protected])
I don't think restart servicemix would help.
The root problem is from recent http--->https redirect from ASF website/INFRA.
And actually the local xsd(from the jar file) should be resolved instead of
fetching the remote one(no matter it's http or https).
Servicemix distribution is way too old and AFAIK there's no plan to release new
Servicemix distribution. The org.apache.aries.blueprint.core - 1.6.1 in
servicemix 6.1.2 has known issue to resolve the local xsd
https://issues.apache.org/jira/browse/ARIES-1540
> org.xml.sax.SAXParseException: Premature end of file.
> -----------------------------------------------------
>
> Key: SM-4968
> URL: https://issues.apache.org/jira/browse/SM-4968
> Project: ServiceMix
> Issue Type: Bug
> Components: bundles
> Affects Versions: 6.1.x
> Reporter: Sandeep Rai
> Priority: Major
> Fix For: 6.1.x
>
>
> Below error started appearing for all running instances of servicemix 6.1.2
> version. Most of the bundles are not getting active and fall to failure.
> Seems like some recent changes on servicemix schema location has created it.
> 2021-12-07 12:58:34,140 | ERROR | Event Dispatcher | BlueprintContainerImpl
> | 15 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start
> blueprint container for bundle com.xxx.xx.xx.rabbitmq.rest/0.0.1.SNAPSHOT
> org.xml.sax.SAXParseException: Premature end of file.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
