First, I would make sure you have the latest IBM java filesets installed (i.e. up to date in terms of JVM).
Next, I would check to make sure that you are using the appropriate xerces and xalan classes (your VM might be bundled with older versions which have trouble parsing jboss' xml config files).
You can do so by moving xercesImpl.jar, xml-apis.jar and xalan.jar bundled with jboss into <java-home>/lib/endorsed
For more info on endorsed standard libraries and overriding, see http://java.sun.com/j2se/1.4.2/docs/guide/standards/
Hope that helps!
Thanks for the info.
I have just tried this and again the same error message.
I have noted that JBOSS lists the JVM and JAVA version which on the iSeries is :-
18:10:42,774 INFO [ServerInfo] Java version: 1.4.1,IBM Corporation
18:10:42,784 INFO [ServerInfo] Java VM: Classic VM 1.4,IBM Corporation
18:10:42,790 INFO [ServerInfo] OS-System: OS/400 V5R2M0,PowerPC
Looking at your link it is pointing to a site which is explaining Java version 1.4.2. Also on my Windows XP box it is using :-
Java version 1.4.2_06
and JBOSS has ran first time on XP. I also have a SUSE box which I will try later to see what happens.
Do you think I am using the wrong version of Java?
To determine the full version of your JVM, type $JAVA_HOME/bin/java -version from the command line.
Based on that, you can go to IBM to determine if they have patches/updates available for you.
Also, you might want to post more of the server.log output because "09:32:14,484 ERROR [MainDeployer] Could not initialise deployment: file:/jboss-4.0.0/server/default/conf/jboss-service.xml" doesn't give much info to go on.
I think you should try to install tha latest cumulative PTF package for java.
and check that all PTF are installed (already see that some java PTF do not install automatically).
We run JBoss 4.0.0 on our iSeries, so no need to step back to the older version. Just a couple of tips:
- Make sure you specify the correct JAVA_HOME in jboss-4.0.0/bin/run.conf (ours is /QIBM/ProdData/Java400/jdk14)
- Make sure you give the VM enough memory in run.conf (at least 512 MB)
- If you use the run.sh script to start JBoss, it should setup the java.endorsed.dirs system property to point to the jboss-4.0.0/lib/endorsed directory, which contains compatible versions of the XML processor.
- Once you get it going from the command line, you can follow the instructions in http://www.iseriesnetwork.com/nwn/story.cfm?ID=17070 to setup things like a subsystem and job queue to run it in. Though the article is older and uses JDK 1.3 and JBoss 3.0, the OS/400 concepts are identical.
Oh, and I second fbiaggi's advice: Make sure your system is all up-to-date on PTF's (Java & others).