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

ASF GitHub Bot commented on ARTEMIS-1731:
-----------------------------------------

Github user clebertsuconic commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1933
  
    @michaelandrepearce I thought the right way to do this was through using 
the actual HTTP location. and have tools to cache it somehow.
    
    In what scenario this is failing? on deploy on master, when running behing 
a firewal? or when using an external tool for this?


> Startup fails when XSD validation cannot access Internet
> --------------------------------------------------------
>
>                 Key: ARTEMIS-1731
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1731
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.5.0
>            Reporter: Ilkka Virolainen
>            Priority: Major
>
> After a recent change allowing splitting up the broker configuration across 
> multiple files, starting Artemis fails when the server running broker has no 
> Internet access. xml:specialAttrs references in artemis-configuration.xsd 
> fail because the schema location http://www.w3.org/2005/08/xml.xsd is 
> inaccessible. To reproduce, pull the latest master for 2.5.0-SNAPSHOT, block 
> www.w3.org and try to run a broker. Including the schema in the build would 
> resolve this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to