I’m running Mac OS X 10.3.9 Server for the server and client (and Mac OS X client for the client). I’m running a solution that works fine in Servoy Developer. I’m running Application Server, and I can access Server admin pages. I can download servoy_client.jnlp, but it aborts with the following:
An error occurred while launching/running the application.
Thanks. Removing three plugins and changing to the standard TCP/IP ports (I was using non-standard RMI and HTTP ports) now has the client working with Servoy Developer running. I can also access the admin pages on Application Server, but I haven’t yet gotten standalone Application Server to support the client
Did you make sure developer was stopped before you started server? The server bit of developer is the same server bit as server so in theory they should behave exactly the same; if however you launched server before quitting developer it might pick up the previous version of your properties file as developer writes that to disk upon existing.
Application server fails to start correctly and won’t support client:
Welcome to Darwin!
server2:~ user1$ cd /Applications/Servoy
server2:/Applications/Servoy user1$ ./servoy_server.sh &
[1] 504
server2:/Applications/Servoy user1$ Loading servoy.properties from /Applications/Servoy/servoy.properties
Loading - Done
Exception in thread “main” org.apache.commons.dbcp.DbcpException: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:85)
at com.servoy.j2db.persistence.datasource.n.createConnection(Unknown Source)
at com.servoy.j2db.persistence.datasource.r.makeObject(Unknown Source)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
at com.servoy.j2db.persistence.datasource.i.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.checkIfTableExistsInDatabase(Unknown Source)
at com.servoy.j2db.persistence.Repository.int(Unknown Source)
at com.servoy.j2db.persistence.Repository.(Unknown Source)
at com.servoy.j2db.persistence.Repository.(Unknown Source)
at com.servoy.j2db.persistence.Server.getRepository(Unknown Source)
at com.servoy.j2db.server.ApplicationServer.main(Unknown Source)
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:487)
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:723)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3071)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:394)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:83)
… 12 more
server2:/Applications/Servoy user1$
The application server doesn’t start up the database server automatically. Makes sense since Servoy doesn’t know ‘up front’ what database you want to use…
OK, starting Developer, then quitting, then starting Application Server seems to have worked - I can now run the client with Application Server, while Developer is not running.
But it seems very strange to have to start Developer as part of the initialization process on a deployment server. Is there no way to fully initialize the Application Server without Developer?
Servoy itself is not a database, for ease of use we ship with sybase ASA but this doesn’t mean that at deployment time it has to or will be used. Additionally in many cases the database server is ran on a different server than the application server. Our server documentation describes how to make sybase ASA launch at startup by installing it as a service.
jaleman:
Servoy itself is not a database, for ease of use we ship with sybase ASA but this doesn’t mean that at deployment time it has to or will be used. Additionally in many cases the database server is ran on a different server than the application server. Our server documentation describes how to make sybase ASA launch at startup by installing it as a service.
That’s completely understandable, but the database (MySQL) was already up and running - that’s not the problem. The exact problem sequence was:
restart server
launch MySQL
launch Servoy Application Server [problems here]
use Servoy web admin interface [works OK]
launch client [doesn’t run]
launch Developer (don’t bother to open solution)
launch client [works fine]
quit Developer
relaunch Application Server
relaunch client [works fine]
The problem isn’t getting MySQL launched; the problem is getting Application Server (and client) running after MySQL is launched.
mit:
The problem isn’t getting MySQL launched; the problem is getting Application Server (and client) running after MySQL is launched.
Are you sure your Repository is in MySQL and not in Sybase?
If MySQL is up and running and all the DBs you need, Repository INCLUDED, are available you only need to launch Servoy Server by using it’s script (servoy_server.sh).
Are you sure your Repository is in MySQL and not in Sybase?
If MySQL is up and running and all the DBs you need, Repository INCLUDED, are available you only need to launch Servoy Server by using it’s script (servoy_server.sh).