[mmaiaz]

My env is: win2000, jdk1.3.1, eclipse2.1.1 and myeclipse2.5.1

I can not add breakpoint and when I was in breakpoint window, all my context menus were greyed out.

Please help!

Regards,
nm

[support-michael]

Please provide more information to enable us to research this issue. Required information includes: type of MyEclipse project, appserver if one is involved, Eclipse log informaiton, is problem repeatable, …. Don’t be shy about providing this info. The better the info the quicker your problem will be resolved.

Regards,

Michael
MyEclipse Support

[mmaiaz]

I got it work now. Somehow, my jdk corrupted and I reinstalled it.

Thanks and regards,
nm

[mmaiaz]

Now I can setup breakpoints and program did stop, however it did not stop(highlight) at the breakpoint. no error just hang there, can not press f6(unavailable) or f9.

Type of eclipse project: enterprise with EJB and Web modules
app server: weblogic 6.1 sp5

Thanks,
nm

[Scott Anderson]

Are any stopped threads shown in the the Debug Perspective’s Debug View? Are you still running WebLogic with JDK 1.3.1? Would you try installing JDK 1.4.1, configuring WebLogic to use that, and seeing if the problem is resolved?

–Scott
MyEclipse Support

[wschung]

I have a similar problem to the second problem here. Here is my environment:

OS: Linux
AppServer: Weblogic 7.0
Eclipse 2.1
MyEclipse 2.5.1
JDK 1.3.1_08
( I don’t believe weblogic support jdk1.4 until version 8.1 )

When I set a breakpoint and run the code, the execution stops and the break point
is not highlighted. It almost looks like eclipse somehow cannot identify the source
code is associated with the class being run on the server. Note that this problem
happens not just in JSP, but also in other classes, including the class in ejb and
other helper classes. I have tried by exploded and archive deployment. The problem
appears in both cases.

What appears in the Debug view look fishy. Here is a sample of one of the stack
shown. There are a few stacks like this in the Debug view. I cannot jump to
the suspension point from the Debug view. Also, all the “Step in”, etc functions are
disabled. The only two deug menu item not disabled are “Suspend” and “Terminate”

weblogic.Server at localhost:9534 (may be out of synch)
<not responding>
<not responding>
<not responding>
<not responding>
<not responding>
<not responding>

Thanks,
ws

[Scott Anderson]

WS,

The problem is the JDK you’re using is incompatible with the Eclipse debugger. Upgrading to either 1.4.1 or 1.4.2 to launch WebLogic will correct the issue.

( I don’t believe weblogic support jdk1.4 until version 8.1 )

Perhaps “officially” that is true. However WLS 7.0 runs great with JDK 1.4.1+. I use it daily in this configuration.

–Scott
MyEclipse Support

[mmaiaz]

Hi Scott,
I was able to set breakpoint and debug it under WIN2000, jdk1.3.1, Weblogic 6.1(SP5). However, I am having problem under WINNT(corp. desktop OS, can not change), jdk131, WLS 6.1(SP5), eclipse 2.1.1 and myeclipse 2.5.1.
I upgraded jdk to jdk1.4.1_04 and when I started server, I got the following errors:
<Aug 26, 2003 11:59:11 AM MST> <Error> <HTTP> <[WebAppServletContext(11678023,csincentives,/csincentives)] Error loading servlet: ‘CSIMainServlet’
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:306)
at java.lang.Class.newInstance(Class.java:259)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:339)
at javax.rmi.CORBA.Util.<clinit>(Util.java:51)
at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
at com.chase.ccs.web.CSIMainServlet.getDAO(CSIMainServlet.java:248)
at com.chase.ccs.web.CSIMainServlet.initializeStaticApplicationData(CSIMainServlet.java:167)
at com.chase.ccs.web.CSIMainServlet.init(CSIMainServlet.java:46)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:731)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:658)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:603)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2387)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:2328)
at weblogic.servlet.internal.HttpServer.preloadServlets(HttpServer.java:570)
at weblogic.servlet.internal.WebService.preloadServlets(WebService.java:450)
at weblogic.t3.srvr.ServletInitRunner.run(ServletInitRunner.java:49)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.lang.RuntimeException: could not find or instantiate any UtilDelegate class
at weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:74)
… 22 more
>
<Aug 26, 2003 11:59:11 AM MST> <Error> <HTTP> <[WebAppServletContext(11678023,csincentives,/csincentives)] Error loading servlet: “CSIMainServlet”
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:306)
at java.lang.Class.newInstance(Class.java:259)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:339)
at javax.rmi.CORBA.Util.<clinit>(Util.java:51)
at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
at com.chase.ccs.web.CSIMainServlet.getDAO(CSIMainServlet.java:248)
at com.chase.ccs.web.CSIMainServlet.initializeStaticApplicationData(CSIMainServlet.java:167)
at com.chase.ccs.web.CSIMainServlet.init(CSIMainServlet.java:46)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:731)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:658)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:603)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2387)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:2328)
at weblogic.servlet.internal.HttpServer.preloadServlets(HttpServer.java:570)
at weblogic.servlet.internal.WebService.preloadServlets(WebService.java:450)
at weblogic.t3.srvr.ServletInitRunner.run(ServletInitRunner.java:49)
at java.lang.Thread.run(Thread.java:536)
#####################################
Regards,
Michael

[Scott Anderson]

Caused by: java.lang.RuntimeException: could not find or instantiate any UtilDelegate class
at weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:74)

This looks like a server configuration error. Try starting the weblogic domain you’re using from the command line and see if it exhibits the same behavior. Also, you should compare each preference page entry between the two machines and look for differences. I’ guess you’re missing a required library on the classpath.

–Scott
MyEclipse Support

[mmaiaz]

Hi Scott,
I switched back to jdk131 and adding the following Variables to class path and it works now. Thanks for your help!

ORG_ECLIPSE_JDT_SOURCE_SRC
d:/eclipse/plugins/org.eclipse.jdt.source_2.1.1/src

ORG_ECLIPSE_PDE_SOURCE_SRC
d:/eclipse/plugins/org.eclipse.pde.source_2.1.0/src

ORG_ECLIPSE_PLATFORM_SOURCE_SRC
d:/eclipse/plugins/org.eclipse.platform.source_2.1.1/src

ORG_ECLIPSE_PLATFORM_WIN32_SOURCE_SRC
d:/eclipse/plugins/org.eclipse.platform.win32.source_2.1.1/src

Regards,
Michael

[Scott Anderson]

Michael,

Well, it looks like WLS 6 isn’t as happy on JDK 1.4 as I asserted. In fact, I found one of our own documents that stated that 1.4.0 worked, but 1.4.1 was a “no-no” with the stacktrace you posted.

Glad you’re up and running!

–Scott
MyEclipse Support

[Author]

Posts