[jira] [Resolved] (ANY23-392) Lunching maven-jetty-plugin: Problem accessing /apache-any23-service/resources/form.html

2018-08-30 Thread Jacek Grzebyta (JIRA)


 [ 
https://issues.apache.org/jira/browse/ANY23-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek Grzebyta resolved ANY23-392.
--
Resolution: Fixed
  Assignee: Jacek Grzebyta

> Lunching maven-jetty-plugin: Problem accessing 
> /apache-any23-service/resources/form.html
> 
>
> Key: ANY23-392
> URL: https://issues.apache.org/jira/browse/ANY23-392
> Project: Apache Any23
>  Issue Type: Bug
>  Components: service
>Affects Versions: 2.3
>Reporter: Jacek Grzebyta
>Assignee: Jacek Grzebyta
>Priority: Major
>
> When using {{maven-jetty-plugin}} web container starts properly but when I 
> try to access root web page: [http://localhost:8080/apache-any23-service/] I 
> have error:
>  
> {code:java}
> HTTP ERROR 404
> Problem accessing /apache-any23-service/resources/form.html. Reason:
> Not Found
> {code}



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


[GitHub] any23 pull request #119: ANY23-392: Add configuration for maven-jetty-plugin

2018-08-30 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/any23/pull/119


---


[jira] [Commented] (ANY23-392) Lunching maven-jetty-plugin: Problem accessing /apache-any23-service/resources/form.html

2018-08-30 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ANY23-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598035#comment-16598035
 ] 

ASF GitHub Bot commented on ANY23-392:
--

Github user asfgit closed the pull request at:

https://github.com/apache/any23/pull/119


> Lunching maven-jetty-plugin: Problem accessing 
> /apache-any23-service/resources/form.html
> 
>
> Key: ANY23-392
> URL: https://issues.apache.org/jira/browse/ANY23-392
> Project: Apache Any23
>  Issue Type: Bug
>  Components: service
>Affects Versions: 2.3
>Reporter: Jacek Grzebyta
>Priority: Major
>
> When using {{maven-jetty-plugin}} web container starts properly but when I 
> try to access root web page: [http://localhost:8080/apache-any23-service/] I 
> have error:
>  
> {code:java}
> HTTP ERROR 404
> Problem accessing /apache-any23-service/resources/form.html. Reason:
> Not Found
> {code}



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


[jira] [Commented] (ANY23-373) Web page /install.html: software version variable was not decoded.

2018-08-30 Thread Hans Brende (JIRA)


[ 
https://issues.apache.org/jira/browse/ANY23-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597914#comment-16597914
 ] 

Hans Brende commented on ANY23-373:
---

[~grzebyta.dev] Yeah, it looks like the site was last published 2018-03-23. 

[~lewismc] How do we update the site more regularly?

> Web page /install.html: software version variable was not decoded.
> --
>
> Key: ANY23-373
> URL: https://issues.apache.org/jira/browse/ANY23-373
> Project: Apache Any23
>  Issue Type: Bug
>  Components: documentation, site
>Reporter: Jacek Grzebyta
>Assignee: Hans Brende
>Priority: Minor
> Fix For: 2.3
>
>
> Web page {{/install.html}} contains unsolved {{$project.version}} variable in 
> text.
> For example:
> {code}
> Unzip the distribution archive, i.e. apache-any23-$project.version-bin.zip to 
> the directory you ...
> {code}



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


[jira] [Commented] (ANY23-394) JSON-LD Extractions Flag Errors in Google's Structured Data Tooling

2018-08-30 Thread Hans Brende (JIRA)


[ 
https://issues.apache.org/jira/browse/ANY23-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597900#comment-16597900
 ] 

Hans Brende commented on ANY23-394:
---

[~lewismc] Do you disagree or should we mark this issue as "not a bug"?

> JSON-LD Extractions Flag Errors in Google's Structured Data Tooling
> ---
>
> Key: ANY23-394
> URL: https://issues.apache.org/jira/browse/ANY23-394
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: extractors, json-ld, service
>Affects Versions: 2.2
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 2.3
>
>
> Hi Folks,
> I recently ran the following extraction
> http://any23-vm2.apache.org/any23/?format=jsonld=https%3A%2F%2Fcmr.earthdata.nasa.gov%2Fsearch%2Fconcepts%2FC179003620-ORNL_DAAC.html=none
> ...which resulted in the below extraction. If you load this into the Google's 
> tooling, http://search.google.com/structured-data/testing-tool you will see 
> many errors. We need to work to address these. I will be investigating. 
> {code}
> {
>   "@graph" : [ {
> "@id" : "_:n0sbl",
> "http://www.w3.org/1999/xhtml/vocab#role; : [ {
>   "@id" : "http://www.w3.org/1999/xhtml/vocab#main;
> } ]
>   }, {
> "@id" : "_:n1sbl",
> "http://www.w3.org/1999/xhtml/vocab#role; : [ {
>   "@id" : "http://www.w3.org/1999/xhtml/vocab#complementary;
> } ]
>   }, {
> "@id" : "_:node1cm0fum9mx85",
> "@type" : [ "http://schema.org/Dataset; ],
> "http://schema.org/alternateName; : [ {
>   "@language" : "en",
>   "@value" : "1860_1993_2050_NITROGEN_830_1"
> } ],
> "http://schema.org/citation; : [ {
>   "@id" : "_:node1cm0fum9mx87"
> } ],
> "http://schema.org/dateCreated; : [ {
>   "@type" : "http://www.w3.org/2001/XMLSchema#date;,
>   "@value" : "2006-04-14"
> } ],
> "http://schema.org/dateModified; : [ {
>   "@type" : "http://www.w3.org/2001/XMLSchema#date;,
>   "@value" : "2006-04-14"
> } ],
> "http://schema.org/description; : [ {
>   "@language" : "en",
>   "@value" : "This data set provides global gridded estimates of 
> atmospheric deposition of total inorganic nitrogen (N), NHx (NH3 and NH4+), 
> and NOy (all oxidized forms of nitrogen other than N2O), in mg N/m2/year, for 
> the years 1860 and 1993 and projections for the year 2050. The data set was 
> generated using a global three-dimensional chemistry-transport model (TM3) 
> with a spatial resolution of 5 degrees longitude by 3.75 degrees latitude 
> (Jeuken et al., 2001; Lelieveld and Dentener, 2000). Nitrogen emissions 
> estimates (Van Aardenne et al., 2001) and projection scenario data (IPCC, 
> 1996; 2000) were used as input to the model."
> } ],
> "http://schema.org/distribution; : [ {
>   "@id" : 
> "https://daac.ornl.gov/daacdata/global_climate/global_N_deposition_maps/;
> } ],
> "http://schema.org/identifier; : [ {
>   "@id" : "_:node1cm0fum9mx86"
> } ],
> "http://schema.org/keywords; : [ {
>   "@language" : "en",
>   "@value" : "EARTH SCIENCE,ATMOSPHERE,ATMOSPHERIC CHEMISTRY,NITROGEN 
> COMPOUNDS,NITROGEN OXIDES"
> } ],
> "http://schema.org/name; : [ {
>   "@language" : "en",
>   "@value" : "Global Maps of Atmospheric Nitrogen Deposition, 1860, 1993, 
> and 2050"
> } ],
> "http://schema.org/potentialAction; : [ {
>   "@id" : "_:node1cm0fum9mx88"
> } ],
> "http://schema.org/provider; : [ {
>   "@language" : "en",
>   "@value" : "\nORNL_DAAC\n  "
> } ],
> "http://schema.org/sameAs; : [ {
>   "@id" : 
> "https://daac.ornl.gov/CLIMATE/guides/global_N_deposition_maps.html;
> }, {
>   "@id" : "https://doi.org/10.3334/ORNLDAAC/830;
> }, {
>   "@id" : 
> "https://daac.ornl.gov/daacdata/global_climate/global_N_deposition_maps/comp/deposition_maps.jpg;
> }, {
>   "@id" : 
> "https://daac.ornl.gov/daacdata/global_climate/global_N_deposition_maps/comp/global_N_deposition_maps.pdf;
> }, {
>   "@id" : 
> "https://daac.ornl.gov/daacdata/global_climate/global_N_deposition_maps/comp/global_N_deposition_maps_readme.pdf;
> }, {
>   "@id" : "https://daac.ornl.gov/graphics/browse/sdat-tds/830_1_fit.png;
> }, {
>   "@id" : "https://webmap.ornl.gov/wcsdown/dataset.jsp?ds_id=830;
> } ],
> "http://schema.org/spatialCoverage; : [ {
>   "@language" : "en",
>   "@value" : "-90.0 -180.0 90.0 180.0"
> } ],
> "http://schema.org/temporalCoverage; : [ {
>   "@type" : "http://www.w3.org/2001/XMLSchema#date;,
>   "@value" : "1860-01-01"
> } ],
> "http://schema.org/version; : [ {
>   "@language" : "en",
>   "@value" : "1"
> } ]
>   }, {
> "@id" : "_:node1cm0fum9mx86",
> 

[jira] [Updated] (ANY23-370) Jenkins: IllegalStateException: checksum mismatch

2018-08-30 Thread Hans Brende (JIRA)


 [ 
https://issues.apache.org/jira/browse/ANY23-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hans Brende updated ANY23-370:
--
Summary: Jenkins: IllegalStateException: checksum mismatch  (was: Jenkins 
builds are timing out)

> Jenkins: IllegalStateException: checksum mismatch
> -
>
> Key: ANY23-370
> URL: https://issues.apache.org/jira/browse/ANY23-370
> Project: Apache Any23
>  Issue Type: Bug
>  Components: CIS (Jenkins)
>Affects Versions: 2.3
>Reporter: Hans Brende
>Priority: Critical
> Fix For: 2.3
>
>
> Jenkins builds (e.g., 
> [#1597|https://builds.apache.org/job/Any23-trunk/1597/]) have been 
> sporadically timing out after 120 minutes during the *archival process*, even 
> though the actual *build process* completes successfully in less than half an 
> hour. I believe that this is due to the following error:
> {noformat}
> ERROR: Failed to archive \{ 
> org.apache.any23/apache-any23-service/2.3-SNAPSHOT/apache-any23-service-2.3-SNAPSHOT.pom=pom.xml,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48.war=target/apache-any23-service-2.3-SNAPSHOT.war,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.war=target/apache-any23-service-2.3-SNAPSHOT-without-deps.war,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-with-deps.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-with-deps.tar.gz,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-with-deps.zip=target/apache-any23-service-2.3-SNAPSHOT-with-deps.zip,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-without-deps.tar.gz,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.zip=target/apache-any23-service-2.3-SNAPSHOT-without-deps.zip,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-server-embedded.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-server-embedded.tar.gz,
>  
> org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-server-embedded.zip=target/apache-any23-service-2.3-SNAPSHOT-server-embedded.zip
> } due to internal error; falling back to full archiving {noformat}
> {noformat}java.lang.IllegalStateException: End of stream while reading number
>  at jsync.protocol.BaseReader.readLong(BaseReader.java:40)
>  at jsync.protocol.BaseReader.readInt(BaseReader.java:26)
>  at jsync.protocol.ChangeStreamReader.next(ChangeStreamReader.java:54)
>  at jsync.protocol.ChangeInputStream.next(ChangeInputStream.java:27)
>  at jsync.protocol.ChangeInputStream.read(ChangeInputStream.java:71)
>  at 
> com.cloudbees.jenkins.plugins.jsync.archiver.MD5DigestingInputStream.read(MD5DigestingInputStream.java:39)
>  at com.google.common.io.LimitInputStream.read(LimitInputStream.java:79)
>  at java.io.FilterInputStream.read(FilterInputStream.java:107)
>  at com.google.common.io.ByteStreams.copy(ByteStreams.java:193)
>  at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:35)
>  at 
> com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:158)
>  at 
> com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:76)
>  at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:512)
>  at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:881)
>  at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>  at hudson.model.Run.execute(Run.java:1794)
>  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
>  at hudson.model.ResourceController.execute(ResourceController.java:97)
>  at hudson.model.Executor.run(Executor.java:429){noformat}
> Then, at some point during the *"full archiving"* process, we get the 
> following message:
> {noformat}
> Build timed out (after 120 minutes). Marking the build as aborted.
> {noformat}
> In order to mitigate this timeout error, I've temporarily increased the 
> timeout to 180 minutes. But this should not be necessary: we should try to 
> fix the underlying issue.
> Here's another similar error message from [build 
> #1599|https://builds.apache.org/job/Any23-trunk/1599]:
> {noformat}
> ERROR: Failed to archive {...} due to internal error; falling back to full 
> archiving
> java.lang.IllegalStateException: checksum mismatch after transfer (900817822 
> vs. 1339188126); 
> 

[jira] [Resolved] (ANY23-384) any23.org: 503 Service Unavailable

2018-08-30 Thread Hans Brende (JIRA)


 [ 
https://issues.apache.org/jira/browse/ANY23-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hans Brende resolved ANY23-384.
---
Resolution: Fixed

any23.org appears to be back up now. [~lewismc] Did you change something to get 
it back up? Must have been resolved within the last few days, because it was 
giving me a 503 as of about a week ago.

> any23.org: 503 Service Unavailable
> --
>
> Key: ANY23-384
> URL: https://issues.apache.org/jira/browse/ANY23-384
> Project: Apache Any23
>  Issue Type: Bug
>  Components: site
>Affects Versions: 2.3
>Reporter: Hans Brende
>Priority: Critical
>
> The site any23.org is not working: it returns a 503 Service Unavailable 
> status code after about a minute delay.



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