[Seagate_UK]

I have installed WebLogic 9.1 and have attempted to have myeclispe start it up.

Is this related to: http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=9a61f1bbf8c3bf427044ee3465b:YfiG?bug_id=6355051
It is throwing the following exception:

<13-Nov-2006 11:38:24 o'clock GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: 

There are 1 nested errors:

weblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:118)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:365)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:116)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:67)
Caused by: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
    at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:546)
    at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
    at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)

CONFIGURATION

<<<<
*** Date: Mon Nov 13 11:38:51 GMT 2006

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_09

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 GA
Build id: 20060805-5.0-GA

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 5.0.1 GA
Build id: 20060810-5.0.1-GA

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse Platform

Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060921-0945

Eclipse RCP

Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060921-0945

Eclipse Java Development Tools

Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse Project SDK

Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse\eclipse 3.2\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
bc4_74
-product
com.genuitec.myeclipse.product.ide
-vm
C:\Program Files\Java\jre1.5.0_09\bin\javaw.exe
>>>>

[Scott Anderson]

Martin,

The problem is that you need to use the JVM shipped with WebLogic in order to start it properly. Look under your WebLogic install directory and reconfigure the JDK page of your connector to use that JDK instead of one of Sun’s. That will resolve the issue.

[Seagate_UK]

Thanks Scott,

the server will start when i ref the shipped JDK. However, I have to configure the connector with the admin server details and then apps are deployed to the admin server! Is this correct? What I would like to do is deploy apps to a managed server. Am I also expected to start the node manager outside myeclipse? Could you please advise what the capabilities of the myeclispe connector are?

Thanks in advance
Martin

[Riyad Kalla]

Martin,
I’m not that versed in WL terminology but the design of the MyEclipse connectors is to provide integrated debugging capabilities and control over the app server from your development environment, intended to be configure to run a local development install of the app server. If you need a different setup than this, you will need to handle running the app server yourself but can still have full debugging capabilities using our remote debugging functionality as outlined here:
http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/

[Scott Anderson]

Martin,

Generally, managed servers are more a production concern than a development concern so distributing development applications in this way isn’t generally supported. Here’s the issue. When the connector launches WebLogic, it sets up a real-time debug session with the WLS JVM so you can debug your applications / JSP pages / etc. If you use the connector to launch the Admin server, you’ll be debugging the admin server. But that’s not the server running your applications.

There are two solutions to this. Simplest is to not use a managed server configuration for development and simply launch WebLogic directly from the MyEclipse connector. This will automatically get debugging working easily. The second option is to do what your doing, but then configure a remote debugging session for the actual server instance that will be running your application. Instructions on how to do that are here.

[Seagate_UK]

Thanks Guys,

It all makes sense now. As our developers will be developing applications locally initially I think it’s not worth the bother to setup remote debugging and trying to replicate the distributed server setup. Keeping it simple and using the admin server as the unit test platform would do us fine. We have other test platforms which can be used for integration tests and system tests.

thanks again for the super quick replies!

Martin

[Riyad Kalla]

No problem Martin, glad it helped.

[Author]

Posts