Trouble-shooting Centos installation of Server 7.0.0 SOLVED
Posted: Sat Apr 06, 2013 11:45 pm
Summary
I am investigating a move from a central HQ Windows server to a VM on Centos on the web. A test setup using Servoy Server 6.1.3 worked fine, but 7.0.0 has problems for us. This post describes progress and invites suggestions for further trouble-shooting.
Scenario:
Servoy Application Server hosted on a Centos virtual server in cloud. Servoy 6.1.3 runs OK, with 2waysocket selected. Clients connect easily. The server has a separate postgreSQL service. Nice and stable. This is a test regime to check out cloud services prior to migration from a Windows server in an HQ office.
The server has Java VM as follows:
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.version=1.7.0_09
java.vm.info=mixed mode
java.vm.vendor=Oracle Corporation
On a Windows VM in Parallels we install Developer 7.0.1 to make a few improvements to our main solution. The solution works fine in Developer and Smart Client.
Next step is to check out the App Server on our local area network. We install 7.0.0 on a spare OS X box. We create a new repository on that machine, and upgrade it according to the Servoy wiki. With solution imported, the Application Server checks out fine. It is set with Network Settings 2waysocket, SocketFactory.compress:ticked, SocketFactory.useSSL:ticked, SocketFactory.tunnelUseSSLForHttp:NOT ticked. We checkout two solutions: one is the upgraded main solution; the other is a simple one form solution called 'names' which connects to a single table and enables simple queries to be fired at the database. 'names' has no variables, no javascript. It simply displays a first name and last name for all of the rows. Both solutions check out OK on our Servoy App Server 7.0.0 test box.
Next step is to uninstall Servoy 6.1.3 from the Centos VM; and to install 7.0.0 application server in its place. We configure servoy.properties as before, but following the Servoy configuration web page rather than starting with our old servoy properties file. We start with a new repository, and upgrade it. We then add database servers, our users and our two test solutions. Our network settings are set as above.
On downloading a new client from the Centos VM port 8080, we are offered the two solutions. On login to either of the solutions, we see a momentary 'You are disconnected etc' - the error message disappears too quickly to see the whole of it. Neither solution loads a form, though the client window remains with a grey background. The Application Server clients page shows the client as connected under solution <none>, and a message can be sent from the server page to the client, where it is presented immediately. The server log reads: ClientExportNotifyListner[3] ERROR com.servoy.j2db.util.Debug Signalling channel lost when reading pings or client export notifies, removing ports: [3001].
Changing the network settings to http&socket does not change the observed behaviour of logging in, but the comms error is different. It changes to: Date/Time multiplexer-reader-Socket[addr=[obscured]localport=1099] ERROR com.sebster.tunnel.impl.od multiplexer failed for client [uuid type identifier].
With this second set of network settings, a check of webclient shows that 'names' can be loaded, and our main solution gets challenged for login, but then shows 'Internal Error'. We see in the server log: java.lang.IllegalStateException: invalid command: 22
at com.sebster.tunnel.impl.lc.run(lc.java:60)
at java.lang.Thread.run(Thread.java:722)
Diagnosis
The observed communications error appears to be associated with the change from v6 to v7 of the application server, but I am not sure.
Any suggestions for further tests? I am working towards a setup which works in smart client.
I am investigating a move from a central HQ Windows server to a VM on Centos on the web. A test setup using Servoy Server 6.1.3 worked fine, but 7.0.0 has problems for us. This post describes progress and invites suggestions for further trouble-shooting.
Scenario:
Servoy Application Server hosted on a Centos virtual server in cloud. Servoy 6.1.3 runs OK, with 2waysocket selected. Clients connect easily. The server has a separate postgreSQL service. Nice and stable. This is a test regime to check out cloud services prior to migration from a Windows server in an HQ office.
The server has Java VM as follows:
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.version=1.7.0_09
java.vm.info=mixed mode
java.vm.vendor=Oracle Corporation
On a Windows VM in Parallels we install Developer 7.0.1 to make a few improvements to our main solution. The solution works fine in Developer and Smart Client.
Next step is to check out the App Server on our local area network. We install 7.0.0 on a spare OS X box. We create a new repository on that machine, and upgrade it according to the Servoy wiki. With solution imported, the Application Server checks out fine. It is set with Network Settings 2waysocket, SocketFactory.compress:ticked, SocketFactory.useSSL:ticked, SocketFactory.tunnelUseSSLForHttp:NOT ticked. We checkout two solutions: one is the upgraded main solution; the other is a simple one form solution called 'names' which connects to a single table and enables simple queries to be fired at the database. 'names' has no variables, no javascript. It simply displays a first name and last name for all of the rows. Both solutions check out OK on our Servoy App Server 7.0.0 test box.
Next step is to uninstall Servoy 6.1.3 from the Centos VM; and to install 7.0.0 application server in its place. We configure servoy.properties as before, but following the Servoy configuration web page rather than starting with our old servoy properties file. We start with a new repository, and upgrade it. We then add database servers, our users and our two test solutions. Our network settings are set as above.
On downloading a new client from the Centos VM port 8080, we are offered the two solutions. On login to either of the solutions, we see a momentary 'You are disconnected etc' - the error message disappears too quickly to see the whole of it. Neither solution loads a form, though the client window remains with a grey background. The Application Server clients page shows the client as connected under solution <none>, and a message can be sent from the server page to the client, where it is presented immediately. The server log reads: ClientExportNotifyListner[3] ERROR com.servoy.j2db.util.Debug Signalling channel lost when reading pings or client export notifies, removing ports: [3001].
Changing the network settings to http&socket does not change the observed behaviour of logging in, but the comms error is different. It changes to: Date/Time multiplexer-reader-Socket[addr=[obscured]localport=1099] ERROR com.sebster.tunnel.impl.od multiplexer failed for client [uuid type identifier].
With this second set of network settings, a check of webclient shows that 'names' can be loaded, and our main solution gets challenged for login, but then shows 'Internal Error'. We see in the server log: java.lang.IllegalStateException: invalid command: 22
at com.sebster.tunnel.impl.lc.run(lc.java:60)
at java.lang.Thread.run(Thread.java:722)
Diagnosis
The observed communications error appears to be associated with the change from v6 to v7 of the application server, but I am not sure.
Any suggestions for further tests? I am working towards a setup which works in smart client.