It was not Exception e but something else that broken after an update,
needs to be fixed, it stopped complaining after i did this, obviouslly
incorrect but what the hey got me back up and running.
try {
job.execute(service);
} catch (RuntimeException e) {
log.error("Job " + job.toString() + " execution failed: " +
e.getMessage());
throw new RuntimeException(e);
}
Jalmari Raippalinna wrote:
Catching plain Exception is not a good thing ;)
try {
job.execute(service);
} catch (Exception e) {
log.error("Job " + job.toString() + " execution failed: " +
e.getMessage());
throw new RuntimeException(e);
}
Why catch the exception at all if its type is unknown and its just
forwarded as RuntimeException?
- Jalmari
Michael Klishin kirjoitti:
Please try again now.
On 27/12/06, sfort <[EMAIL PROTECTED]> wrote:
I've got the same problem! Any ideas?
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
