Community
Participate
Working Groups
Created attachment 263650 [details] Eclipse Neon always throws us this dialogue box for this issue. Stack trace "first" is the original, "Second" is what we are currently having. We have updated our FusionDebug product to install and work on Eclipse Neon (for Java Developers). We tested working and (purposefully)faulty connections on eclipse JUNO, LUNA, MARS & NEON. Everything worked fine on all versions, except the faulty connections on NEON. When we make a faulty configuration in our plugin, Eclipse NEON throws an un-handled "nullpointer" exception. However, we have tried to resolve this issue by making changes in our code but without any positive result. We have released our FusionDebug version now after extensive customer demands, but we have had to warn them about this issue in eclipse NEON. Below I have attached a zip that contains two stack traces and a screenshot of the issue in the UI. The "First" stack trace is the one we got when we first discovered the issue while the "Second" stack trace is the one we have after modification to code on our side. We always get the same dialogue error whenever we mis-configure the debug port that the application server is listening to. Thank you in advance. Mike - FusionReactor engineer
If I understand correctly, everything in com.integral.fusiondebug is *your* code, right? In Error-stacktrace-first.png (why a png? ascii text is so much easier to share) I see an NPE in fusiondebug code. To me this looks like a bug in fusiondebug. How could this possibly be a bug in JDT? Please explain. What is your expectation: who should handle the faulty connection and how? What connection is that anyway?
Created attachment 263694 [details] Eclipse Mars dialogue Hello, In the second stack trace, by "fix" I mean we added code to catch our null pointer exception, and instead deliberately throw the ConnectException. Despite this the Eclipse dialogue still displays a null pointer exception. In previous version of eclipse this would show a ConnectException with the stack trace being the dialogue content. So this issue seems specific to eclipse Neon. Here is a dialogue box from mars showing the ConnectException - this is what we were expecting to happen in Eclipse Neon. Looking forward to your responce Mike
Hi Mike, could you respond to Stephan's question about the connection you are talking about? What is the connection and what does it connect and with what?
Hi all It is jdwp style debug connection to a ColdFusion based application server (ColdFusion/Lucee/Railo). The plugin is for live debugging java or cf code on application servers. It connects eclipse to whichever class the user wants to debug if it exists. Looking forward to your response, Mike
I would like to believe this is not an Eclipse problem, or at the very least not a JDT issue. Copying Sarika from debug in case she has some idea about this.
Looks like even if you have fixed by catching the NPE and throwing ConnectException, NPE is still reaching Eclipse Debug component. You can put a breakpoint on Line 885 in org.eclipse.debug.internal.core.LaunchConfiguration to see which exception is coming back to Eclipse.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
