no access to the servoy-admin since update to 6.0.5

Classic Servoy
1

I have updated the Servoy Application Server from 6.0.4 to vers. 6.0.5 by servoy_updater.jar.
Because I have selfsigned jars I installed and run the lasted signtester tool (1.1.4, 01/29/2012). But I cannot open the servoy-admin site. The connection fails, but the server is running.
How do I get the server running?

Regards

2

What do the servoy logs say?

3

Good morning Harjo!

Today I have restarted the debian server with Servoy Application Server 6.0.5 and selfsigned jars to see/get logs. The servoy app server is running only once and I always cannot establish a http-connection to the servoy-admin.
This are the latesed entries in the servoy_log.txt:

2012-01-31 09:07:25,255 ERROR [main] com.servoy.j2db.util.Debug - Throwable [ ]
java.rmi.server.ExportException: Port already in use: 1099; nested exception is: 
	java.net.BindException: Address already in use
	at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
	at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
	at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
	at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
	at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
	at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68)
	at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
	at com.servoy.j2db.server.main.ApplicationServer.Za(ApplicationServer.java:664)
	at com.servoy.j2db.server.main.ApplicationServer.main(ApplicationServer.java:211)
Caused by: java.net.BindException: Address already in use
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
	at java.net.ServerSocket.bind(ServerSocket.java:328)
	at java.net.ServerSocket.<init>(ServerSocket.java:194)
	at java.net.ServerSocket.<init>(ServerSocket.java:150)
	at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:84)
	at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:81)
	at com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:58)
	at com.servoy.j2db.rmi.ServerTwoWaySocketFactory.createServerSocket(ServerTwoWaySocketFactory.java:379)
	at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
	at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
	... 9 more

Regards

4

Addition:

The servoy app server 6.0.5 was running and I could connect to the servoy-admin before I run the signtester tool!
But the solution doesn’t open because of a sign error of the jars, of course.

Regards

5

Hi Thomas,

Did you run signtester when Server was running ? You should always stop Server before you run signtester.

6

Hi Robert,

for sure I stopped the server before running the signtester tool, but I will try it again and reply the result.

Regards

7

Are you sure you are not running 2 instances of servoy?
This looks suspicious:

java.rmi.server.ExportException: Port already in use: 1099; nested exception is: 
   java.net.BindException: Address already in use
8

Hi Nicola,

you are right, it seems so. But in the Terminal I list the running services by “ps -ax” and there is only one servoy-server service running:

1554 ?        S      0:00 /bin/sh ./servoy_server.sh
 1558 ?        Sl     0:05 java -Djava.awt.headless=true -Xmx2048m -Xms64m -XX:MaxPermSize=128m -cla
9

Ok, that is what I have done now:

  • shut down the servoy_server
  • run the signtester.jar (vers. 1.1.4) and got this last lines (different as in Servoy 6.0.4 with a previous vers. of the signtester tool):
Unsigning: wicket-extentions.jar
Exception in thread "main" java.lang.SecurityException: SHA-256 digest error for org/apache/wicket/extensions/Initializer.class
	at sun.security.util.ManifestEntryVerifier.verify(ManifestEntryVerifier.java:198)
	at java.util.jar.JarVerifier.processEntry(JarVerifier.java:212)
	at java.util.jar.JarVerifier.update(JarVerifier.java:199)
	at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:449)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
	at java.io.FilterInputStream.read(FilterInputStream.java:90)
	at net.stuff.servoy.utils.JarUnsigner.unsign(JarUnsigner.java:137)
	at com.servoy.jarsigner.SignerTest.dir(SignerTest.java:148)
	at com.servoy.jarsigner.SignerTest.main(SignerTest.java:101)
admin@ip:~/servoy6/application_server$
  • restart of the servermachine (starts automatically servoy_server)
  • only one server instance is running

no connect to the servoy-admin :cry:

10

Hi Thomas,

Can you run the following command to see if it is actually listening to the ports ?

sudo lsof -i | grep -i listen
11

Hi Robert,

this is the output:

java 1552 root 61u IPv6 235965249 TCP *:rmiregistry (LISTEN)

Could it be a problem of IPv6? It’s a hosted Debian server, but I also have the same issue on a Mac OS X 10.6.8 machine.

Regards

12

Hi Thomas,

So there is no process listening on port 8080 (or any other port Servoy was set to) ?
Check what port tomcat is set to in the server.xml (in application_server/server/conf/ dir).
Also the signing error is suspect. Perhaps you should reinstall Servoy server and resign it again.

13

Hi Robert,

thank you for your replys.

On the Debian Server I made complete new install of Servoy App Server 6.0.5, started it and could connect to the servoy-admin… huray!
Now I make the settings and than I will try to open the solution. But I think this will faile because of the plugins. Than I stop the servoy server from the servoy-admin and run the signtester tool.
I will reply what happen.

Regards

14

It works!
The solution is running (no need to run signtester) on the Debian server with servoy 6.0.5 app server.
I will also make a new install on the Mac server and see what’s going on…

Regards