Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-9523

On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for org.jboss.varia.property.SystemPropertiesService


    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: JBossAS-5.1.0.GA
    • Fix Version/s: None
    • Component/s: Other
    • Labels:
    • Environment:

      Any OS - I've only reproduced the issue with JBoss 5.1.0.GA.


      Please see https://community.jboss.org/message/775821

      We are moving from JBoss 4.3.0.EAP to JBoss 5.1.0.GA EAP.

      In JBoss 4.3.0, we deploy an XML mbean with code="org.jboss.varia.property.SystemPropertiesService" to create some system properties:

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE server>

      <mbean code="org.jboss.varia.property.SystemPropertiesService"
      <attribute name="Properties">


      We can then use these properties in web applications' JBoss configuration files such as jboss.xml:

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE jboss PUBLIC
      -//JBoss//DTD JBOSS 4.2//EN


      This was nice, because then we could hot-deploy system properties to the server without having to edit the configuration of the domain.

      However, in JBoss 5.1.0.GA, this seems to have stopped working. The jboss.xml will not evaluate these system properties presumably because they are not deployed in time.

      Some things:

      1) I am aware of this post: https://community.jboss.org/thread/152996 - which correctly says it will work if we specify the mbean for the SystemPropertiesService in jboss-service.xml. But this is NOT an option for us. We need to be able to deploy those system properties dynamically.

      2) Note how I tried to use <depends> to make it so the mbean depended on that Service. But it just seems to ignore it.

      3) If I wait until the server is fully deployed before deploying the ejb jar file, this works. But I have the requirement that the ejb-jar must load on server startup with everything else. So no delayed deploy trick will work here unfortunately.

      Is there some way I can achieve this how we have it working in JBoss 4.3.0?

      I have attached some files to help test this:

      1) test-testSysProp-service.xml - https://community.jboss.org/servlet/JiveServlet/download/775821-71425/test-testSysProp-service.xml

      Defines the system properties. Copy this in your server/PROFILE/deploy directory to deploy it.

      2) TestEJB.jar - https://community.jboss.org/servlet/JiveServlet/download/775821-71426/TestEJB.jar

      An EJB jar that will use system properties from test-testSysProp-service.xml. The EJB will only deploy if those properties are able to be resolved. Otherwise, you will get this error:

      ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=TestEJB.jar,name=ExRemEJB,service=EJB3_IORFactory state=Createorg.omg.CosNaming.NamingContextPackage.InvalidName: IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0

      3) TestEJBProject.zip - https://community.jboss.org/servlet/JiveServlet/download/775821-71427/TestEJBProject.zip

      The eclipse EJB project TestEJB

        Gliffy Diagrams




              • Assignee:
                ndipiazza Nicholas DiPiazza
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: