jcompagner:
that doesnt say to much,
you need to have the log of the client. Because the client closes the connection to the server.
Have left client now, but will be back there on Thursday…
Do you have that same errors on all your clients to that machine? or only on that mac
If a windows machine connects to that server what does it do then?
I think the issue is the same on all Macs that have the company proxy settings enabled on them. On my Mac and another Mac of someone that works there but doesn’t have proxy enabled, it is fine.
All the PCs have the Java/Network Settings/Direct Connection enabled (as when I first set up their Servoy system, we had to do this on all PCs to allow them to work) & so work fine.
Is there some virusscanner or firewall inbetween? Maybe something in the middle just doesnt trust the data and closes it.
Based on my comment above, I would assume it has to be something in the Proxy settings on the Mac & not the firewall on the server (I’m not sure if a virus scanner is running on server). I was sure we had configured it correctly for Servoy, as it does work when Compress is turned off, so what else would we need to add to the exception rules for that server (called ‘testsrv-6’)?
rafig:
Based on my comment above, I would assume it has to be something in the Proxy settings on the Mac & not the firewall on the server (I’m not sure if a virus scanner is running on server). I was sure we had configured it correctly for Servoy, as it does work when Compress is turned off, so what else would we need to add to the exception rules for that server (called ‘testsrv-6’)?
Try to update to the latest Apple Java and then turn on “direct connection” to skip the proxy in the Java preferences.
ngervasi:
Try to update to the latest Apple Java and then turn on “direct connection” to skip the proxy in the Java preferences.
Hi. Thanks for the advice!
My client will give it a try, but they have wait for IT to come round and update their Mac 8-(
Other Mac user’s there are running on 10.4 & I’m not sure if that option will appear if they update.
it compresses the communications between client and server with gzip compression. This can result in 90% less traffic and a few less roundtrips to the server.
Normally there shouldnt be any problem for normal clients, but if for some reason there is a problem you can switch it off. This switching of could be very likely if you use developers with the servoy team repository setup.
Jan Blok:
We are pleased announce the immediate availability of Servoy 3.5.10
[fix] case 209788: DB sequence was not used after switchServer
I would like to have more information on this fix because we are going to use switchServer() to switch between customer dbs in a multicustomer installation.
The original error was about Servoy sequences od DB sequences? I suppose Servoy ones but I prefer to ask…
Sequences were never switched (always used those of the first connection aka they were not maintained for each db…) or they were switched once and never after or they didn’t work at all after a switchServer?
The issue we fixed was that the sequence setting on a column was not always applied to the same column in the switched-to server after calling databasemanager.switchServer().
For example, if you configured a column to use database sequences, after the switchServer() call the column in the target database would sometimes fall back to servoy sequences.