BLOCKING: https://camel.apache.org/schema/blueprint/cxf is down

[Andrea Dondoni <ad...@intesigroup.com>]

Hello All,
today we restart our serviceMix live environment but the system was not
restarted.

The problem is that this namespace
*https://camel.apache.org/schema/blueprint/cxf
<https://camel.apache.org/schema/blueprint/cxf>* actually is down.

How can I solve this?

This is a blocking problem for my company at this moment.

BR
Andrea

Re: BLOCKING: https://camel.apache.org/schema/blueprint/cxf is down

[Andrea Cosentino <an...@gmail.com>]

Sometimes, it would be nice to have a feedback from the reporter. We worked
hard to understand where it was the problem coming from.

Il giorno lun 6 dic 2021 alle ore 20:44 Andrea Cosentino <an...@gmail.com>
ha scritto:

> Thanks for the investigation Zoran.
>
> It worths to have a look at our dependencies related to blueprint and
> aries.
>
> Cheers!
>
> Il giorno lun 6 dic 2021 alle ore 20:39 Zoran Regvart <zo...@regvart.com>
> ha scritto:
>
>> Hi Andrea, Cameleers,
>> I think this might be caused by a change in the way websites are
>> served at ASF: in that all websites now redirect from `http` to
>> `https`. Notice of this change was sent on the users@infra.apache.org
>> mailing list[1] in October.
>>
>> Someone on the Zulip chat[2] just mentioned a similar (or identical)
>> issue. It could be that the resolver used to fetch the XML schemas
>> doesn't support or is not configured to follow redirects. A
>> question[3] on Stack Overflow on a similar (or identical) issue, seems
>> to point that this was fixed in a newer version of blueprint-core from
>> Aries. And that could be related to this issue[4] that was fixed in
>> blueprint-core 1.6.2.
>>
>> zoran
>>
>> [1] https://lists.apache.org/thread/wqh6f72lnwcjwon2jjdr8zwxp5r9mgb4
>> (requires authentication)
>> [2]
>> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Camel.20CXF.20issue
>> [3]
>> https://stackoverflow.com/questions/70239676/blueprint-container-error-on-osgi-bundle-start-up
>> [4] https://issues.apache.org/jira/browse/ARIES-1540
>>
>>
>> On Mon, Dec 6, 2021 at 9:21 AM Zoran Regvart <zo...@regvart.com> wrote:
>> >
>> > Hi Andrea,
>> > it seems that files from within `/schema/blueprint/cxf` were removed
>> > in 2015, I've restored them now[1] and when the website build[2]
>> > finishes in 30-40 minutes. They should be available. I don't know if
>> > this will fix the issue you're seeing, you did not provide enough
>> > details for me to be even remotely certain of that.
>> >
>> > In general I would advise you not to allow production systems
>> > arbitrary access to the Internet and I urge you to migrate to a newer
>> > version of Camel, old versions contain known security defects and
>> > you'll struggle getting, even commercial, support for them.
>> >
>> > zoran
>> >
>> > [1]
>> https://github.com/apache/camel-website/commit/315a5a4e26a194771e8deed457f5ebd4ab767097
>> > [2]
>> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/580/
>> >
>> > On Mon, Dec 6, 2021 at 1:37 AM Andrea Dondoni <ad...@intesigroup.com>
>> wrote:
>> > >
>> > > Hello All,
>> > > today we restart our serviceMix live environment but the system was
>> not
>> > > restarted.
>> > >
>> > > The problem is that this namespace
>> > > *https://camel.apache.org/schema/blueprint/cxf
>> > > <https://camel.apache.org/schema/blueprint/cxf>* actually is down.
>> > >
>> > > How can I solve this?
>> > >
>> > > This is a blocking problem for my company at this moment.
>> > >
>> > > BR
>> > > Andrea
>> >
>> >
>> >
>> > --
>> > Zoran Regvart
>>
>>
>>
>> --
>> Zoran Regvart
>>
>

Re: BLOCKING: https://camel.apache.org/schema/blueprint/cxf is down

[Andrea Cosentino <an...@gmail.com>]

Thanks for the investigation Zoran.

It worths to have a look at our dependencies related to blueprint and aries.

Cheers!

Il giorno lun 6 dic 2021 alle ore 20:39 Zoran Regvart <zo...@regvart.com>
ha scritto:

