Servoy 7
Solution is designed for web client only.
Runs fine on development PC.
Accessing solution from desktop of remote server works fine, i.e. locally to the server.
Accessing from a client PC across the internet allows log in to solution, but after a few seconds it goes to the default Servoy solution selection page.
Changing the server network settings tunnelConnectionMode to HTTP only seems to stop this, but then downloads don’t work.
Nothing in log files (wrapper or server).
Only one client connecting with a memory ceiling of 3GB, so memory is not an issue.
Port 8080 is open for incoming on Windows firewall on server. 1099 not an issue as smart client not allowed.
In further testing - a simple test solution with one label on one form exhibits the same behaviour - redirects to the solution choice page after 10 or so seconds.
The Servoy admin page, accessed over the internet, works fine and does not time out. Well, probably after 60 mins.
You may want to stick with 6.1.6 unless you are prepared to…
A little story about how we spent a year going from 6.1 betas to finally 6.1.6. Early on each point release fixed some things and broke some things. At about 6.1.3 we started getting private “RC” builds before point releases were shipped. Sometimes there were up to 4-5 RC builds for a point release. Each one of these fixed some things and broke some things.
We maintained two servers to compare new builds against old. We also kept Servoy install snapshots for each RC of each point release. We even set up our test servers so you could easily spin up a different release. We filed bug reports with detailed descriptions and sample solutions. If we caught an issue later down the line, we could (and did) go back and pinpoint which point and RC release the issue popped up in.
Against all this we had a fairly comprehensive testing process. We focused on UI and speed because these seemed to have the most variableness with regards to web client. We went from solution model being mostly unusable, network chatter out the wazzoo, CSS design incomplete, anchoring all over the place, various widgets issues, etc — to 6.1.6 which is a very solid release.
Along the way we figured out web client best practices, what to avoid, and how to seriously hack web client. It wasn’t uncommon for other developers to wait to upgrade until they had seen the results of our testing.
Web client isn’t the focus of 7.x so we’re not moving up. (More likely they will break more than they will fix is our thinking.) Yes I miss not having constructors and yes I drool over the upcoming form folders and yes I’d like to being able to use Git without hard-linking directories…but it sure is nice taking a break from what seemed like non-stop Servoy testing.
Moral of the story: you will get stuck—over and over—and not just simple-stuck. You either need your own comprehensive testing process or you need to piggy-back off someone else’s. And looking around, I don’t think anyone (including Servoy) has this thorough of a process in place for testing 7.x builds (RCs are public now) from a web client perspective. Or at least they are not being vocal about it like we were.
So in my opinion, waiting for 7.x to mature would be a good choice if web client is your focus. 6.1.6 is just one of those rare “really solid” Servoy releases.
I was also beginning to come round to the conclusion that I should revert to 6.x myself … what confuses me though is why everything would work in 7.x on developer, and on the customer server when running a browser there and accessing via localhost or whatever, but not across the internet …
Since it all works fine via localhost I am beginning to suspect something is causing Tomcat sessions to timeout, but I have no idea how I would go about establishing that.
Since it all works fine via localhost I am beginning to suspect something is causing Tomcat sessions to timeout, but I have no idea how I would go about establishing that.
Progress…you’ve ruled out Servoy version. And I would say it’s a low chance the issue is in your code since no log errors are thrown and it works on localhost.
Next up is eliminating issues with the server. So…Servoy settings, various machine specific settings, database connections, database setup and performance, memory utilization, disk performance, etc etc.
If that all clears then you have to look at the network. Speed, ping, firewalls, routers, wireless routers, proxies…
After 10 years of setting up Servoy servers and hosting, we’ve run into issues with just about everything (and more) in the above list at one time or another. Yesterday alone for example one team member was rebuilding a 14 disk raid 10 array for main data center and another was getting a random Servoy-based ISV on-premise install up and running again in some part of the world. Thankfully not every day is like this!
So if you don’t want to deal with this stuff there are people around on this forum who might be able to help…