| Problem Integrating Eclipse with WAS 6.0 [message #165813] |
Tue, 04 April 2006 05:16  |
Eclipse User |
|
|
|
Originally posted by: randomcoding.gmail.com
Hi.
I just downloaded a trial version of WebSphere Application Server 6.0 to
try out integrated development with Eclipse.
I'm using Eclipse 3.1.2 with Web Tools Platform (WTP) plugin 1.0 and
trying to connect to WAS 6.0. I can define a new Server Runtime but I
can't start the server from Eclipse. It aborts without any error message
on the Eclipse console, but when I check the Server logs (SystemOut and
SystemErr files), I can see the following exception:
____________________________________________________________ _
[4/3/06 11:57:12:562 GMT+05:30] 0000000a SystemErr R
org.xml.sax.SAXNotRecognizedException: Feature:
http://apache.org/xml/features/nonvalidating/load-external-d td
at
org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReader Impl.java:219)
at
com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadD escriptor(MBeanDescriptorLoader.java:148)
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)
[4/3/06 11:57:12:562 GMT+05:30] 0000000a SystemErr R at
org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReader Impl.java:219)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadD escriptor(MBeanDescriptorLoader.java:148)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.load DescriptorFile(MBeanDescriptorManager.java:319)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.descriptor.MBeanDescriptorManager.getD escriptor(MBeanDescriptorManager.java:133)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:375)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFa ctoryImpl.java:348)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.management.component.AdminImpl.initialize(AdminIm pl.java:350)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nt(ContainerImpl.java:1161)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.component.ContainerImpl.initializeCompone nts(ContainerImpl.java:1015)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImp l.java:245)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer Impl.java:157)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:378)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.runtime.WsServer.main(WsServer.java:50)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
java.lang.reflect.Method.invoke(Method.java:324)
[4/3/06 11:57:12:578 GMT+05:30] 0000000a SystemErr R at
com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
[4/3/06 11:57:12:609 GMT+05:30] 0000000a SystemErr R
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)
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.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: The service is unable to activate MBean: type JVM, collaborator
com.ibm.ws.management.component.JVMMBean@1bcfbeb, configuration ID 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: The service is unable to parse the MBean descriptor file
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
____________________________________________________________ ___________
Probably the problem is that some file called JVM.xml doesn't confirm to
strict syntax. I tried searching the installation directory of WAS, even
looking inside JARs and ZIPs but couldn't find any file called JVM.xml. I
tried reinstalling WAS, also tried on another machine, but got the same
error.
I've no idea how to resolve the issue. I would appreciate any help on this
matter.
Thanks in advance.
-Parag
|
|
|
| Re: Problem Integrating Eclipse with WAS 6.0 [message #165822 is a reply to message #165813] |
Tue, 04 April 2006 05:36  |
| Eclipse User |
|
|
|
Originally posted by: randomcoding.gmail.com
And if it makes any difference, I'd better add that initially the error
was different... When I tried to start WebSphere from Eclipse, it aborted
saying some JAR file in the WebSphere installation directory could not be
found. I discovered that the problem was because the installation
directory had a space character in it (Program Files). When I reinstalled
WAS in another directory that didn't have a space in it, that error was
solved, but since them I am having the startup problems as explained in my
previous post.
-Parag
|
|
|
Powered by
FUDForum. Page generated in 0.02866 seconds
] 
Search
Help
Register
Login
Home