> Hi Andrea, Cameleers,
> I think this might be caused by a change in the way websites are
> served at ASF: in that all websites now redirect from `http` to
> `https`. Notice of this change was sent on the users@infra.apache.org
> mailing list[1] in October.
>
> Someone on the Zulip chat[2] just mentioned a similar (or identical)
> issue. It could be that the resolver used to fetch the XML schemas
> doesn't support or is not configured to follow redirects. A
> question[3] on Stack Overflow on a similar (or identical) issue, seems
> to point that this was fixed in a newer version of blueprint-core from
> Aries. And that could be related to this issue[4] that was fixed in
> blueprint-core 1.6.2.
>
> zoran
>
> [1] https://lists.apache.org/thread/wqh6f72lnwcjwon2jjdr8zwxp5r9mgb4
> (requires authentication)
> [2]
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Camel.20CXF.20issue
> [3]
> https://stackoverflow.com/questions/70239676/blueprint-container-error-on-osgi-bundle-start-up
> [4] https://issues.apache.org/jira/browse/ARIES-1540
>
>
> On Mon, Dec 6, 2021 at 9:21 AM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi Andrea,
> > it seems that files from within `/schema/blueprint/cxf` were removed
> > in 2015, I've restored them now[1] and when the website build[2]
> > finishes in 30-40 minutes. They should be available. I don't know if
> > this will fix the issue you're seeing, you did not provide enough
> > details for me to be even remotely certain of that.
> >
> > In general I would advise you not to allow production systems
> > arbitrary access to the Internet and I urge you to migrate to a newer
> > version of Camel, old versions contain known security defects and
> > you'll struggle getting, even commercial, support for them.
> >
> > zoran
> >
> > [1]
> https://github.com/apache/camel-website/commit/315a5a4e26a194771e8deed457f5ebd4ab767097
> > [2]
> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/580/
> >
> > On Mon, Dec 6, 2021 at 1:37 AM Andrea Dondoni <ad...@intesigroup.com>
> wrote:
> > >
> > > Hello All,
> > > today we restart our serviceMix live environment but the system was not
> > > restarted.
> > >
> > > The problem is that this namespace
> > > *https://camel.apache.org/schema/blueprint/cxf
> > > <https://camel.apache.org/schema/blueprint/cxf>* actually is down.
> > >
> > > How can I solve this?
> > >
> > > This is a blocking problem for my company at this moment.
> > >
> > > BR
> > > Andrea
> >
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
>

Re: BLOCKING: https://camel.apache.org/schema/blueprint/cxf is down

[Zoran Regvart <zo...@regvart.com>]

Hi Andrea, Cameleers,
I think this might be caused by a change in the way websites are
served at ASF: in that all websites now redirect from `http` to
`https`. Notice of this change was sent on the users@infra.apache.org
mailing list[1] in October.

Someone on the Zulip chat[2] just mentioned a similar (or identical)
issue. It could be that the resolver used to fetch the XML schemas
doesn't support or is not configured to follow redirects. A
question[3] on Stack Overflow on a similar (or identical) issue, seems
to point that this was fixed in a newer version of blueprint-core from
Aries. And that could be related to this issue[4] that was fixed in
blueprint-core 1.6.2.

zoran

[1] https://lists.apache.org/thread/wqh6f72lnwcjwon2jjdr8zwxp5r9mgb4
(requires authentication)
[2] https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Camel.20CXF.20issue
[3] https://stackoverflow.com/questions/70239676/blueprint-container-error-on-osgi-bundle-start-up
[4] https://issues.apache.org/jira/browse/ARIES-1540


On Mon, Dec 6, 2021 at 9:21 AM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Andrea,
> it seems that files from within `/schema/blueprint/cxf` were removed
> in 2015, I've restored them now[1] and when the website build[2]
> finishes in 30-40 minutes. They should be available. I don't know if
> this will fix the issue you're seeing, you did not provide enough
> details for me to be even remotely certain of that.
>
> In general I would advise you not to allow production systems
> arbitrary access to the Internet and I urge you to migrate to a newer
> version of Camel, old versions contain known security defects and
> you'll struggle getting, even commercial, support for them.
>
> zoran
>
> [1] https://github.com/apache/camel-website/commit/315a5a4e26a194771e8deed457f5ebd4ab767097
> [2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/580/
>
> On Mon, Dec 6, 2021 at 1:37 AM Andrea Dondoni <ad...@intesigroup.com> wrote:
> >
> > Hello All,
> > today we restart our serviceMix live environment but the system was not
> > restarted.
> >
> > The problem is that this namespace
> > *https://camel.apache.org/schema/blueprint/cxf
> > <https://camel.apache.org/schema/blueprint/cxf>* actually is down.
> >
> > How can I solve this?
> >
> > This is a blocking problem for my company at this moment.
> >
> > BR
> > Andrea
>
>
>
> --
> Zoran Regvart



--
Zoran Regvart

Re: BLOCKING: https://camel.apache.org/schema/blueprint/cxf is down

[Zoran Regvart <zo...@regvart.com>]

Hi Andrea,
it seems that files from within `/schema/blueprint/cxf` were removed
in 2015, I've restored them now[1] and when the website build[2]
finishes in 30-40 minutes. They should be available. I don't know if
this will fix the issue you're seeing, you did not provide enough
details for me to be even remotely certain of that.

In general I would advise you not to allow production systems
arbitrary access to the Internet and I urge you to migrate to a newer
version of Camel, old versions contain known security defects and
you'll struggle getting, even commercial, support for them.

zoran

[1] https://github.com/apache/camel-website/commit/315a5a4e26a194771e8deed457f5ebd4ab767097
[2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/580/

On Mon, Dec 6, 2021 at 1:37 AM Andrea Dondoni <ad...@intesigroup.com> wrote:
>
> Hello All,
> today we restart our serviceMix live environment but the system was not
> restarted.
>
> The problem is that this namespace
> *https://camel.apache.org/schema/blueprint/cxf
> <https://camel.apache.org/schema/blueprint/cxf>* actually is down.
>
> How can I solve this?
>
> This is a blocking problem for my company at this moment.
>
> BR
> Andrea



-- 
Zoran Regvart