Servoy 2.2.6

Classic Servoy
1

We announce the immediate availability of Servoy 2.2.6

Make a backup of your current Servoy installation (directory and database) before installing.

This version will also be available through auto update shortly (via help menu → check for new version)

Changes:
[enh]-calculations faster initialized, to improve performance
[enh]-performance improvement in 2way socket handling
[enh]-less connection closes when client network disconnects happens
[enh]-integer format property in locale preferences/adminpage
[enh]-to work better under Java 6
[fix]-omitted records cleared more consistent
[fix]-apply tablefilter more consistent
[fix]-invalid linked records when having null column keys in relation
[fix]-use transaction when active in databaseManager.refreshRecordsFromDatabase(…)
[fix]-for bean property editing
[fix]-prevent duplicate user/group creation

2

Hi

I have just updated to 2.26 and have noticed that when i select a row in a portal now the background colour will persist even if i move away from this and select another row. This is undesirable as you will quickly lose the identity of which row is currently selected as you will have multiple rows highlighted (and looks a mess).

3

This effect only occurs if the property of the field in the portal is non-editable.

4

This effect is fixed if you set the property of the fields in a portal to transparent.

5

We upgraded from 2.2.5 to 2.2.6 yesterday evening.

Now we have a lot more disconnects, and following errors:

2006-11-22 11:46:25 : Error flushing message buffer to client 5568753c-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.119; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.119:2084 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:46:25 : Error flushing message buffer to client 46e5dbbb-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.111; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.111:2058 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:46:25 : Error flushing message buffer to client 3f72827a-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.112; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.112:2094 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:46:41 : Signalling channel lost when reading pings or client export notifies, removing ports: [2094]
2006-11-22 11:46:55 : Signalling channel lost when reading pings or client export notifies, removing ports: [2096]
2006-11-22 11:46:55 : Exception writing to the signalling channel for a socket request for 192.168.0.135:2096 removing port
2006-11-22 11:46:57 : Error flushing message buffer to client 5568753c-79fc-11db-a43f-a5e5e92a5b40, Connection refused to host: 192.168.0.119; nested exception is: java.net.ConnectException: Connection timed out: connect
2006-11-22 11:54:13 : Signalling channel lost when reading pings or client export notifies, removing ports: [2062]
2006-11-22 11:55:07 : Error flushing message buffer to client 8b4a5219-79fa-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.108; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.108:2093 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:55:07 : Error flushing message buffer to client 5568753c-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.119; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.119:2100 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:55:28 : Signalling channel lost when reading pings or client export notifies, removing ports: [2100]
2006-11-22 11:55:29 : Error flushing message buffer to client 46e5dbbb-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.111; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.111:2098 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 11:55:35 : Signalling channel lost when reading pings or client export notifies, removing ports: [2093]
2006-11-22 11:56:03 : Signalling channel lost when reading pings or client export notifies, removing ports: [2098]
2006-11-22 12:02:28 : Error flushing message buffer to client 46e5dbbb-79fc-11db-a43f-a5e5e92a5b40, no such object in table
2006-11-22 12:03:37 : Error flushing message buffer to client 46e5dbbb-79fc-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.111; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.111:2105 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 12:03:41 : Signalling channel lost when reading pings or client export notifies, removing ports: [2105]
2006-11-22 12:03:52 : Signalling channel lost when reading pings or client export notifies, removing ports: [2099]
2006-11-22 12:04:57 : Signalling channel lost when reading pings or client export notifies, removing ports: [2097]
2006-11-22 12:05:07 : Error flushing message buffer to client 1c45b255-7a0b-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.114; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.114:2097 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 12:05:07 : Error flushing message buffer to client 8f917905-79f7-11db-a43f-a5e5e92a5b40, Exception creating connection to: 192.168.0.115; nested exception is: java.io.InterruptedIOException: The socket pool for a client 192.168.0.115:2103 did not recieve a callback socket from the client within 60000ms, pool still empty
2006-11-22 12:05:10 : Signalling channel lost when reading pings or client export notifies, removing ports: [2103]
2006-11-22 12:05:59 : Signalling channel lost when reading pings or client export notifies, removing ports: [2089]

ApplicationServer.pingDelay = 50

Anyone?

Thanks!
Stef

6

Signalling channel lost when reading pings or client export notifies, removing ports: [2103]

We did optimize several things in the 2way network layer in Servoy 2.2.6, it seems not all firewalls are to happy with this change, we now made the RMI connection (idle) timeout configurable in Servoy 2.2.7

7

Yes, we are seeing these as well, but have put them down to the perrenial problem with MySQL client disconnects that has been previously documented.

However,

Signalling channel lost when reading pings or client export notifies, removing ports: [2096]

…is something new that we are seeing recently, which is coming up on the console and db server log.

We are running repository and data both on MySQL 5.0.27 with the latest 5.0.4 driver.

8

guydoms:
Yes, we are seeing these as well, but have put them down to the perrenial problem with MySQL client disconnects that has been previously documented.

Try to add this two lines to your my.cnf and the disconnects should go away:

wait_timeout = 129600
interactive_timeout = 129600
9

Hi Nicola,

Thanks, we’ll give that a go.

Regards,

10

guydoms:
Yes, we are seeing these as well, but have put them down to the perrenial problem with MySQL client disconnects that has been previously documented.

Did you read this post?

11

The signaling channel disconnects don’t have anything to do with the database connection. it is the connection between client and server not the one between server and database.