Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
runtime exceptions 1
- Thread starter TheDash
- Start date
sedj
Programmer
- Aug 6, 2002
- 5,610
NumberFormatException is normally thrown when you try to do something like :
String value = "5.05";
int i = Integer.parseInt(value);
Whether or not these exceptions should be caught is a matter of debate - it depends what you are doing ! However, it would be normal for a program to catch runtime parsing exceptions and take appropriate action.
--------------------------------------------------
Free Database Connection Pooling Software
String value = "5.05";
int i = Integer.parseInt(value);
Whether or not these exceptions should be caught is a matter of debate - it depends what you are doing ! However, it would be normal for a program to catch runtime parsing exceptions and take appropriate action.
--------------------------------------------------
Free Database Connection Pooling Software
-
1
- #3
stefanwagner
Programmer
I'm not aware of a technique, to write all java exceptions to the syslog.
If you start from commandline, exceptions will be written to stderr, aka the console, as long as you don't redirect them.
If a script starts the program, it may redirect the errormessages to the syslog.
If the exception isn't caught, you would find a stacktrace in the syslog - if you only find single messages, they were caught, I guess.
Of course the softwaredeveloper might have used a logging-mechanism to log errors, and might have specified syslog.log in the code. But again, I would expect a StackTrace for uncaught exceptions.
You could try to find out which program threw the exception to find out more - I would expect it's name in the logfile or search for date/time ...
seeking a job as java-programmer in Berlin:
If you start from commandline, exceptions will be written to stderr, aka the console, as long as you don't redirect them.
If a script starts the program, it may redirect the errormessages to the syslog.
If the exception isn't caught, you would find a stacktrace in the syslog - if you only find single messages, they were caught, I guess.
Of course the softwaredeveloper might have used a logging-mechanism to log errors, and might have specified syslog.log in the code. But again, I would expect a StackTrace for uncaught exceptions.
You could try to find out which program threw the exception to find out more - I would expect it's name in the logfile or search for date/time ...
seeking a job as java-programmer in Berlin:
stefanwagner
Programmer
What do you have to write to syslog?
Which system?
seeking a job as java-programmer in Berlin:
Which system?
seeking a job as java-programmer in Berlin:
- Status
Similar threads