Version 24

    Frequently Asked Questions about the JBoss4 Release



      • J2EE1.4 Certified Application Server.


    1. What happened to JBoss.Net Module?


    • has been replaced with the j2ee 1.4 compliant web services implementation supplied by the jboss-ws4ee.sar and can be found at:  




    2. What are the new J2EE1.4 features?



    3. Classloading with JBoss 4.0.0


    • In the default configuration, the


      is configured to isolate deployments. Use the standard configuration in


      (started with

      ./ -c standard

      ) to get something closer to 3.2.x

    • JBoss 4.0.1 changed these settings back to the behaviour known from 3.2.x.


    4. There are more services using the database, how do I reconfigure JBoss

    to use a database?



    5. Is there a changelog for the changes between JBoss 3.2 and 4?


    • The changelogs are on the SourceForge-Site in the "Docs" section. Look for the "4.0.x Change Notes" subsection there. Some examples for the 3.2 to 4.0.0 transition are linked from here:



    6. Changes to RAR deployment



    7. Files in META-INF are not deployed


    • If you put a deployment in META-INF, e.g. a META-INF/some-service.xml in an ejb jar file it is not deployed in JBoss4. This did work in jboss-3.2.x, but it was not the intended behaviour. META-INF is reserved for information about the current deployment. If you want to make a subdeployment (for those archives that support simple Russian Doll packaging), place it in the root of the parent deployment.

    • To add a -service.xml or other non j2ee deployment to an EAR, you need to reference it from the META-INF/jboss-app.xml in a <service> element.

    • WARs do not support subdeployments


    8. Interrupting threads at transaction time out.


    • By default JBoss-3.2.x interrupts the thread associated with the transaction at transaction timeout. JBoss-4.0.x does not do this. You can re-enable the 3.2.x behaviour in conf/jboss-service.xml

          | The fast in-memory transaction manager.
       <mbean code=""
          <attribute name="TransactionTimeout">300</attribute>
          <attribute name="InterruptThreads">true</attribute> <!-- HERE -->
          <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>