ConAim wrote:Found out the problem to this issue (since I ran into this also). It's port 8843 that Smartfox was trying to binding into. Event set isActive to false in webSocket block and/or set to another port inside server.xml. It's still binding into port 8843. So either Smartfox's dev. was hard coded the port and/or there are some other setting somewhere else beside server.xml that I was not aware off. In any case Smartfox should have a try-catch to log.error the port number for easier troubleshooting.
The only way to get this to work is turn off the other application that also using this port. (use TclView.exe or Resource Monitor to know the PID).
Thanks, Its working ...