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.
By debugging of Liferay Portal, that is tomcat application, eclipse make usual stop at ThreadPoolExecutor$Worker.run() line: 912 although I don’t set a breakpoint at this class. The ThreadPoolExecutor isn’t a class of my application, I think that belongs to tomcat. My Question is: what is wrong here, and why eclipse stopt here?
And is it possible to set such “external breakpoints” in eclipse to ignore?
You can fix this immediately by opening the Markers view and delete the Java Exception Breakpoints.
However, to permanently remove this type of breakpoints, you have to go to the Java Debug options and uncheck the “Suspend excecution on uncaught exceptions” option. Then this type of breakpoints won’t get added again in the future.