Sunday 15 March 2015

problems when installing kaazing websocket gateway -


I use Geoiser 2.1.3 on port 8080 on XP 80.2.2 and Port 8080. 3.5 MSI X64 installer To install it locally on my laptop I followed the official guidelines from the site. MSI has successfully set up Gateway but it installs in C: \ Application Files \ etc not in C: \ Program Filesx68 \. Anyhow, I tried to start services, I have demo-services. Start.Bat ran and a notification came from windows, which was saying that the Windows Firewall has blocked some features of Java. So I hit "Allow" and wait. Command line says something like

  "Send data to more than an hour ucd: // localhost / 50505, ucd: // localhost / 50506 "  

, nothing happened. So I thought that something was wrong with windows and Java. I was uninstalling the cage, allow Java to edit the Windows Firewall settings and reinstall the Kazan again. Notification is not showing anymore, but when I ran demo-services Start.Bat, still nothing, says only one thing when I travel

  http: // localhost / 8000   

Then gives a 404 error I tried everything, to make the ports fickle, uninstall and re-install twice, install on not connected to the Internet, checking the settings of windows fire wall, demo-services To run manually Start.Bet and Gateway Start.bat gateway Start.bat actually runs properly and says that the gateway has started, but when I go to the local host / 8000, there is a 404 error. Installation via MSI is always complete with errors but Gateway does not work Whether it is a wall of fire, Demos is a bat file, I do not get it ...

Suggestions / hints?

The first thing is that Gateway is successfully running first. So do not worry about running demo-services. Start.bat so far

Starting the Windows Service application, start the KAzING webset gateway. Then go to C: \ Program Files \ Kasking, locate your installation and see it in the log directory. Open the error.log using a text editor and verify that there is no error.

If there are no errors, then you should be able to open the http: // localhost: 8001 browser. (Note, you have http: // localhost / 8000 in your example, but this last slash should be a colon.) You can either use port 8000 or 8001, but 8001 Where there are samples,

If you are blocking firewalls or some other ports, you will need to make sure that ports 8000 and 8001 are accessible.

If you are unsure, start a separate server process on Port 8000 or 8001 (such as to configure Epache to listen to port 8000 or 8001) and see if the browser can connect.

MSI has successfully installed Gateway but gets installed in C: \ Application Files \ etc. No in C: \ Program Files \ x68 \ etc.

The gateway is not only executable, but runs in a JVM. Therefore there is no 32 bit code that prevents the application from being installed in C: \ Program Files (x86). Thus C: \ Program Files has made the most sense.

You can use 32-bit JVM which will keep in C: \ program files (x86), but the casing files are explained through java, then for C: \ Program Files Gateway Have a proper place.

There is a forum on the Caging Website for the BTW Kazan question.

No comments:

Post a Comment