errors in red in application server log

Classic Servoy
1

lately I’m seeing what I think are errors in the servoy admin
server log.

the messages are in red, which leads me to believe that
something isn’t good here, but they just appear to be sql
statments (not mine), so Im not sure what servoy is trying
to tell me.

here’s what I’m seeing:

2006-02-05 11:04 : select db_admin.db_admin_id from db_admin order by db_admin.db_admin_id
2006-02-05 11:04 : select db_admin.db_admin_id from db_admin where db_admin.item_name = ? order by db_admin.db_admin_id

db_admin is indeed one of my tables, and db_admin_id is one of the
fields/columns in this table, but I’m not sure what this means.

any thoughts would be appreciated.
thanks.
rm.

2

If they are red, something went wrong. Try to have a look at the stack trace (popup menu on top of the server page) and you will most likely see an error from the database.

3

interesting…

when I look at the stacktrace(thanks patrick),I see the
following (the first line is in red):

2006-02-06 08:33 : select menu.menuid from menu order by menu.menuid

2006-02-06 08:33 : java.sql.SQLException: Communication link failure: java.net.SocketException
	at org.gjt.mm.mysql.MysqlIO.sendCommand(MysqlIO.java)
	at org.gjt.mm.mysql.MysqlIO.sqlQueryDirect(MysqlIO.java)
	at org.gjt.mm.mysql.MysqlIO.sqlQuery(MysqlIO.java)
	at org.gjt.mm.mysql.Connection.execSQL(Connection.java)
	at org.gjt.mm.mysql.Connection.execSQL(Connection.java)
	at org.gjt.mm.mysql.PreparedStatement.executeQuery(PreparedStatement.java)
	at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.servoy.j2db.persistence.datasource.p.invoke(Unknown Source)
	at $Proxy1.executeQuery(Unknown Source)
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:179)
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:179)
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:179)
	at com.servoy.j2db.dataprocessing.SQLEngine.a(Unknown Source)
	at com.servoy.j2db.dataprocessing.SQLEngine.performQuery(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
	at sun.rmi.transport.Transport$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Unknown Source)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
4

Sounds like the database is gone somehow :?

5

no, db is alive and well.

6

yes, but somehow not reached anymore by the servoy server, no?

7

Looks like the connection to the backend is been closed after a long idle time, it’s a known issue with MySQL.
Does this happen in the morning after the server has been idle all night?
If you use MySQL as backend you should use “validation query” in the DB Server config and use a simple and fast query like “select 1;”.
Hope this helps.
I’m going to publish a MySQL+Servoy miniHowTo soon, if you would like a preview copy just mail me.

8

ngervasi:
Does this happen in the morning after the server has been idle all night?

as a matter of fact, yes! I just checked the error logs, and it
looks as though the problem occurs the first time the user
connects in the morning. I believe you solved my problem,
Nicola!

thank you very much. :P

rm.

9

You’re welcome! :D