Unable to connect Klaros - Klaros Test Management - Forum - Klaros Test Management
Unable to connect Klaros
Julien Erny, modified 11 Years ago.
Unable to connect Klaros
Youngling Post: 1 Join Date: 6/13/13 Recent Posts
Hi,
I've done a fresh install of Klaros (first install to test it) but I'm unable to connect to it.
I get an error 404 from Tomcat.
I'm on windows, used the last installer (3.7.9).
I have Jave SDK 7U21 installed and both JRE_HOME and JAVA_HOME are set.
I joined the log files (catalina and localhost)
Thanks for your help
I've done a fresh install of Klaros (first install to test it) but I'm unable to connect to it.
I get an error 404 from Tomcat.
I'm on windows, used the last installer (3.7.9).
I have Jave SDK 7U21 installed and both JRE_HOME and JAVA_HOME are set.
I joined the log files (catalina and localhost)
Thanks for your help
Attachments:
Torsten Stolpmann, modified 11 Years ago.
RE: Unable to connect Klaros
Jedi Council Member Posts: 764 Join Date: 2/12/09 Recent Posts
Hello Julien,
are you located behind a Firewall which is inhibiting outgoing connections to port 80?
Upon startup Klaros is retrieving the last released version number from the internet, and from the stacktrace it seems that you are able to connect but you are retrieving empty/malformed content from this URL (http://www.klaros-testmanagement.com/files/version.properties).
It may help to add HTTP proxy settings to the environment settings if this applies to your situation.
We need to make this method more robust in 3.7.10 to cover this case as well.
Hope this helps,
Torsten
are you located behind a Firewall which is inhibiting outgoing connections to port 80?
Upon startup Klaros is retrieving the last released version number from the internet, and from the stacktrace it seems that you are able to connect but you are retrieving empty/malformed content from this URL (http://www.klaros-testmanagement.com/files/version.properties).
It may help to add HTTP proxy settings to the environment settings if this applies to your situation.
We need to make this method more robust in 3.7.10 to cover this case as well.
Hope this helps,
Torsten