AS 6.0.0.M3 Release Notes

    http://www.jboss.com/images/common/jbosscorp_logo.png

     

    JBoss AS 6.0.0.M3 is the third milestone release of the community driven AS 6 series. Building on the AS 6.0.0.M1 Release Notes and AS 6.0.0.M2 Release Notes milestone release, it includes support for additional key technologies that are part of the EE6 specification. Further capabilities will be added in future milestones. The release is available for download from the download page.

     

    Two major EJB 3.1 features included in this release are:

     

    • EJB3.1 Singleton Beans in AS 6.0.0 M3 - A more advanced "stateless" bean that allows greater control over concurrency semantics.
    • Container managed concurrency - A set of annotations that allow you to control the locking semantics of your bean. As an example you can implement a common read/write locking model by annotating methods as read or write.

     

    Other major additions include:

     

    • HornetQ - A new high performance messaging implementation. This replaces the JBoss Messaging JMS & MDB implementation.
    • Remoting 3 - A high performance remote invocation framework. The next milestone will switch to this as the default invocation framework for remote EJB connectivity.
    • VFS3 User Guide - A new more efficient implementation of our internal file abstraction layer.
    • OOTB JConsole (JSR-160) Support - You can now use jconsole (and other jsr-160 tools) out of the box, without special properties, to manage AS JMX services.
    • JBoss Embedded AS | Quickstart and Runnable Example - The embedded project is now part of the distribution.
    • JBoss OSGi - The JBoss OSGI project is now included as part of a special "osgi" profile.
    • Many bug fixes and small enhancements as listed in the full notes below.

     

    A Note on Release Naming

     

    The shorthand name for this release is 6.0.0.M3; this is what you'll see in many locations primarily meant to be read by humans (e.g. the download pages.) However, the official name for the release is 6.0.0.20100429-M3, a name which follows the JBoss project versioning conventions for projects that issue milestone releases. The inclusion of the date of the release in the release qualifier helps ensure proper release ordering as specified by the OSGi specification. The official name appears in distributions zips, jar manifests, Maven pom files, and in Maven repository URLs.

     

    Resources

     

    Getting Involved

    JBoss projects are all open source, and are developed by hundreds of developers (many like you) around the world.  If you are interested in contributing to an exciting project with cutting edge technology, then take a look at the HowToContribute wiki entry for more details.

     

    Licensing

    JBoss Application Server  is licensed under the LGPL, as explained in the JBoss End User License Agreement. The license texts for JBoss and the thirdparty components it uses may be found in the docs/licenses directory of the distribution.

    Browse Licenses

     

    Full Release Notes

            Bug

    • [JBAS-5332] -         Container artifacts should have symmetric lifecycles
    • [JBAS-7327] -         Connection validation should return valid connections to the pool when an invalid connection is found
    • [JBAS-7400] -         admin console shows incorrect AS Server version
    • [JBAS-7577] -         Commented-out JmxOpsAccessControlFilter in jmx console's web.xml is invalid
    • [JBAS-7594] -         Seam testsuite ears fail to deploy due to parse issues
    • [JBAS-7676] -         ejbClass is null in JBossEnterpriseBeanMetaData
    • [JBAS-7751] -         unexpected redeployment when using JBTools
    • [JBAS-7760] -         Error when defining dependency between an EAR and its related WAR
    • [JBAS-7767] -         IllegalStateException thrown by InvokerServlet
    • [JBAS-7768] -         JAXBRepositoryContentMetadataPersister does not support EmbeddedAS Servers
    • [JBAS-7769] -         NamingProviderURLWriter does not support EmbeddedAS Servers
    • [JBAS-7783] -         Issue with JBoss5DeploymentScope and VFS3
    • [JBAS-7784] -         JTS transaction propagation does not work in case of server-side initiated transaction and default invoker
    • [JBAS-7785] -         JBossManager should follow StandardContext's naming convention for mbean for root context
    • [JBAS-7786] -         DataSourcePersistentManager storeSessionData attempts to continue using a db connection after an exception
    • [JBAS-7787] -         DataSourcePersistentManager does not overwrite creation time when "re-inserting" a record
    • [JBAS-7790] -         Undeployment of an .ear through HDScanner leads to a deploy() call on the deleted deployment
    • [JBAS-7792] -         WeldJndiBinder incompatible with new EE6 namespace code
    • [JBAS-7797] -         EARContentsDeployer creates the wrong name for modules
    • [JBAS-7808] -         Update EJB 2 TimerImpl classes
    • [JBAS-7811] -         Multithreaded access to remote JDBC datasource is broken
    • [JBAS-7812] -         Add method to create unconnected sockets to DomainSocketFactory
    • [JBAS-7815] -         JSR-88 support fails to undeploy
    • [JBAS-7817] -         java.lang.IllegalArgumentException on JBoss 5.0.1
    • [JBAS-7861] -         user-type-mapped types are not working in ejbql aggregate functions
    • [JBAS-7875] -         Auto creation of destinations for MDBs is broken
    • [JBAS-7876] -         NPE in JNDIBasedSecurityManagement causing authentication failure
    • [JBAS-7877] -         HornetQ stalls for a couple of minutes during journal recovery
    • [JBAS-7878] -         Unhelpful exception from HornetQ RAR
    • [JBAS-7891] -         Fix the NPE in EJB3DeploymentDeployer introduced in EJB3.1 singleton implementation which causes testcase failures 
    • [JBAS-7902] -         WS stack context properties not propagated to servlet context
    • [JBAS-7913] -         Exception when adding HornetQ Core queues to hornetq-configuration.xml/hornetq-queues.xml
    • [JBAS-7914] -         invalid configurationUrl in hornetq-jboss-beans.xml
    • [JBAS-7918] -         "HornetQException[errorCode=112 message=Server not started]" occured during AS unit testing
    • [JBAS-7927] -         Fix VFS3 regression in org.jboss.test.webservice.jbws309.JBWS309TestCase
    • [JBAS-7931] -         Distribution ZIP packages $JBOSS_HOME under ${project.build.dir}
    • [JBAS-7934] -         org.jboss.test.xml.MBeanServerUnitTestCase test failure (java.net.URISyntaxException)
    • [JBAS-7939] -         Naming issues with spring + ejb integration
    • [JBAS-7945] -         LookupSucceededFilter is not thread safe
    • [JBAS-7946] -         javax.jms.JMSSecurityException: Unable to validate user: null
    • [JBAS-7949] -         AuthenticationInterceptor is removing the SecurityContext from the thread
    • [JBAS-7951] -         EjbModule warns about bypassing security for unprotected EJBs
    • [JBAS-7956] -         add application client 6 schemas to metadata-deployer-jboss-beans.xml
    • [JBAS-7966] -         Repositories in pom.xml are outdated which prevents zero config builders
    • [JBAS-7973] -         classes in org.jboss.web.tomcat.metadata are missing JAXB propOrder
    • [JBAS-7984] -         DataSource UNKNOWN run state
    • [JBAS-7985] -         Remove WARNING message on Boot

     

            Feature Request

    • [JBAS-1313] -         RepositorySelector should be integrated into JBoss Server
    • [JBAS-6260] -         Configure JGroups sockets via ServiceBindingManager
    • [JBAS-7161] -         update bindingservice.beans/META-INF/bindings-jboss-beans.xml to rewrite redirectPort only conditionally
    • [JBAS-7195] -         On executing readonly query, WrappedConnection.checkTransactionStatus throws exception when transaction is marked for roll back
    • [JBAS-7466] -         Get rid of ServiceBindingManager XSL transform of server.xml
    • [JBAS-7661] -         Integrate JBoss OSGi in AS distribution
    • [JBAS-7706] -         HornetQ Integration
    • [JBAS-7776] -         Sort system properties in boot.log
    • [JBAS-7779] -         Provide a node name mechanism
    • [JBAS-7791] -         Enhance MBean operation JBossManagedConnectionPool.testConnection to use subject
    • [JBAS-7799] -         DeploymentManager fails to specify a context when unable to determine the module type
    • [JBAS-7881] -         JBossWebRealm needs a flag to bypass the JBoss Security Authorization Framework and rely on only RealmBase authorization
    • [JBAS-7933] -         jconsole regression, no longer works
    • [JBAS-7970] -         Support multiple session factories in -hibernate.xml
    • [JBAS-7979] -         Add encryption for the SSLPassword attribute in native JBossWeb connectors

     

            Release

    • [JBAS-7756] -         Create 6.0.0-Alpha9 release for jboss-integration project

     

            Task

    • [JBAS-2073] -         Remove xalan.jar and serializer.jar from ./lib/endorsed
    • [JBAS-5464] -         Distribute unified-http-invoker.sar package for accessing JNDI, EJB2s and EJB3s over Unified HTTP invoker
    • [JBAS-6108] -         Testcase for CLIENT-CERT for web application
    • [JBAS-6157] -         Track component updates
    • [JBAS-6620] -         JON/Open Console Issues
    • [JBAS-7219] -         Port the TS crash recovery tests from JBPAPP_5_0 to trunk
    • [JBAS-7253] -         Don't assume Address object available from Channel is an IpAddress
    • [JBAS-7267] -         Add missing artifacts to the dependency chain
    • [JBAS-7342] -         VFS3 Migration Parent Task
    • [JBAS-7378] -         Upgrade to Weld 1.0.0.CR1 and test
    • [JBAS-7501] -         Track component updates - 6.0.0.M3
    • [JBAS-7574] -         Update the AS build to prevent jboss-ejb-api jar from being added to common/lib
    • [JBAS-7633] -         Allow for configuring default resource adaptor name for the EJB3 MDBs
    • [JBAS-7641] -         Update JBoss Web deployer to use or create a jboss-threads pool rather than using its own threads
    • [JBAS-7644] -         Enforce EE 6 module name requirements within an application
    • [JBAS-7657] -         Basic smoke testing of OSGI functionality
    • [JBAS-7738] -         Remove resolver.jar and xercesImpl.jar from ./lib/endorsed
    • [JBAS-7749] -         Set groupId to org.jboss.jbossas in resteasy-int poms
    • [JBAS-7754] -         Dist Zip file base directory should match name of the zip file
    • [JBAS-7771] -         Bring EmbeddedAS libraries into the AS distribution
    • [JBAS-7781] -         Update ClusteredDeploymentRepository to deal with VFS3
    • [JBAS-7789] -         Allow the default jmx name of EJB(2.x) deployments to be deterministic
    • [JBAS-7800] -         Upgrade wsdl4j to 1.6.2
    • [JBAS-7801] -         Delete asynch tests in aspects module
    • [JBAS-7823] -         Integrate EJBContextBinder
    • [JBAS-7848] -         Remove direct testsuite dependency on JBoss Cache
    • [JBAS-7863] -         Remove EJB3 dependencyManagement config from component-matrix; bring in EJB3 AS6 BOM
    • [JBAS-7892] -         Fix the INFO level logging in HornetQ deployers
    • [JBAS-7894] -         Refactor AS dist/build pom into separate dist and depchain poms
    • [JBAS-7905] -         Fix the WARN messages logged during AS shutdown
    • [JBAS-7911] -         Allow for configuring default resource adaptor name for the EJB2 MDBs
    • [JBAS-7912] -         Slim down jbossws.deployer
    • [JBAS-7915] -         Move HornetQ configs to hornetq-int
    • [JBAS-7916] -         Move the EmbeddedAS testuite into AS proper
    • [JBAS-7919] -         Split the Build from the Distribution
    • [JBAS-7920] -         Rename EJB3 testcases so that they are included in the default AS testsuite runs
    • [JBAS-7929] -         Clean out protocol stack configs used by JBM
    • [JBAS-7932] -         Shutdown RmiRegistry on stop of JMXConnector
    • [JBAS-7936] -         Add java.net.preferIPv4Stack=true to run.conf(.bat)
    • [JBAS-7942] -         Fix org.jboss.test.security.test.HttpsUnitTestCase
    • [JBAS-7948] -         Fix the testsuite build error resulting from changing snowdrop artifact to jboss-spring-deployer
    • [JBAS-7961] -         Update jboss AS build to use new repositories
    • [JBAS-7962] -         Fix the deprecated dependencies in the AS build
    • [JBAS-7972] -         Ensure the ZIP distribution is free of temp work and log files
    • [JBAS-7983] -         Configure Maven settings in AS so that build works without repository configuration.

     

            Thirdparty Change

    • [JBAS-6133] -         Upgrade Quartz to latest release
    • [JBAS-7216] -         upgrade to the latest 2.x.x metadata
    • [JBAS-7766] -         Upgrade to latest org.jboss.bootstrap
    • [JBAS-7777] -         Integrate VFS abstraction project into AS VFS3 branch
    • [JBAS-7778] -         Integrate VFS abstraction project into AS trunk
    • [JBAS-7809] -         Integrate VFS 3.0.0.CR4
    • [JBAS-7814] -         Integrate VFS 3.0.0.CR5
    • [JBAS-7845] -         Upgrade jboss-ejb-api_3.1_spec to 1.0.0.Beta2
    • [JBAS-7854] -         Upgrade to EJB 3.1 1.0.6-alpha-1 / ejb3-core 1.3.0-alpha-1
    • [JBAS-7890] -         Upgrade to 0.1.1 of ejb3 bom
    • [JBAS-7928] -         Upgrade to org.jboss.bootstrap 2.1.0-alpha-5
    • [JBAS-7963] -         Update to ShrinkWrap 1.0.0-alpha-9 and org.jboss.embedded:1.0.0-alpha-3

     

            Component Upgrade

    • [JBAS-7251] -         Upgrade JGroups to a 2.10 release
    • [JBAS-7529] -         Upgrade MyFaces to 1.2.7
    • [JBAS-7558] -         Upgrade JBoss JavaEE APIs to 1.0.0.Beta1
    • [JBAS-7729] -         Update JBossWS to 3.3.0.Beta3
    • [JBAS-7731] -         Upgrade to JBossXACML 2.0.5.CR1
    • [JBAS-7734] -         Upgrade jboss naming
    • [JBAS-7750] -         Update JBoss LogManager to 1.2.0
    • [JBAS-7762] -         Upgrade web
    • [JBAS-7772] -         Upgrade xalan and serializer to 2.7.1.patch01-brew
    • [JBAS-7833] -         Upgrade to JBossWS 3.3.0.CR1.SP2
    • [JBAS-7899] -         Upgrade JBoss LogManager to 1.2.0.CR2
    • [JBAS-7900] -         Update JBoss Log Service Metadata to 1.0.0.CR9
    • [JBAS-7901] -         Upgrade JBoss Threads & Metadata to 2.0.0.CR4
    • [JBAS-7903] -         Upgrade XNIO Metadata to 2.1.0.CR5
    • [JBAS-7904] -         Upgrade JBoss Marshalling to 1.3.0.CR3

     

            Sub-task

    • [JBAS-6451] -         Drop the trunk/bootstrap in favor of the jbossas/projects/bootstrap/
    • [JBAS-6452] -         Need JBBOOT 0.1.0  release
    • [JBAS-6941] -         consistency between XSD, propOrder and XML in the MC
    • [JBAS-7153] -         org.jboss.test.web.test.JSFInjectionUnitTestCase
    • [JBAS-7208] -         component upgrade of jboss.common.core to version 2.2.13.GA (or greater) instead of 2.2.12.GA
    • [JBAS-7330] -         Integrate VFS3
    • [JBAS-7343] -         Update jboss-as-cluster to use VFS3
    • [JBAS-7344] -         Update jboss-as-connector to use VFS3
    • [JBAS-7345] -         Update jboss-as-deployment to use VFS3
    • [JBAS-7346] -         Update jboss-as-ejb3 to use VFS3
    • [JBAS-7347] -         Update jboss-as-hibernate-int to use VFS3
    • [JBAS-7348] -         Update jboss-as-profileservice to use VFS3
    • [JBAS-7349] -         Update jboss-as-security to use VFS3
    • [JBAS-7350] -         Update jboss-as-server to use VFS3
    • [JBAS-7352] -         Update jboss-as-system to use VFS3
    • [JBAS-7354] -         Update jboss-as-tomcat to use VFS3
    • [JBAS-7355] -         Update jboss-as-varia to use VFS3
    • [JBAS-7356] -         Update jboss-as-webservices to use VFS3
    • [JBAS-7357] -         Update AS testsuite to use VFS3
    • [JBAS-7358] -         Update org.jboss.aop:jboss-aop-asintegration-mc to use VFS3
    • [JBAS-7359] -         Update org.jboss.aop:jboss-aop-deployers to use VFS3
    • [JBAS-7360] -         Update org.jboss.cl:jboss-classloading-vfs to use VFS3
    • [JBAS-7361] -         Update jboss-deployers-vfs-spi to use VFS3
    • [JBAS-7362] -         Update jboss-deployers-vfs to use VFS3
    • [JBAS-7363] -         Update jboss-ejb3-core to use VFS3
    • [JBAS-7365] -         Update jboss-profileservice-spi to use VFS3
    • [JBAS-7366] -         Update jboss-jpa-deployers to use VFS3
    • [JBAS-7367] -         Update jboss-metadata to use VFS3
    • [JBAS-7368] -         Update jboss-test to use VFS3 (just a sysproperty)
    • [JBAS-7369] -         Update security policies to use file: URLs
    • [JBAS-7510] -         Remove jmx-remoting implementation (jsr-160)
    • [JBAS-7560] -         Remove FIELD granularity web session replication
    • [JBAS-7613] -         Update mc-ann to use VFS3
    • [JBAS-7616] -         Update weld-int to use VFS3
    • [JBAS-7617] -         Update bootstrap to use VFS3
    • [JBAS-7707] -         Replace admin-console snapshot with released version
    • [JBAS-7712] -         Update jboss-seam-int ot use VFS3
    • [JBAS-7733] -         Fix intermittent failures in org.jboss.test.naming.test.NamingRestartUnitTestCase
    • [JBAS-7741] -         Looki into a more permanent solution to JBAS-7736
    • [JBAS-7742] -         Add permanent fix for JBAS-7735
    • [JBAS-7773] -         Upgrade to jboss-mdr 2.2.0.Alpha2
    • [JBAS-7774] -         Upgrade to jboss-kernel 2.2.0.Alpha8
    • [JBAS-7794] -         Integrate Remoting into AS
    • [JBAS-7795] -         Integrate Remoting Metadata
    • [JBAS-7796] -         Integrate jboss-marshalling
    • [JBAS-7798] -         Naming deployers should get module name from NamedModule attached to DeploymentUnit
    • [JBAS-7802] -         Update Remoting 3 server configs (XNIO) to use ServiceBindingManager
    • [JBAS-7816] -         JNDI binding tests returning null values
    • [JBAS-7825] -         Port Twiddle and Shutdown to JSR-160
    • [JBAS-7827] -         Create a JSR-160 connector server deployment in AS
    • [JBAS-7829] -         Port org.jboss.jmx.adaptor.html.ClusteredConsoleServlet to use the JSR-160 client API
    • [JBAS-7830] -         Remove the "jboss.jmx:type=adaptor,name=Invoker,protocol=http,service=proxyFactory" object from jmx-invoker-service.xml
    • [JBAS-7836] -         Upgrade mod_cluster to 1.1.0.CR1
    • [JBAS-7846] -         Upgrade ha-server-cache-spi
    • [JBAS-7847] -         Upgrade ha-server-cache-jbc
    • [JBAS-7873] -         add bindings-jboss-beans.xml support for new JSR160 jmx connector (rmi registry port and jmx connector)
    • [JBAS-7874] -         Change unit tests to use JMXConnectorFactory (instead of RMIAdaptor) or remove the unit test
    • [JBAS-7887] -         Upgrade JBoss AOP to 2.2.0
    • [JBAS-7896] -         Remove old LoggingMonitor
    • [JBAS-7898] -         Upgrade JBoss Logging to 3.0.0.Beta2
    • [JBAS-7906] -         Upgrade JBoss ClassPool to 1.0.0.Alpha5
    • [JBAS-7959] -         org.jboss.test.spring
    • [JBAS-7971] -         fix ordering in various -jboss-beans.xml