[Jeff Blumenthal]

Hello,

I am running:
Eclipse 3.0 M3 (note this happens in 2.1.1 too)
MyEclipse plugin
W2K SP3
Weblogic 8.1 SP1 with JCOM native mode enabled
(JCOM is a BEA’s rename of JIntegra which is a 2 way COM bridge)

Scenario:
I need to debug and application I have devloped. When I go to start my WLS 8 server through the start servers tab, it pops up a message box saying: Resource DLL not found [ntvinv\ResourceDll\International\English\ResourceDll.dll] error=[126].

I can open up a cmd window and run the startWebloic.cmd and the server works fine.

Please advise.

Thank you.

[Scott Anderson]

You need to add the directory containing the dll to the Library Path field on the Paths page of the WebLogic preference page (Window > Preferences > MyEclipse > Application Servers > WebLogic 8 > Paths.

–Scott
MyEclipse Support

[Jeff Blumenthal]

I included the path as advised and I still get the same error. I setup a 2003 server and tried this and got the same answer.

From the looks at the stack, it seems there is a problem with myEclipse seeing the registered jvm in the registery.

Regards,
Jeff

<Dec 8, 2003 9:09:28 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2-b28 from Sun Microsystems Inc.>
<Dec 8, 2003 9:09:30 AM CST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<Dec 8, 2003 9:09:30 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009>
<Dec 8, 2003 9:09:30 AM CST> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at D:\bea\user_projects\domains\mydomain\config.xml.>
<Dec 8, 2003 9:09:37 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea\user_projects\domains\mydomain\myserver\myserver.log is opened. All server side log events will be written to this file.>
<Dec 8, 2003 9:09:42 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 8, 2003 9:09:43 AM CST> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server “myserver” for domain “mydomain”>
java.lang.UnsatisfiedLinkError: D:\bea\weblogic81\server\bin\ntvinv.dll: A dynamic link library (DLL) initialization routine failed
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1560)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1485)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at com.linar.jintegra.NativeObjRef.init(NativeObjRef.java:358)
at com.linar.jintegra.Dispatch.isNativeMode(Dispatch.java:133)
at com.linar.jintegra.Dispatch.isNativeMode(Dispatch.java:111)
at com.linar.jintegra.Jvm.init(Jvm.java:131)
at com.linar.jintegra.Jvm.register(Jvm.java:198)
at weblogic.com.COMService.initialize(COMService.java:68)
at weblogic.t3.srvr.SubsystemManager.initialize(SubsystemManager.java:118)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:893)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
***************************************************************************
The WebLogic Server did not start up properly.
java.lang.UnsatisfiedLinkError: registerJvm
at com.linar.jintegra.NativeObjectProxy.registerJvm(Native Method)
at com.linar.jintegra.Jvm.register(Jvm.java:202)
at weblogic.com.COMService.initialize(COMService.java:68)
at weblogic.t3.srvr.SubsystemManager.initialize(SubsystemManager.java:118)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:893)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
Reason: registerJvm

[Scott Anderson]

Jeff,

From the looks at the stack, it seems there is a problem with myEclipse seeing the registered jvm in the registery

I’m not sure what you mean by this. The output looks fine for JDK 1.4.2. Can you explain what you expected to see?

Also, since you’re not running a “stock” WebLogic installation, quite a bit of customization of the MyEclipse launch options may be needed. The easiest way to tell what these are is to compare the external WebLogic launch script that launches the JCOM configured version with the script that launches the basic version. Our connector basically provides everything the standard launch script does, but you’ll need to add any additional settings or jars that are added to the JCOM version’s launch script. For example, we had a long thread here awhile back on how to configure the connector to launch WebLogic Portal. I think this will basically take the same kind of research. Does that make sense? Naturally, we’ll be glad to help as we can. 🙂

–Scott
MyEclipse Support
.

[Author]

Posts