This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
hi, I have three files called first_err.log, first.log, first.out. In all the three files i want to get the exception names like NullPointerException, IndexOutofBounds, etc and count the total number of occurancy for each exceptions and put in a new file called Excepiton.txt. We should use java version 1.4.x only.
Welcome to the JavaRanch, Nagendra. What in particular do you have a question about? If you are unfamiliar with working with files, The Java Tutorial has an introduction to Java IO here. If you want to get fancy, there's a number of string searching algorithms to consider once you've figured out the reading and writing part of your program.
hi i want the code related to my question which i had mentioned earlier. presently i am running batch file to search the exceptions , it takes lot of time. so, please give me some code related to this. thank u
Your code looks great, Joe, but perhaps you didn't notice that he said his files were 2G in size? BufferedReader will output each line of text to a String. The problem with that is that it goes into the String Pool, where it can never be deleted (except by exiting the program). That means 2G of memory will be taken up (minus the occasional line duplicates), just by reading in the files!
I mainly mention this because I'm having the same problem (trying to read-in and parse HUGE text files). A BufferedReader that returned type StringBuilder instead of String would be great, but I don't see it in the API.
Anyone have any more ideas?
Thanks! Scott [ August 02, 2006: Message edited by: Scott Cook ]
Originally posted by Scott Cook: The problem with that is that it goes into the String Pool, where it can never be deleted (except by exiting the program).
welcome to the JavaRanch, Scott If that were true, I don't think any java program would be able to run for any amount of time without running out of memory. Strings which are hardcoded in your program go into a literal pool and are never destroyed. Strings which are created in the course of a program's execution are elegible for garbage collection just like every other object. [ August 02, 2006: Message edited by: Joe Ess ]
Joined: Aug 01, 2006
Strings which are created in the course of a program's execution are elegible for garbage collection
Thanks for clearing that up! I read about String Immutability in the appendix of Head First Java and got really nervous. It sounded like a HUGE memory leak to me!(not literally, but has the same effect)