It depends on how much time per day you can dedicate. I estimate that I put in around 10-15 hours per week, for 3 or 4 weeks.
HFEJB is the only hardcopy reference I used but the sites linked at
JDisucss are quite useful. On the few days leading up to the test, read and re-read
these SCBCD study notes. They were invaluable to me for cramming immediately before the test.
My study strategy was to read the book while at my computer, and take notes, IN YOUR OWN WORDS. Don't copy the book text verbatim because you can do that without thinking. If you have to translate key pieces of text in the book to your own words, it forces your brain to process them, and you will remember them better. Do all the exercises. When you have completed the book, then start doing mock exams on the web. You can find free ones linked at JDiscuss.
When you take the test, READ CAREFULLY. Some of the questions are *very* subtle and require you to know perfectly the differences between stateful/stateless, session/entity/MDB, remote/local, the five roles (bean provider, app assembler, etc) and their responsibilities, etc. Make sure when you are done you revisit every single question and reread it carefully (twice!). I almost missed two questions because I was accustomed to "Bean Provider" being the first choice for role questions and I automatically chose that option without realizing that it actually said "Deployer". If I hadn't reviewed, I would have missed 4 questions instead of 2
The best thing you can do for yourself if practice. Take as many mock exams as you can find because it will give you a very good idea of what you struggle with. For me, it was the subtle differences between the interfaces and the actions each interface allow you to take. USE YOUR SCRATCH PAPER. Immediately before the test, memorize your problem areas and write them down on your scratch paper before you answer a single question. That enables you to relax a little bit and rely less on memory during your question answering. Using this strategy, I didn't miss any questions in my problem areas.
Mike