[
https://issues.apache.org/jira/browse/BROOKLYN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023132#comment-15023132
]
ASF GitHub Bot commented on BROOKLYN-197:
-----------------------------------------
GitHub user rdowner opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1056
BROOKLYN-197 Add jetty-schemas to launcher deps
Without this, Jetty will try to download XML schemas for the documents it
processes. This means that Brooklyn requires a working connection to the public
Internet. With this dependency, Jetty can discover the schemas it requires
without an Internet connection.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rdowner/incubator-brooklyn jira-BROOKLYN-197
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1056.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1056
----
commit dc0a642927c06726259baa9fada07bb4dbdcf0fa
Author: Richard Downer <[email protected]>
Date: 2015-11-23T21:33:27Z
BROOKLYN-197 Add jetty-schemas to launcher deps
Without this, Jetty will try to download XML schemas for the documents
it processes. This means that Brooklyn requires a working connection to
the public Internet. With this dependency, Jetty can discover the
schemas it requires without an Internet connection.
----
> 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
> Assignee: 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)
