-
1. Re: JBoss Startup - Log4JService
jaikiran Oct 24, 2007 6:54 AM (in response to matty_r)Which version of JBoss and which version of Java? And if there is any other exception stacktrace then please post that too.
-
2. Re: JBoss Startup - Log4JService
matty_r Oct 24, 2007 7:26 AM (in response to matty_r)It's old versions jboss-3.0.1_tomcat-4.0.4 and Java 1.3.0_03. The other 2 errors in the log file are:-
12:21:55,229 INFO [ServiceConfigurator] Problem configuring service jboss.system:type=Log4jService,service=Logging
org.jboss.deployment.DeploymentException: No property editor for attribute: ConfigurationURL; type=class java.net.URL
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:328)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:187)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:130)
at org.jboss.system.ServiceController.install(ServiceController.java:224)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:209)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:749)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:484)
12:22:03,781 ERROR [Server] start failed
Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
[ObjectName: jboss.system:type=Log4jService,service=Logging
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: No property editor for attribute: ConfigurationURL; type=class java.net.URL]
at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1095)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:484)
Thanks again for the help... -
3. Re: JBoss Startup - Log4JService
jaikiran Oct 24, 2007 7:33 AM (in response to matty_r)It's old versions jboss-3.0.1_tomcat-4.0.4 and Java 1.3.0_03
Any reason why you would want to use these old versions of the software? The latest available version of JBoss is 4.2.1 which can be used with JDK5. -
4. Re: JBoss Startup - Log4JService
matty_r Oct 24, 2007 7:54 AM (in response to matty_r)It just comes down to cost of upgrade / retesting all of the different apps hosted on the server...
-
5. Re: JBoss Startup - Log4JService
jaikiran Oct 24, 2007 8:25 AM (in response to matty_r)"Matty_R" wrote:
It just comes down to cost of upgrade / retesting all of the different apps hosted on the server...
Fair enough.
I dont have that version installed on my test system. The oldest that i have is 3.2.7. I looked at the jboss-service.xml file and it mentions:<!-- Preload all custom editors for VMs that don't use the thread context class loader when searching for PropertyEditors. Uncomment if your JDK 1.3.0 VM fails to find JBoss PropertyEditors. <mbean code="org.jboss.varia.property.PropertyEditorManagerService" name="jboss:type=Service,name=BootstrapEditors"> <attribute name="BootstrapEditors"> java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor java.lang.Class=org.jboss.util.propertyeditor.ClassEditor java.util.Date=org.jboss.util.propertyeditor.DateEditor java.io.File=org.jboss.util.propertyeditor.FileEditor java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor javax.management.ObjectName=org.jboss.mx.util.propertyeditor.ObjectNameEditor java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor [Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor java.net.URL=org.jboss.util.propertyeditor.URLEditor </attribute> </mbean> -->
This part is just above the Log4j initialization mbean. As mentioned (specifically for JDK 1.3) in that note, could you try uncommenting this part and see if it works. -
6. Re: JBoss Startup - Log4JService
matty_r Oct 24, 2007 10:12 AM (in response to matty_r)I've managed to fixed that particular problem... I had a JAVA_HOME environment variable set which when removed enabled JBoss to start without error...
Thanks for the help