Exception management

briphi · Post by **briphi** » 13 Feb 2008, 16:15

I'm having some trouble handling exceptions, and am getting quite confused in the process.

I'm trying to handle my own exceptions, and I want to log them to a file. Is there a way to access the stack trace data (which smartfoxserver prints when we don't catch the exception), so that I can log it myself?

Is there a solution that works with exceptions that originate from either javascript or java?

Bascially, I want to create a high level try/catch that will catch all exceptions and log their stack trace.

Post by **Lapo** » 19 Feb 2008, 07:54

No I am sorry, this is not possible.
If you can give us more details about what you are trying to do we could offer more help

Boing · Post by **Boing** » 01 Sep 2009, 13:13

well, isn't this rather problematic?
I just experienced the problem that I saw an exception on the console but did not find it in the log.
Is some information written only to the console?

I don't know if this might cause problems but I am messing around with the SFS loggers a bit in order to integrate it to my Log4J system like this:

Code: Select all

        // remove SFS log handlers
        Handler[] handlers = SmartFoxServer.log.getHandlers();
        if (handlers != null && handlers.length > 0) {
            for (int i = 0; i < handlers.length; i++) {
                SmartFoxServer.log.removeHandler(handlers[i]);
            }
        }
        // redirect SFS logging to Log4J
        SmartFoxServer.log.addHandler(new SFSLog4JLogger());
        SmartFoxServer.log.setUseParentHandlers(false);

Post by **Lapo** » 02 Sep 2009, 13:14

If you run the server as a service everything gets logged.
That's the recommended mode for running the server in a production environment.

I don't know if this might cause problems but I am messing around with the SFS loggers a bit in order to integrate it to my Log4J system like this:

Log4J will replace the java default logging system in the next major update.

Boing · Post by **Boing** » 02 Sep 2009, 18:44

Lapo wrote:If you run the server as a service everything gets logged.
That's the recommended mode for running the server in a production environment.

okay, and when not running as a service? Stacktraces get swallowed?

We currently have our own start script, I think because we had problems with the default one when we started.

Code: Select all

screen -h 5000 -dmS jumpjupiter java -server -Xms1024m -Xmx2048m -enableassertions -cp ${CLASSPATH} [...] it.gotoandplay.smartfoxserver.SmartFoxServer

Are there good reasons to change this?

Post by **Lapo** » 02 Sep 2009, 19:04

Simply use this instead:
./sfs start (or stop, restart, console)

Boing · Post by **Boing** » 02 Sep 2009, 19:15

Since our script does some more stuff it won't be just "simply".
That's why I want to find out if it's worth it - what are the advantages? Or is it the same in the end?

Post by **Lapo** » 03 Sep 2009, 08:38

Exceptions are always logged to log files depending on your logging level config. Stack traces are not.

We do output to console a few stack traces for extra debugging. Those are captured by running the server as we recommend.

Boing · Post by **Boing** » 03 Sep 2009, 09:04

okay, that's at least one good reason.
Simply using your script did not work on the first attempt, but I'll try to get it running on the weekend.
I saw some threads handling the topic. In case I don't get the problems solved I'll post there.
Thanks for your answers, Lapo.