brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-197) Fails to launch unless Internet access is available
Date Mon, 23 Nov 2015 13:25:11 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022090#comment-15022090
] 

Aled Sage commented on BROOKLYN-197:
------------------------------------

There are a few references to this:

* http://stackoverflow.com/questions/24123120/jetty-http-lookup-when-not-connected-to-internet
reports the same problem; no solution proposed there.

* email thread at http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2014-October/029970.html
proposes a couple of fixes (see the next messages in that thread for further discussion).
(subject: "[Bug 2029] web-storage-service fails to start if machine is not connected to the
internet")

* https://www.jfrog.com/jira/browse/RTFACT-3166 suggests removing Jetty's TLD scanner.

* http://markmail.org/thread/qtjk3w64bpyzyt3o

* http://osdir.com/ml/java.jetty.support/2003-05/msg00195.html suggests that Jetty should
always get the DTDs from $JETTY_HOME/etc/dtd, without having to go to the web.

I'm not convinced all of those links are relevant, based on the dates they were posted and
the date that Jetty 9.x was released (we are now on 9.2.13.v20150730, previously we were on
8.1.17.v20150415).

> Fails to launch unless Internet access is available
> ---------------------------------------------------
>
>                 Key: BROOKLYN-197
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-197
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Richard Downer
>
> Brooklyn 0.9.0-SNAPSHOT requires a connection to the public Internet to work. This is
a regression from Brooklyn 0.8.0.
> This is an issue when Brooklyn is launched into secured server environments. It is common
in many corporations that production servers have restricted egress access to the public Internet.
Therefore this is a major issue.
> The issue appears to be that Jetty is using Xerces to parse XML files; Xerces is trying
to resolve the DTDs by downloading them from the URL in the XML header. Therefore, it will
be trying to access http://java.sun.com. When this operation fails, the root webapp is not
deployed, and the Brooklyn web console (and probably the REST API too) returns 503 Service
Unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message