- This topic has 5 replies, 2 voices, and was last updated 17 years, 11 months ago by
.
-
Posts
-
Not sure where to post this since I used MyEclipse to develop the application but now I am trying to deploy to a staging server…
I have an EJB/Struts application that I was able to run via Tomcat in MyEclipse just fine. But when I try to manually create a JBoss install via:
/usr/local/jboss-4.0.2/ and deploy my EAR to /usr/local/jboss-4.0.2/ server/default/deploy I get the following message:
2007-02-21 21:23:35,795 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/usr/local/jboss-4.0.2/server/default/conf/login-config.xml
2007-02-21 21:23:35,855 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML
org.jboss.xml.binding.JBossXBException: Failed to get parser’s XMLReader
at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.setFeature(SaxJBossXBParser.java:112)
at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:71)
at org.jboss.xml.binding.Unmarshaller.<init>(Unmarshaller.java:68)
at org.jboss.xml.binding.Unmarshaller.<init>(Unmarshaller.java:52)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:305)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:273)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:253)
at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:162)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:418)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
at org.jboss.Main.boot(Main.java:195)
at org.jboss.Main$1.run(Main.java:463)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.xml.sax.SAXNotRecognizedException: Feature: http://apache.org/xml/features/validation/schema
at org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:204)
at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.setFeature(SaxJBossXBParser.java:108)
… 55 more
2007-02-21 21:23:35,865 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as Sun format, url=file:/usr/local/jboss-4.0.2/server/default/conf/login-config.xml
2007-02-21 21:23:35,920 WARN [org.jboss.security.auth.login.XMLLoginConfigImpl] End loadConfig, failed to load config: file:/usr/local/jboss-4.0.2/server/default/conf/login-config.xml
org.jboss.security.auth.login.ParseException: Encountered “<?xml” at line 1, column 1.
Was expecting one of:
<EOF>
<IDENTIFIER> …The login-config.xml is valid – or at least I haven’t modified it at all, not sure that I need to?
I am not able to use the MyEclipse deployer because this project was originally written as one big EAR file consisting of several JAR’s and EAR’s. But I didn’t think there would be a huge problem just manually copying the EAR over to the JBoss directory.My guess is either end-of-line character problems, or the file got borked. Notice the error:
org.jboss.security.auth.login.ParseException: Encountered “<?xml” at line 1, column 1.
Was expecting one of:
<EOF>
<IDENTIFIER> …Try opening the file on linux using a linux editor, maybe it’s got a sneaky \n in there someplace that is actually breaking the format of the file for the parser.
I have opened up the login-config.xml file in several editors and it is good. But I am seeing this in the log files, which might also explain by mysql-ds.xml declaration isn’t getting bound and the database connection is not working either.
2007-02-24 09:34:09,856 DEBUG [org.jboss.system.ServiceController] starting service jboss.security:service=XMLLoginConfig 2007-02-24 09:34:09,857 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Starting jboss.security:service=XMLLoginConfig 2007-02-24 09:34:09,857 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/usr/local/jboss-4.0.2/server/default/conf/login-config.xml 2007-02-24 09:34:09,924 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML org.jboss.xml.binding.JBossXBException: Failed to get parser's XMLReader at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.setFeature(SaxJBossXBParser.java:112) at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:71) at org.jboss.xml.binding.Unmarshaller.<init>(Unmarshaller.java:68) at org.jboss.xml.binding.Unmarshaller.<init>(Unmarshaller.java:52) at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:305) at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:273) at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:253) at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:162) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:418) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315) at org.jboss.Main.boot(Main.java:195) at org.jboss.Main$1.run(Main.java:463) at java.lang.Thread.run(Thread.java:595) Caused by: org.xml.sax.SAXNotRecognizedException: Feature: http://apache.org/xml/features/validation/schema at org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:204) at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.setFeature(SaxJBossXBParser.java:108) ... 55 more 2007-02-24 09:34:09,936 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as Sun format, url=file:/usr/local/jboss-4.0.2/server/default/conf/login-config.xmlI’m not sure what is going on here but all the errors are originating from JBoss files… maybe try a new install (just unzip it somewhere and reconfigure your connector?) I’m sorry I don’t have more helpful suggestions right now.
I found the answer was that my startup script was using the crimson-1.1.1.jar which was causing XML parsing issues. Once I modified my scripts to not load any extra files, and just use the default JBoss files, that fixed a great many issues.
Thank you for your help.
