[razor_harm]

Hi all,

when I try to start my JBoss server (3.2.3) from myEclipse I get the following error:

11:50:30,973 INFO  [Server] Core system initialized
11:50:30,988 INFO  [MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.3/server/mtb/conf/jboss-service.xml
11:50:31,051 ERROR [MainDeployer] Could not initialise deloyment: file:/C:/jboss-3.2.3/server/mtb/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: Document root element is missing.; - nested throwable: (org.xml.sax.SAXParseException: Document root element is missing.)
    at org.jboss.deployment.SARDeployer.init(SARDeployer.java:151)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:696)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
    at org.jboss.Main.boot(Main.java:150)
    at org.jboss.Main$1.run(Main.java:395)
    at java.lang.Thread.run(Thread.java:534)
Caused by: org.xml.sax.SAXParseException: Document root element is missing.
    at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3339)
    at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3327)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:635)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:333)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:505)
    at org.jboss.deployment.SARDeployer.init(SARDeployer.java:115)
    ... 17 more

This happens only after I’ve adjusted the jboss-service.xml file. The changes that I’ve made in this file are:

     <!--
      <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
      -->
      <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute>

instead of:

<attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
      <!--
      <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute>
      -->

Has anybody had this problem or does anybody know a solution to this problem?

Thnx,

Richard Teeuwen

[Scott Anderson]

Richard,

The Sax exception is because your XML document is no longer well-formed. I think if you look over your edits and diff the two files you’ll find that you left off a closing comment or end tag inadvertantly.

[razor_harm]

if I diff the two files the only difference, except the changes I made, is that the one that works is ASCII and the one that doesn’t is UTF-8. So I changed the modified version to ASCII and the server continues to load until the next XML file and then the same error occurs.

Richard

[Scott Anderson]

It’s definately something to do with your machines XML library configuration. What version of the JDK are you using to start JBoss? Are you positive? Does the behavior change when you start from the command line versus the MyEclipse application connector?

Can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.

[razor_harm]

Hi Scott,

I’m using Eclipse Version: 3.0.0 Build id: 200406251208 on a win XP machine. MyEclipse version 3.8.1 QF20040823 (also tried 3.8.0). My JDK version is 1.4.2_03.

If I start jboss from the command line, everything works fine. If I use MyEclipse to start jboss the error occurs.

Richard

[Scott Anderson]

Richard,

And I assume you’re using the same domain and exactly the same JDK to start in both instances? When you open a command prompt and type java -version do you get 1.4.2_03? And you’re positive it’s JBoss 3.2.3 and not 3.2.5? There’s obviously some difference in the runtime configurations between the commandline and the connector and I’m simply trying to isolate it. The JDK used is the prime candidate since it chan have ‘endorsed’ dirs or something that wreak havoc with the XML processing environment.

[razor_harm]

Scott,

the output of java -version:

C:\Documents and Settings\richard>java -version
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode)

and the last line of the jboss boot:

14:37:17,580 INFO  [Server] JBoss (MX MicroKernel) [3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)] Started in 1m:2s:504ms

And I’m indeed using the same domain and JDK to start both instances.

hope this helps

Richard

[Riyad Kalla]

Richard,
Can you open your jboss-service.xml file with a text editor like TextPad, UltraEditor or equally capable text editor (Notepad doesn’t count) and then copy/paste the contents into a brand new file, do File > Save and overwrite the jboss-service.xml file?

Someone reported *exactly* this same error about a month ago, we trouble shot it for 2 weeks and it turned out to be a newline issue that the JBoss parser was barfing on and thought the file was not well formed… but because the file LOOKED ok when you opened it to examine it, it took us forever to track down the problem.

[razor_harm]

Riyad,

this works fine as long as I save it as ASCII (see earlier in this post Posted: Aug 24, 2004 – 01:10 AM) except that the error now occurs on the following xml file (or ear/war containing xml).

Richard

[Riyad Kalla]

Richard can you navigate to your connector properties for JBoss 3 and change the 2 builder paths from “.crimson.” to “.xerces.” meaning, find the part of the package name that says “crimson” and change it to “xerces” and try and start JBoss? If that doesn’t work add xerces to your class path and try again… this was a required change for JBoss >=3.2.5 so I’m wondering if we should just totally change over to xerces in our connector… (p.s. I’m not able to reproduce this problem locally otherwise I’d do it myself).

[razor_harm]

Riyad,

Thanks, that did the trick for me. I just changed crimson to xerces and jboss starts.
Thanks again and keep up the good work !!!

Richard

[Riyad Kalla]

Richard,
I’m glad it worked, I’ll let the team know so we can update the defaults for the JBoss 3 connector.

[a4dev2]

Note that I had a similar problem and found that changing:

<?xml version="1.0" encoding="UTF-8"?>

to

<?xml version="1.0"?>

solved the issue for me.

Scott

[Riyad Kalla]

ahh another great workaround, thanks Scott!

[Author]

Posts