Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Recently jrebel has started reloading all of the classes in our project when we make a jersey request as well as when we shut down. It doesn’t seem to be every request but if you wait a while between requests it is almost guaranteed to happen.
It just loops over every class in the project and reloads it – I had to bump the permgen because it was blowing past that.
Any ideas on what to check that may have changed that would cause this to happen all of the sudden?
It turns out the problem was a maven issue in the way we were installing a jar that was not part of a repo. It was getting a strange dependency that was causing a circular reference which meant that when any class changed it refreshed all of them thus causing jrebel to reload everything.