Eclipse Community Forums: ServerTools (WTP) » Can't start WAS6 from Eclipse with WTP

Help

Home

Home » Language IDEs » ServerTools (WTP) » Can't start WAS6 from Eclipse with WTP

Show: Today's Messages :: Show Polls :: Message Navigator

Can't start WAS6 from Eclipse with WTP [message #169164]

Thu, 11 May 2006 17:09

Eclipse User

Originally posted by: jordicahue.es.ibm.com

Hi, I'm trying to start WAS6 server from Eclipse Server view but I get the
exception DescriptorParseException with the XML file
com/ibm/ws/management/descriptor/xml/JVM.xml.
On the other hand, I can start withot any problem my WAS6 server outside
Eclipse.

I would appreciate any help on this matter.

Thanks in advance, and sorry about spanish logs.

Jordi.
------------------------------------------------------------ -

************ Start Display Current Environment ************
WebSphere Platform 6.0 [ND 6.0.0.1 o0445.08] running with process name
ESQ86734Node03Cell\ESQ86734Node03\server1 and process id 560
Host Operating System is Windows XP, version 5.1
Java version = 1.4.1_05, Java Compiler = null, Java VM name = Java
HotSpot(TM) Client VM
was.install.root = C:/IBM/WAS6/AppServer1
user.install.root = C:/IBM/WAS6/AppServer1/profiles/TF7AppSrv
Java Home = C:\Program Files\Java\j2re1.4.1_05
ws.ext.dirs =
C:/IBM/WAS6/AppServer1/java/lib;C:/IBM/WAS6/AppServer1/profi les/TF7AppSrv/classes;C:/IBM/WAS6/AppServer1/classes;C:/IBM/ WAS6/AppServer1/lib;C:/IBM/WAS6/AppServer1/installedChannels ;C:/IBM/WAS6/AppServer1/lib/ext;C:/IBM/WAS6/AppServer1/web/h elp;C:/IBM/WAS6/AppServer1/deploytool/itp/plugins/com.ibm.et ools.ejbdeploy/runtime
Classpath =
C:\IBM\WAS6\AppServer1\properties;C:\IBM\WAS6\AppServer1\lib \bootstrap.jar;C:\IBM\WAS6\AppServer1\lib\j2ee.jar;C:\IBM\WA S6\AppServer1\lib\lmproxy.jar;C:\IBM\WAS6\AppServer1\lib\url protocols.jar
Java Library path =
C:/IBM/WAS6/AppServer1/java/bin;C:/IBM/WAS6/AppServer1/bin;C :/IBM/WAS6/AppServer1/java/bin;C:/IBM/WAS6/AppServer1/java/j re/bin
************* End Display Current Environment *************
[11/05/06 18:48:34:804 CEST] 0000000a ManagerAdmin I TRAS0017I: El
estado de rastreo de arranque es *=info.
[11/05/06 18:48:34:964 CEST] 0000000a MBeanDescript W ADMN0001W: El
servicio no puede analizar el archivo descriptor de MBean
com/ibm/ws/management/descriptor/xml/mbeans.xml.
[11/05/06 18:48:35:065 CEST] 0000000a AdminInitiali A ADMN0015I: El
servicio de administración se ha inicializado.
[11/05/06 18:48:35:105 CEST] 0000000a MBeanDescript W ADMN0001W: El
servicio no puede analizar el archivo descriptor de MBean
com.ibm.websphere.management.exception.DescriptorParseExcept ion:
ADMN0001W: El servicio no puede analizar el archivo descriptor de MBean
com/ibm/ws/management/descriptor/xml/JVM.xml.
at
com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadD escriptor(MBeanDescriptorLoader.java:164)
at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.load DescriptorFile(MBeanDescriptorManager.java:319)
at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.getD escriptor(MBeanDescriptorManager.java:133)
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:375)
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:348)
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminIm pl.java:350)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nt(ContainerImpl.java:1161)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nts(ContainerImpl.java:1015)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImp l.java:245)
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer Impl.java:157)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:378)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
..
[11/05/06 18:48:35:135 CEST] 0000000a WsServerImpl E WSVR0009E: Se ha
producido un error durante el inicio
META-INF/ws-server-components.xml
[11/05/06 18:48:35:175 CEST] 0000000a WsServerImpl E WSVR0009E: Se ha
producido un error durante el inicio
com.ibm.ws.exception.ConfigurationError:
com.ibm.ws.exception.ConfigurationError: Problem initializing AdminImpl:
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer Impl.java:166)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:378)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
Caused by: com.ibm.ws.exception.ConfigurationError: Problem initializing
AdminImpl:
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminIm pl.java:697)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nt(ContainerImpl.java:1161)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nts(ContainerImpl.java:1015)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImp l.java:245)
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer Impl.java:157)
... 8 more
Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem registering
JVM MBean.
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminIm pl.java:361)
... 12 more
Caused by: com.ibm.websphere.management.exception.AdminException:
ADMN0005E: El servicio no puede activar MBean: tipo JVM, colaborador
com.ibm.ws.management.component.JVMMBean@4b29cf, ID de configuración JVM,
descriptor null.
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:600)
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:348)
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminIm pl.java:350)
... 12 more
Caused by:
com.ibm.websphere.management.exception.DescriptorParseExcept ion:
ADMN0001W: El servicio no puede analizar el archivo descriptor de MBean
com/ibm/ws/management/descriptor/xml/JVM.xml.
at
com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadD escriptor(MBeanDescriptorLoader.java:164)
at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.load DescriptorFile(MBeanDescriptorManager.java:319)
at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.getD escriptor(MBeanDescriptorManager.java:133)
at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:375)
... 14 more

Report message to a moderator

Re: Can't start WAS6 from Eclipse with WTP [message #169332 is a reply to message #169164]

Fri, 12 May 2006 21:04

Dario Bassan

Messages: 8
Registered: July 2009

Junior Member

Hi Jordi,
I don't know exactly what happens but looking your log there is
something wrong on WAS JRE Env used to startup.

From your log:

Java version = 1.4.1_05, Java Compiler = null, Java VM name = Java Java
Home = C:\Program Files\Java\j2re1.4.1_05

I think it should be:

Java version = J2RE 1.4.2 IBM Windows 32 build cn142ifx-20051115 (SR3 +
94164 + 97403 + 97482) (JIT enabled: jitc), Java Compiler = jitc, Java
VM name = Classic VM
Java Home = C:\IBM\WAS6\java\jre

Change your WAS configuration creating a new JRE definiton mapping to
"C:\IBM\WAS6\java\jre".

Hope this help.

Ciao
Dario

Report message to a moderator

Previous Topic:	starting tomcat with admin webapp?
Next Topic:	Encoding problems

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 07:16:53 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter