{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 冷血范 的问题《Remove java exception breakpoints when debugging L》','https://www.manongdao.com/q-1316337.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
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.