To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.

HTTP response code: 500 from package repository

nigelbrown
edited February 2015 in - Usage

Hi

When package Manager starts a downlaod from repository a server sends a server side error code 500. Not sure if from proxy server or repository server?

I am using a corporate proxy by specifying it in java commandline (see below).The java is from portable apps as corporate java is 1.6., javajcl shows 'use browser settings' for network but other connection settings doesn't change error.

F:\PortableApps\CommonFiles\Java\bin\java -ea -Xmx1G  -Dhttp.proxyHost=xxx -Dhttp.proxyPort=80 -Dhttp.proxyUser=xxx -Dhttp.proxyPassword=xxx -Djava.net.preferIPv4Stack=true -classpath ProM641.jar org.processmining.contexts.uitopia.packagemanager.PMFrame

Adding -Dhttp.agent="Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0" didn't change error

The respoitory sends file information and option to install is shown, the problem is with initiating download when install is selected for RunnerUpPackages. I suspect it is still a proxy issue but as error code is server side thought I'd ask if this has been encountered/solved before. If it is not thought to be a server issue I will work further on proxy connection. URL works in browsers Firefox and IExplorer on same system.

Hope you can advise.

Nigel

Error text from "External Packages Required" frame:

Started package manager session
Downloading: StochasticPetriNets-6.4.104
I/O Exception: java.io.IOException: Server returned HTTP response code: 500 for URL: http://www.promtools.org/prom6/packages641/StochasticPetriNets/StochasticPetriNets-6.4.104-all.zip
An error has occurred. Please select OK to continue.

Answers

  • Dear Nigel,

     

    If this error is not temporary (e.g. it also occurs after a couple of minutes still) then it is most likely indeed a problem with the proxy. There are currently no know server issues with the package server.

     

    I hope you manage to fix this issue!

    Joos Buijs

    Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
    Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Sign In or Register to comment.