3 Replies Latest reply on Aug 22, 2002 5:28 AM by juha

    problems with ibm jre and jboss 3.0.1

    nganju


      JBoss 3.0.0 works with IBM jre, but Jboss 3.0.1 doesn't. I get multiple errors at startup saying:

      18:32:01,108 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)


      18:32:02,679 INFO [ServiceConfigurator] Problem configuring service jboss:type=Service,name=SystemProperties
      org.jboss.deployment.DeploymentException: No property editor for attribute: Properties; type=class java.util.Properties
      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)

      What is this "No Property Editor" issue? Is there some class that Sun's JRE has that IBM jre doesn't? If so, can I just put this class in the classpath?

      Thanks,
      Nick

        • 1. Re: problems with ibm jre and jboss 3.0.1
          nganju


          Also, I think it's important that JBoss work with IBM JRE. On linux, IBM JRE is about twice as fast and much more stable than SUN's JRE.

          • 2. Re: problems with ibm jre and jboss 3.0.1
            nganju


            After perusing the source code, I found the problem. There is some incompatibility with the call to PropertyEditorManager.setEditorSearchPath(newPath) in the file org.jboss.util.propertyeditor.PropertyEditors .

            There is an old version of this class which makes calls to PropertyEditorManager.registerEditor(). When I replace the new version in the jboss-common.jar file with this old version, it works with IBM JRE.

            Probably IBM JRE has a bug in the PropertyEditorManager.setEditorSearchPath() call. I would recommend that you try to make your codebase compatible with IBM JRE, because it is substantially faster on linux.

            Thanks,
            Nick

            • 3. Re: problems with ibm jre and jboss 3.0.1

              sourceforge trackers are the correct place to post this type of information