For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 2 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
Recently our group moved to using JRockit 1.5_02 for our server runtime JVM instead of Suns 1.5_02. When we did, the MyEclipseIDE environment started automatically hitting a breakpoint in a class named com.sun.net.ssl.internal.sss.BaseSSLSocketImpl. Here is the stack trace that comes up in the MyEclipseIDE Debug window: nested under org.jboss.Main — doesn’t appear to be fatal because I can continue and the app seems to run fine. Still…it bugs me and would like to know what is going on.
System Thread [Finalizer] (Suspended (exception NullPointerException))
SSLSocketImpl(BaseSSLSocketImpl).finalize() line: 245
SSLSocketImpl(Object).runFinalizer() line: not available
LangAccessImpl.objectFinalize(Object) line: not available
Thread.run() line: not availableWe do use SSL.
This happens sometimes when we startup the JBOSS server within MyEclipseIDE or sometimes when the application is run (access login screen).
This never happened using Suns JRE for JBOSS’s runtime JVM.
The work around is just to continue the application after the false breakpoint is hit and our application appears to run fine.
Our dev environment is as follows,
MyEclipseIDE 3.8.4 (Eclipse 3.0.2)
App Server is JBOSS 4.0.2
Compile JDK is Sun’s JDK1.4.2_07
Server runtime JDK is JRockit 1.5_02Thanks,
J.D.J.D.
It looks like you have an exception breakpoint set on NullPointerException and the finalizer is throwing one, thus triggering the breakpoint. Remove the exception breakpoint and you should be fine.
@support-scott wrote:
J.D.
It looks like you have an exception breakpoint set on NullPointerException and the finalizer is throwing one, thus triggering the breakpoint. Remove the exception breakpoint and you should be fine.
Sorry, no breakpoints set…this is happening to multiple users here in our office using MyEclipseIDE. The only change they made to their environment was to change their runtime JDK on JBOSS from Sun’s to JRockit 1.5_02. This is when the ghost breakpoints started showing up. I’ve already tried the -clean argument to Eclipse and that didn’t fix the problem. My next workaround attempt is to create a new workspace and import my existing projects to see if it goes away.
