Improved Logging

Discuss all feature requests you have for a new Servoy versions here. Make sure to be clear about what you want, provide an example and indicate how important the feature is for you

Improved Logging

Postby Yeroc » Tue Dec 02, 2008 11:11 pm


Is there any chance that the logging information produced on the server could be improved?

Here's an example error from our server (v4.1.0 rc1) logs:
Code: Select all
2008-12-02 11:21:54,287 ERROR [TP-Processor12] com.servoy.j2db.util.Debug - TypeError: Cannot set property "visible" of undefined to "false" (graphics_find#20)
2008-12-02 11:21:54,287 ERROR [TP-Processor12] com.servoy.j2db.util.Debug - Throwable
org.mozilla.javascript.EcmaError: TypeError: Cannot set property "visible" of undefined to "false" (graphics_find#20)
        at org.mozilla.javascript.ScriptRuntime.constructError(
        at org.mozilla.javascript.ScriptRuntime.constructError(
        at org.mozilla.javascript.ScriptRuntime.typeError(
        at org.mozilla.javascript.ScriptRuntime.typeError3(
        at org.mozilla.javascript.ScriptRuntime.undefWriteError(
        at org.mozilla.javascript.ScriptRuntime.setObjectProp(
        at org.mozilla.javascript.gen.c10881._c0(Unknown Source)
        at Source)
        at org.mozilla.javascript.optimizer.OptRuntime.callProp0(
        at org.mozilla.javascript.gen.c10883._c0(graphics_find:20)
        at org.mozilla.javascript.ContextFactory.doTopCall(
        at org.mozilla.javascript.ScriptRuntime.doTopCall(
        at com.servoy.j2db.scripting.ScriptEngine.executeFunction(
        at com.servoy.j2db.FormController.Za(
        at com.servoy.j2db.FormController.executeFunction(
        at com.servoy.j2db.Zdb.Za(
        at com.servoy.j2db.server.headlessclient.dataui.WebEventExecutor.fireActionCommand(
        at com.servoy.j2db.server.headlessclient.dataui.WebEventExecutor.onEvent(
        at com.servoy.j2db.server.headlessclient.dataui.Zdc.onEvent(
        at org.apache.wicket.ajax.AjaxEventBehavior.respond(
        at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(
        at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(
        at org.apache.wicket.RequestCycle.processEventsAndRespond(
        at org.apache.wicket.RequestCycle.step(
        at org.apache.wicket.RequestCycle.steps(
        at org.apache.wicket.RequestCycle.request(
        at org.apache.wicket.protocol.http.WicketFilter.doGet(
        at org.apache.wicket.protocol.http.WicketServlet.doGet(
        at javax.servlet.http.HttpServlet.service(
        at javax.servlet.http.HttpServlet.service(
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(
        at org.apache.catalina.core.StandardWrapperValve.invoke(
        at org.apache.catalina.core.StandardContextValve.invoke(
        at org.apache.catalina.core.StandardHostValve.invoke(
        at org.apache.catalina.valves.ErrorReportValve.invoke(
        at org.apache.catalina.valves.AccessLogValve.invoke(
        at org.apache.catalina.core.StandardEngineValve.invoke(
        at org.apache.catalina.connector.CoyoteAdapter.service(
        at org.apache.jk.server.JkCoyoteHandler.invoke(
        at org.apache.jk.common.HandlerRequest.invoke(
        at org.apache.jk.common.ChannelSocket.invoke(
        at org.apache.jk.common.ChannelSocket.processConnection(
        at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(
        at org.apache.tomcat.util.threads.ThreadPool$

This error would be much more helpful if it included the Javascript stack trace (where applicable) since we often need to know what code called the method that triggered the error not just where the error occurred.

Also, the logging does not include the name of the affected Solution. Since we have a number of Solutions running on a single server it makes sense that all errors that are applicable to a single Solution should include the Solution name. It looks like Servoy is using log4j so it would be relatively easy to use the MDC or NDC features to include the Solution name.

Posts: 109
Joined: Tue Aug 12, 2008 1:12 am
Location: Calgary, AB, Canada

Re: Improved Logging

Postby jcompagner » Wed Dec 03, 2008 1:10 pm

please add a feature request for this in our support system
Johan Compagner
User avatar
Posts: 8284
Joined: Tue May 27, 2003 7:26 pm
Location: The Internet

Re: Improved Logging

Postby Yeroc » Wed Dec 03, 2008 6:46 pm

I've created case # 178133 for this.
Posts: 109
Joined: Tue Aug 12, 2008 1:12 am
Location: Calgary, AB, Canada

Return to Discuss Feature Requests

Who is online

Users browsing this forum: No registered users and 10 guests