It always works when I switch debugging on

[doodab]

if (log.isDebugEnabled()) {
    log.debug("process() called");
    try {
        String text = message.getBody();
        ....

Really?

[Spacecadet]

if (log.isDebugEnabled()) {
    log.debug("process() called");
    try {
        String text = message.getBody();
        ....

Really?

Was the previous developer from Luton?

[VectraMan]

I tried something earlier in IE9, and was horrified to see it suddenly had stopped working. Fired up the script debugger; worked fine.

Fortunately I know this one. I'd left a console.log in my javascript, and in IE9 rather than just ignore it if it's got nowhere to log to, it throws a script exception and kills everything. With the debugger on, console.log has somewhere to go and so the code works.

They have fixed it in IE10 at least.

Ah programming. What a laugh.

[suityou01]

Was the previous developer from Luton?

Fail.

[eek]

JavaScript error management

I think there's a plan b in that.

Oops I meant plan c and its in the footer below

[doodab]

JavaScript error management

I think there's a plan b in that.

Oops I meant plan c and its in the footer below

Awesome. Except I need a Java one

BTW, on your plan C page, if I click "blog" then click "about" it's broken (http://erro.rs/about/) and the "follow us" bit appears to say "follow us f ing" at first glance....

[eek]

Awesome. Except I need a Java one

BTW, on your plan C page, if I click "blog" then click "about" it's broken (http://erro.rs/about/) and the "follow us" bit appears to say "follow us f ing" at first glance....

I know there are a list of issues on the website I need to fix that is one of many ( other stuff is consuming some time at the moment).

We do process stacktraces from java but it requires a bit of configuration. If your 500 error page can provide a stacktrace I can provide the code to collect the data.

[doodab]

I know there are a list of issues on the website I need to fix that is one of many ( other stuff is consuming some time at the moment).

We do process stacktraces from java but it requires a bit of configuration. If your 500 error page can provide a stacktrace I can provide the code to collect the data.

The code doesn't throw an error. The error is that the code that is supposed to run gets skipped unless the logging level is set to debug. So you'd need to do some sort of static analysis.