minibison / javamelody

Automatically exported from code.google.com/p/javamelody
1 stars 0 forks source link

Not able to start Desktop version #440

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Test done with Javamelody 1.53 and JIRA 6.2.7, download of monitoring.jnlp
Java version installed is 1.70_67

Error Details are :
Startup File
<jnlp spec="1.0+" codebase="http://localhost:8080/monitoring">
  <information>
    <title>JavaMelody</title>
    <vendor>JavaMelody</vendor>
    <description>Monitoring</description>
    <offline-allowed/>
  </information>
  <security>
    <all-permissions/>
  </security>
  <update check="always" policy="always"/>
  <resources>
    <j2se version="1.7+" max-heap-size="300m"/>
    <jar href="http://localhost:8080/monitoring?part=desktopJar" size="4714296"/>
    <property name="jnlp.javamelody.application" value="_ALKAES001"/>
    <property name="jnlp.javamelody.collectorServer" value="false"/>
    <property name="jnlp.javamelody.url" value="http://localhost:8080/monitoring?format=serialized"/>
    <property name="jnlp.javamelody.range" value="jour"/>
    <property name="jnlp.javamelody.locale" value="fr_FR"/>
    <property name="jnlp.javamelody.http-transform-pattern" value="-\d+|/\d+|chment/.+|onent/.+|abel/.+|/x/.+|est/.+|ifact/.+"/>
    <property name="jnlp.javamelody.quartz-default-listener-disabled" value="true"/>
    <property name="jnlp.javamelody.system-actions-enabled" value="true"/>
    <property name="jnlp.javamelody.rewrap-datasources" value="true"/>
    <property name="jnlp.javamelody.analytics-id" value="UA-1335263-8"/>
    <property name="jnlp.cookies" value="AJS.conglomerate.cookie=|upm.tab=manage; atlassian.xsrf.token=B3O2-MVM7-OKV9-VQZL|2345b81118b4edf735f1b423f84359ef71effbee|lin; __utmt_navlinks=1; __utmt_greenhopper=1; JSESSIONID=8AC4AA893405731388519ADA6807EDF3; __utma=1.19585283.1411425136.1412279016.1412328842.37; __utmb=1.12.10.1412328842; __utmc=1; __utmz=1.1411425136.1.1.utmcsr"/>
  </resources>
  <application-desc main-class="net.bull.javamelody.Main"/>
</jnlp>

Exception
com.sun.deploy.net.FailedDownloadException: Impossible de charger la ressource 
: http://localhost:8080/monitoring?part=desktopJar
    at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Embedded Exception
java.io.IOException: Invalid jar file
    at com.sun.deploy.net.HttpDownloadHelper.download(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.downloadResourceToTempDir(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Thanks by advance.
Vincent

Original issue reported on code.google.com by v.tho...@alkaes.fr on 3 Oct 2014 at 9:47

GoogleCodeExporter commented 9 years ago
I was too fast while trying to optimize the download of the desktop jar file, 
in revision 3762.
Because calling the app server often needs a http session, but javawebstart 
certainly can't give the http session when downloading the desktop jar file.
So it is needed to download the desktop jar file from Internet and not from the 
app server.
It's fixed in trunk (revision 3950) and ready for the next release (1.54).

Original comment by evernat@free.fr on 12 Oct 2014 at 2:35