[Tyson Bunch]

I am currently using myeclipse with eclipse M3 and weblogic 700 with JDK1.4.2_01. When I fire up weblogic from eclipse and hit some break points everything works fine. After I stop the server and start it back up I hit a break point in LibraryManager.class during start up and when trying to loads JSPs. I have removed all break points but it still happens.

[Scott Anderson]

Did you used to have a breakpoint there, but now it’s gone, doesn’t show up in the margin, but the Eclipse debugger still seems to honor it?

If so, I’ve seen this in Eclipse too. To remove it I think I added another breakpoint and then in the ‘Breakpoints’ view I right-clicked and selected ‘Remove All’. Removing it individually didn’t seem to work for some reason. I’ve seen it in Eclipse 2.1.1, so it’s interesting that the problem still persists in 3.0.

–Scott
MyEclipse Support

[Tyson Bunch]

Looks like a unsatisfied link exception. Here is the stack trace. This happens when I start up weblogic. I have added break points and did the remove all but still no fix. I never set a break point in that class. ANy help is appreciated.. Maybe it is a weblogic issue.

Thread [main] (Suspended (exception UnsatisfiedLinkError))
LibraryManager.getMajorVersion() line: not available [native method] [local variables unavailable]
LibraryManager.load() line: 39 [local variables unavailable]
JDKBridge.loadClass(String, String, ClassLoader) line: 75
Util.loadClass(String, String, ClassLoader) line: 235
Util.createDelegateIfSpecified(String, String) line: 339
Util.<clinit>() line: 51
Utils.<clinit>() line: 229
NamingContextImpl(ObjectImpl).<init>() line: 47
NamingContextImpl.<init>() line: 90
NamingContextImpl.<clinit>() line: 54
InitialReferences.initializeInitialReferences() line: 41
OIDManager.initializeServer() line: 266
OIDManager.initialize() line: 241
RMIServerService.initialize(FailedStateCallback) line: 19
ServerLifeCycleList.initialize(FailedStateCallback) line: 54
T3Srvr.initialize1(FailedStateCallback) line: 756
T3Srvr.initialize(FailedStateCallback) line: 589
T3Srvr.run(String[]) line: 277
Server.main(String[]) line: 32

Here is the weblogic log. Breaks on the IIOP stuff.
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
(c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
<Oct 30, 2003 5:20:42 PM MST> <Info> <WebLogicServer> <000215> <Loaded License : C:\bea\license.bea>
<Oct 30, 2003 5:20:42 PM MST> <Info> <RJVM> <000520> <Network Configuration
Cluster Participant: false
Native Socket IO Enabled: false
Java Socket IO Thread Pool %: 33
Java Socket IO Timeout Min: 100 ms
Java Socket IO Timeout Max: 1000 ms
Reverse DNS Allowed: false
Network Channel: Default
Listen Address: not configured
Listen Port: 7001
SSL Listen Port: none
External DNS Name: not configured
Cluster Address: not configured
Protocol(s): T3,HTTP,IIOP
Tunneling Enabled: false
Outgoing Enabled: true
Admin Traffic Only: false
Admin Traffic OK: true
Channel Weight: 50
Accept Backlog: 50
Login Timeout: 5000 ms
Login Timeout SSL: 25000 ms
Message Timeout HTTP: 60000 ms
Message Timeout T3: 60000 ms
Message Timeout IIOP: 60000 ms
Idle Timeout IIOP: 60000 ms
Max Message Size HTTP: 10000000
Max Message Size T3: 10000000
Max Message Size IIOP: 10000000
>
<Oct 30, 2003 5:20:46 PM MST> <Info> <IIOP> <002014> <IIOP subsystem enabled.>

[support-michael]

What OS are you using?

What happens if you continue the suspended thread? I have run into several suspended thread situations with other servers. In those cases I continued execution with no other side effects.

Michael
MyEclipse Support

[Tyson Bunch]

I can continue on just fine. ONly thing that bugs me is it get suspended in that class 3-4 times per page hit and a couple of times during startup. The weird thing is that the very first time I start eclipse then the myeclipse->weblogic plugin this problem doesn’t arise. It only happens when I shut down the server and then restart.

[support-michael]

I empathize with you on the multiple thread suspensions. I have seen this problem during testing and my hypothesis is there is an issue with the JPDA of the version of JVM you are using. We will research this through the Eclipse team and see if they are aware of such issues. In the meantime:

0) can you try a different version of JVM and see if the problem still persists.

1) What OS are you using?

Michael
MyEclipse Support

[Tyson Bunch]

I will try that. I am using 1.4.2_01 on windows XP… Thanks for your help.

[Author]

Posts