JBoss-2.4.4_Tomcat-4.0.1 Startup Error

[dolkein]

Getting the folowing error starting JBoss on Win2K. Have had ZERO problems running under Linux for months so I'm stumped.

After searching/reading the FAQ, I decided to reset all lib folders with a fresh install of the JDK and JBoss so this should be pristine. I couldn't see rt.jar on the classpath so I added it, with no noticable effect. The crimson.jar file is in the default location in jboss\lib folder.

Thanks in advance for any assistance.


C:\JBoss-2.4.4_Tomcat-4.0.\jboss\bin>run_with_catalina.bat
JBOSS_CLASSPATH=;c:\jdk1.3.1_01/lib/tools.jar;run.jar;C:\jdk1.3.1_01\jre\lib\rt.jar;../lib/crimson.jar
jboss.home = C:\JBoss-2.4.4_Tomcat-4.0.1\jboss
Using JAAS LoginConfig: file:/C:/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/auth.conf
JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
JBoss version: 2.4.4.2001-12-29 02:04:40 PST
Using configuration "catalina"
[INFO,root] Started Log4jService, config=file:/C:/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/log4j.properties
[INFO,Info] Java version: 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] System: Windows 2000 5.0,x86
[INFO,Shutdown] Shutdown hook added
[INFO,Default] Runtime error
[ERROR,Default] javax.xml.parsers.FactoryConfigurationError: org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
[ERROR,Default] at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:80)
[ERROR,Default]
[ERROR,Default] at org.jboss.configuration.ConfigurationService.loadConfiguration(ConfigurationService.java:449)
[ERROR,Default]
[ERROR,Default] at java.lang.reflect.Method.invoke(Native Method)
[ERROR,Default]
[ERROR,Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[ERROR,Default]
[ERROR,Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main.(Main.java:200)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main$1.run(Main.java:110)
[ERROR,Default]
[ERROR,Default] at java.security.AccessController.doPrivileged(Native Method)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main.main(Main.java:106)
[ERROR,Default]
[INFO,Default] JBoss-2.4.4 Started in 0m:2s.453
[INFO,Default] Shutting down

[barinek]

I have the same problem on Windows XP...


JBOSS_CLASSPATH=;run.jar;../lib/crimson.jar
jboss.home = C:\JBoss-2.4.4_Tomcat-4.0.1\jboss
Using JAAS LoginConfig: file:/C:/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/default/aut
h.conf
JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
JBoss version: 2.4.4.2001-12-29 02:04:40 PST
Using configuration "default"
[INFO,root] Started Log4jService, config=file:/C:/JBoss-2.4.4_Tomcat-4.0.1/jboss
/conf/default/log4j.properties
[INFO,Info] Java version: 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] System: Windows 2000 5.1,x86
[INFO,Shutdown] Shutdown hook added
[INFO,Default] Runtime error
[ERROR,Default] javax.xml.parsers.FactoryConfigurationError: org.apache.crimson.
jaxp.DocumentBuilderFactoryImpl
[ERROR,Default] at javax.xml.parsers.DocumentBuilderFactory.newInstance(
DocumentBuilderFactory.java:80)
[ERROR,Default]
[ERROR,Default] at org.jboss.configuration.ConfigurationService.loadConf
iguration(ConfigurationService.java:449)
[ERROR,Default]
[ERROR,Default] at java.lang.reflect.Method.invoke(Native Method)
[ERROR,Default]
[ERROR,Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1628)
[ERROR,Default]
[ERROR,Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1523)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main.(Main.java:200)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main$1.run(Main.java:110)
[ERROR,Default]
[ERROR,Default] at java.security.AccessController.doPrivileged(Native Me
thod)
[ERROR,Default]
[ERROR,Default] at org.jboss.Main.main(Main.java:106)
[ERROR,Default]
[INFO,Default] JBoss-2.4.4 Started in 0m:0s.828

[benny]

I'm also using win2K and got the same error message.

I solved the problem by installing j2sdk1.4.0.