JBoss AS 4.2.0.CR1 Release Notes

This is the first Candidate Release of jboss-4.2.0. JBoss 4.2 is a stepping stone from JBoss 4.0 to JBoss 5.0. It combines a lot (but not all) of the exciting new features of JBoss 5, but based on the stable 4.x MicroKernel architecture.

For information on the APIs that make up Java EE 1.4, see Java EE v1.4 Documentation. For a comprehensive tutorial on Java EE 1.4, see The Java EE™ 1.4 Tutorial. A jboss-4.2.x getting started guide that is based on contents from the tutorial can be found in JBoss Application Server Documentation Library

Note: The 4.2.x release of the JBoss Application Server provides support for certain JavaEE5 features, such as EJB3, but it is not Java EE5 certified.

Overview

• Highlights
• Known Compatibility Issues
• Known Configuration Issues
• JBoss/Thirdparty Library Updates
• Detailed Release Notes
• Additional Docs and Help
• Licenses
• About JBoss

Highlights

• JDK5 is *required* to run JBossAS 4.2.x. The decision was based on the fact that JDK1.4 is phased out and the reality that a lot of people like Java Annotations support and want to combine EJB3 and JBoss Seam components with JBossAS. JDK6 is not formally supported yet, although you may be able to start the server with it. JDK6 support will come with JBossAS 5.x.
• JBoss EJB3 is now deployed *by default* in JBossAS 4.2.x The fact that we base on JDK5 makes our life easier in this regard, meaning we don't have to maintain jdk5 code retro-weaved for jdk1.4 runtimes, and we can include by default components that require jdk5 to run.
• JBoss Web v2.x is the web container in JBossAS 4.2, an implementation based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server. In the absence of the native libraries in the JBoss classpath, JBoss Web falls back to the standard non-native connector mode. The native libraries need to be downloaded and installed separately.
• JBoss Transactions v4.2 is the default transaction manager for JBossAS 4.2. JBoss Transactions is founded on industry proven technology and 18 year history as a leader in distributed transactions, and is one of the most interoperable implementations available. The JTA version of JBoss Transactions included with the server provides for fully recoverable transactions. For distributed transaction support the JTS version of JBoss Transactions will need to be used. Furthermore, it is always possible to fall back to the legacy JBossTM fast in-memory transaction manager implementation, if necessary.
• JBossWS is the web services stack for JBoss 4.2 providing Java EE compatible web services. It has been upgraded to v1.2.0.GA
• JGroups/JBossCache were upgraded to the latest releases. The server is already configured to support channel multiplexing, when it becomes available.

Minor feature additions.

• Remote access to MBeanInfo of JMX mbeans with non-serializable attributes over the InvokerAdaptorService, JBAS-1955.
• More options for externalizing LoginModule secrets, JBAS-2895.
• New quartz JCA inflow adapter, JBAS-3206.
• Support of transaction timeouts for MDBs, JBAS-3321.
• Extenstions in the BarrierController to allow wider lifecycle control options, JBAS-3469.
• Configurable policies for determining the master node for HASingletons, JBAS-2499.
• Fast datasource failover, when using the highly available datasource resource adapter, JBAS-3851.
• The higly available (HA) version of the local and xa resource adapters (jboss-ha-local-jdbc.rar, jboss-ha-xa-jdbc.rar), are now consider production quality.
• The JBoss javax.management.timer.Timer implementation has been cloned into a difference package for use with a JDK5 runtime, JBAS-3870.
• .EAR files support ./lib directory, JBAS-4037.

Plus more than 50 bug fixes, see the Detailed Release Notes section for the full details.

Compatibility Issues

• A JavaSE 5 runtime is required to run JBossAS 4.2. A full JDK with tools.jar support is no longer needed by jboss, since JBoss Web packages the eclipse JDT compiler for compiling JSP pages and javassist has its own internal compiler. JAVA_HOME can point to a JRE, JBAS-4161.

• According to our product versioning rules, JBossAS 4.2 is a minor upgrade against JBoss AS 4.0. The various JBoss APIs should be stable but backwards compatibility for individual component implementations may not be guaranteed, e.g. interoperating with another JBoss instance that uses an older version of JGroups.

• Tomcat 6 is now bundled as part of JBoss Web. deploy/jbossweb-tomcat55.sar has been replaced by deploy/jboss-web.deployer.
• conf/log4j.xml has been renamed to conf/jboss-log4j.xml, to allow log4j.properties override from scoped deployments, JBAS-1853.
• log4j and commons-logging have both been upgraded. commons-logging is patched in addition, JBAS-2823.
• Better integration with WebSphere MQ 5.x, JBAS-3183.
• The MyFaces JSF implementation has been replaced by the Glassfish JSF 1.2 one, JBAS-3897.
• Hibernate, hibernate-annotations and hibernate-entity-manager have all been upgraded. to v3.2.1.
• The default invoker for EJBs has been changed from the rmi-invoker to the unified-invoker, provided by JBoss Remoting, JBAS-3950.

Configuration Issues

• JBossAS now binds its services to localhost (127.0.0.1) *by default*, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers properly. To bind JBoss services to a particular interface, simply run jboss with the -b option.
• There now distinct properties to configure the various mcast ports, JBAS-4021.
• JBoss EJB3 is now included by default. If you don't need/want EJB3 support, simply remove deploy/ejb3.deployer.
• When using native libraries for JBoss Web store them in JBOSS_HOME/bin/native, which is automatically included in the classpath, JBAS-4162.
• JBoss Transactions is the new default transaction manager in JBoss. It is configured in conf/jboss-service.xml and has additional properties defined in conf/jbossjta-properties.xml. The transaction log is stored by default at server/default/data/tx-object-store.
• If you are on redhat linux, check out the changes in bin/jboss_init_redhat.sh, JBAS-4041.
• The JBossAS distributions now include the installer (.jar), the sources (.tar.gz) and the canonical binary release (.zip). Unzipping the binary distribution (.zip) with a native unzip utility will restore correctly the executable permission in the /bin/*.sh files. However, unzipping using the JDK jar utility ignores the executable bit, so this need to be set manually.

Library Updates

JBoss Library Updates

• hibernate, upgraded to v3.2.1.GA (from v3.2.0.GA)
• hibernate-annotations upgraded to v3.2.1.GA (from v3.2.0.GA)
• hibernate-entitymanager upgraded to v3.2.1.GA (from v3.2.0.GA)
• javassist, upgraded to v3.5.0.CR1 (from v3.3.0.GA)
• jboss-aop, upgraded to v1.5.4.SP2 (from v1.5.2.GA)
• jboss-backport-concurrent v2.1.0.GA removed
• jboss-cache, upgraded to v1.4.1.SP2 (from v1.4.0.SP1)
• jboss-common, upgraded to v1.0.4.GA (from v1.0.0.GA)
• jboss-ts14, introduced at v4.2.3.CR3
• jboss-retro-rt, v1.0.3.GA removed
• jbossws, upgraded to v1.2.0.GA (from v1.0.3.SP1)
• jboss-we4ee, v4.0.4.SP1 removed
• jbossxb, upgraded to v1.0.0.CR9 (from v1.0.0.CR6)
• jboss-remoting, upgraded to v2.0.0.GA (from v1.4.3.GA)
• jboss-vfs, introduced at v1.0.0.Beta
• jboss-web, introduced at v2.0.0.CR1
• jgroups, upgraded to v2.4.1.GA (from v2.2.7.SP1)

Thirdparty Library Updates

• apache-addressing, at v7-19, removed
• apache-digester, upgraded to v1.7 (from v1.6)
• apache-discovery, upgraded to v0.4 (from v0.2)
• apache-fileupload, upgraded to v1.1.1 (from v1.0)
• apache-httpclient, upgraded to v3.0.1 (from v2.0.2)
• apache-log4j, upgraded to v1.2.14 (from v1.2.8)
• apache-logging, upgraded to v1.1.0.jboss (from v1.0.5-jboss)
• apache-myfaces, v1.1.4 removed
• apache-slide, upgrade to v2.1 (from v1.0.16)
• apache-tomcat, upgraded to v5.5.20 removed
• apache-wss4j, v7-19, removed
• gnu-getopt, upgraded to v1.0.12 (from v1.0.10)
• jaxen, upgraded to v1.1 (from v1.1-beta9)
• junit, upgraded to v3.8.2 (from v3.8.1)
• sleepycat at v1.5.2 removed
• stax-api, introduced at v1.0
• sun-jaxb, introduced at v2.0.3
• sun-jsf, introduced at v1.2_03
• sun-jstl, introduced at v1.2
• sun-servlet, upgraded to v2.5 (from v2.4)
• woodstox, introduced at v3.1.1
• wutka-dtdparser at v1.2.1 removed
• xdoclet, upgraded to v1.2.3 (from v1.2b3)
• xml-sax, at v2.0.x removed

Detailed Release Notes

Includes versions: JBossAS-4.2.0.CR1

Feature Request

• [ JBAS-1824 ] JACC: * in web.xml should allow configurable authorization bypass
• [ JBAS-1955 ] XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions
• [ JBAS-2249 ] Cleanup the org.jboss.naming packaging
• [ JBAS-2523 ] Add a multi-thread option to JndiLoginInitialContextFactory.
• [ JBAS-2895 ] Extend SecureIdentityLoginModule to externalize the secret
• [ JBAS-3206 ] Quartz resource adaptor integration
• [ JBAS-3321 ] Support for "method-attributes" including "transaction-timeout" for MDBs
• [ JBAS-3469 ] Enhance the BarrierController with the ability to destroy/re-create the Barrier
• [ JBAS-3675 ] Add LockOwnerName to ThreadDump output from ServerInfo
• [ JBAS-3769 ] JBossMail Adapter needs logging improvements
• [ JBAS-3847 ] Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
• [ JBAS-3851 ] Slow DataSource Failover - JCA Stale Connection Detection
• [ JBAS-3870 ] Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package
• [ JBAS-3966 ] Add a VersionNumber attribute on the jboss.system:type=Server mbean
• [ JBAS-4037 ] Add support for ear lib directory
• [ JBAS-4047 ] PooledInvokerProxy.getPooledConnection() could hold a lock for shorter period of time
• [ JBAS-4127 ] Need an example datasource for MSSQL 2005

Bug

• [ JBAS-1537 ] When Tomcat error handler is invoked, JBossGenericPrincipal is returned instead of custom principal
• [ JBAS-2215 ] Datasource deployments should only depend on a jrmp invoker when use-java-context is true
• [ JBAS-2731 ] JndiLoginInitialContextFactory still extends org.jnp.interfaces.NamingContextFactory
• [ JBAS-3924 ] InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting
• [ JBAS-3198 ] Problems with separated ClassLoaders for EARs and pooled invoker (PooledInvokerHA).
• [ JBAS-3265 ] Problem with empty classname in classloader
• [ JBAS-3268 ] FormAuthenticator has copy/paste error
• [ JBAS-3316 ] outdated log4j.jar causes UndeclaredThrowableException
• [ JBAS-3352 ] Provide better validation of the redelivery parameters on JBossMQ queues and topics
• [ JBAS-3398 ] Non exploded sar containing war cannot undeploy the war file properly
• [ JBAS-3703 ] Update JRMPInvoker to not cast exported object to RemoteStub
• [ JBAS-3721 ] Clustered SSO entries not properly cleaned up if a server crashes
• [ JBAS-3746 ] org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute failure
• [ JBAS-3784 ] derby-jdbc2-service.xml not updated to jboss 4.x
• [ JBAS-3785 ] Syntax Error in derby-jdbc2-service.xml
• [ JBAS-3805 ] Validation problem with jboss-web_4_0.dtd's replication-field-batch-mode element
• [ JBAS-3821 ] Uncatch JMSException in receive() methods in SpyMessageConsumer.java
• [ JBAS-3828 ] spelling mistake in xml tag
• [ JBAS-3833 ] Cannot unregister HAMembershipListener
• [ JBAS-3838 ] ServerInfo does not check response from getThreadInfo for null
• [ JBAS-3840 ] StackTrace appears on stderr when session.processSessionRepl() failed without tx
• [ JBAS-3849 ] Duplicating _$$_javassist_ classes after remote - call - OutOfMemory: PermGen
• [ JBAS-3860 ] XAManagedConnection should implement LocalTransaction to clean up hanging LocalTransaction
• [ JBAS-3861 ] DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem
• [ JBAS-3917 ] The JMS JCA adapter's DLQMaxResent is set by default to 0, causing messages to go straight to DLQ
• [ JBAS-3941 ] JBossCacheService fails in start if context path contains '/'
• [ JBAS-3947 ] JConsole throws exception on connect post JBoss4.0.3SP1
• [ JBAS-3956 ] JACC PolicyContextHandler usage leaks ThreadLocal values
• [ JBAS-3963 ] JBoss AS security test case(CustomSecurityManagerTestCase) failed
• [ JBAS-3964 ] DeployerInterceptorEJB3 depends on jboss.ejb3:service=EJB3Deployer
• [ JBAS-3972 ] incorrect synchronization in JmsServerSessionPool
• [ JBAS-4002 ] JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API
• [ JBAS-4014 ] timer persistence in afterCompletion
• [ JBAS-4033 ] cache partition index calculation
• [ JBAS-4035 ] BatchReplicationClusteredSessionValve masks exceptions
• [ JBAS-4041 ] jboss_init_redhat.sh is incompatible with a clustered config
• [ JBAS-4048 ] ExternalContext needs to expand its proxy interface collection
• [ JBAS-4056 ] Web Console causes an error when navigating to EJB statistics page (MBeanProxyCreationException)
• [ JBAS-4060 ] NPE in StandardSession.endAccess()
• [ JBAS-4067 ] Collection modifications do not trigger FieldBasedClusteredSession version update
• [ JBAS-4072 ] XAManagedConnectionFactory does not allow for 'is" form of XADataSource properties
• [ JBAS-4075 ] JBossCacheManager.findLocalSessions concurrency issue
• [ JBAS-4090 ] Race condition in Connection.close() can deadlock the JBossMQ's ping thread.
• [ JBAS-4097 ] DummyTransactionManager polluting JNDI in testsuite
• [ JBAS-4114 ] LdapExtLoginModule needs to mask BIND_CREDENTIAL in trace logging
• [ JBAS-4116 ] JRMPInvokerHA fails with a NPE when no JRMPInvoker is setup on the server
• [ JBAS-4118 ] A truly trivial issue; a typo...
• [ JBAS-4121 ] Race condition in JCA Pool Filler
• [ JBAS-4124 ] Using getDefaultSession istead of getSession in org/jboss/resource/adapter/mail/inflow/MailFolder.java
• [ JBAS-4158 ] JACC:WebUserDataPermission creation for unchecked policy should consider excluded constraints

Patch

• [ JBAS-3754 ] ExceptionSorter which marks all exceptions as fatal

Task

• [ JBAS-1853 ] Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.
• [ JBAS-2617 ] ej3.deployer contains too many jars
• [ JBAS-2823 ] Upgrade commons-logging to v1.1
• [ JBAS-2865 ] Move org.jboss.naming package from server module to naming module
• [ JBAS-3183 ] Integration with WebSphere MQ 5.x
• [ JBAS-3272 ] update JBossRemoting to version 2.0.0
• [ JBAS-3276 ] Exception Sorter Implementations should be validated against current RDBMS documentation.
• [ JBAS-3626 ] Upgrade jbossws to 1.2.0.GA
• [ JBAS-3776 ] Update SerialVersionUIDUnitTestCase to test against new versions
• [ JBAS-3789 ] Update JBossORG-EULA.txt
• [ JBAS-3842 ] Upgrade jboss aop to 1.5.4.SP2
• [ JBAS-3886 ] Upgrade jboss and thirdparty dependencies for JBoss 4.2.0
• [ JBAS-3899 ] Get all testsuites passing
• [ JBAS-3900 ] Get the 4.0-compatibility tests passing
• [ JBAS-3922 ] JBossEntityResolverMgr Mbean example should be included in jboss-4.x\docs\examples
• [ JBAS-3971 ] Add basic classloader leakage tests
• [ JBAS-3974 ] Remove versioned jars
• [ JBAS-4049 ] Consider removing Subject mixin from FIELD granularity session Pojos
• [ JBAS-4050 ] Restore the org.jboss.web.tomcat.tc5.session FIELD granularity marker interfaces
• [ JBAS-4051 ] Support the org.jboss.cache.aop marker interfaces for FIELD granularity pojos
• [ JBAS-4100 ] Introduce v4_2 dtds/schemas
• [ JBAS-4102 ] Remove jbossretro-rt.jar and jboss-backport-concurrent.jar dependencies
• [ JBAS-4104 ] Remove namespace.jar from the build
• [ JBAS-4119 ] Consoles and invokers need to accept local connections only
• [ JBAS-4147 ] Include derby-plugin.jar in docs/examples/varia
• [ JBAS-4149 ] Update Jacc Authorization to consider deployment level roles
• [ JBAS-4159 ] Create the release notes for 4.2.0.CR1
• [ JBAS-4161 ] run.sh/.bat should not complaint when running with a JRE
• [ JBAS-4162 ] run.bat/.sh should allow loading native libraries from bin/native, if it exists

Sub-task

• [ JBAS-2560 ] Replace the MockHAPartition unit test with one that uses a JGroups GossipRouter
• [ JBAS-3612 ] failing org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
• [ JBAS-3613 ] failing test in org.jboss.test.iiop.test.ParameterPassingStressTestCase
• [ JBAS-3614 ] failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase
• [ JBAS-3615 ] failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase
• [ JBAS-3616 ] failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase
• [ JBAS-3617 ] 3 failing tests in org.jboss.test.util.test.PropertyEditorsUnitTestCase
• [ JBAS-3636 ] Port HASingletonElectionPolicy to Branch_4_2
• [ JBAS-3732 ] Remove classloader.equals optimization
• [ JBAS-3863 ] Need to properly test the PooledInvoker for scoped invocations
• [ JBAS-3887 ] Upgrade Javassist to v3.5.0.CR1
• [ JBAS-3888 ] Upgrade to EJB3 RC10
• [ JBAS-3890 ] Upgrade to Hibernate 3.2.1
• [ JBAS-3891 ] Upgrade to JBoss Cache 1.4.1.SP2
• [ JBAS-3892 ] Replace TxManager with JBoss Transactions 4.2.3.CR3
• [ JBAS-3897 ] Switch to JSF1.2 Glassfish implementation
• [ JBAS-3898 ] Switch to embedded JBossWeb 2.0.0.CR1
• [ JBAS-3920 ] Upgrade to JGroups 2.4.1
• [ JBAS-3939 ] Upgrade jbossxb to 1.0.0.CR9
• [ JBAS-3949 ] Upgrade to log4j 1.2.14
• [ JBAS-3950 ] Change ejb2 invoker to be the unified invoker
• [ JBAS-3955 ] Upgrade commons-httpclient to v3.0.1
• [ JBAS-3987 ] failing org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCase
• [ JBAS-3990 ] failing org.jboss.test.binding.BindingServiceUnitTestCase(binding-manager)
• [ JBAS-3994 ] Upgrade apache digester to v1.7
• [ JBAS-3995 ] org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase
• [ JBAS-3998 ] failing org.jboss.test.classloader.test.ScopingUnitTestCase
• [ JBAS-4008 ] Upgrade jboss-common to 1.0.4.GA
• [ JBAS-4011 ] failing org.jboss.test.tm.test.TxTimeoutUnitTestCase
• [ JBAS-4013 ] Add ability to use multiplexer to ClusterPartition
• [ JBAS-4015 ] failing org.jboss.test.invokers.test.MultiInvokersUnitTestCase
• [ JBAS-4016 ] failing org.jboss.test.jca.test.BaseConnectionManager{Unit|Stress}TestCase
• [ JBAS-4017 ] failing org.jboss.test.jca.test.XAExceptionUnitTestCase
• [ JBAS-4018 ] failing org.jboss.test.jrmp.test.DynLoadingUnitTestCase
• [ JBAS-4019 ] failing org.jboss.test.security.test.SRPUnitTestCase - unlimited crypto support needed
• [ JBAS-4021 ] Distinct system properties for mcast_port in each config file
• [ JBAS-4023 ] failing org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase
• [ JBAS-4024 ] failing org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase
• [ JBAS-4025 ] failing org.jboss.test.web.test.ssl.SSLUnitTestCase
• [ JBAS-4026 ] failing org.jboss.test.web.test.JSFIntegrationUnitTestCase
• [ JBAS-4031 ] failing org.jboss.test.jacc.test.* tests
• [ JBAS-4058 ] Use the JDK 5 version of JBoss Cache
• [ JBAS-4064 ] failing org.jboss.test.jacc.test.*(JACC+SecurityMgr)
• [ JBAS-4066 ] failing org.jboss.test.classloader.test.CircularityUnitTestCase
• [ JBAS-4073 ] failing org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase
• [ JBAS-4074 ] failing org.jboss.test.jbossmq.test.UIL2JBossMQUnitTestCase
• [ JBAS-4076 ] failing org.jboss.test.jca.test.{Contentious|Recycling|Uncontended}*StressTestCase tests
• [ JBAS-4079 ] failing org.jboss.test.tm.test.Simple*LocalStressTestCase
• [ JBAS-4080 ] failing org.jboss.test.security.test.CustomPrincipalPropagationUnitTestCase
• [ JBAS-4081 ] failing org.jboss.test.security.test.CustomSecurityManagerTestCase(custom-secmgr)
• [ JBAS-4082 ] failing org.jboss.test.naming.test.* tests
• [ JBAS-4085 ] failing org.jboss.test.web.test.WebIntegrationUnitTestCase
• [ JBAS-4126 ] failing org.jboss.test.aop.test tests
• [ JBAS-4136 ] Update XDoclet to an official release
• [ JBAS-4137 ] Update apache-discovery to 0.4
• [ JBAS-4139 ] Update Jaxen to an official release
• [ JBAS-4140 ] Remove sleepycat from thirdpart
• [ JBAS-4141 ] Update apache-slide to v2.1
• [ JBAS-4143 ] remove apache-addressing and apache-wss4j

Documentation and Help

• JBoss AS Documentation
• JBoss Wiki
• JBoss JIRA
• JBoss Forums

Licenses

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

About JBoss, a division of RedHat

JBoss, a division of RedHat, is in the business of providing superior technical support to our customers. Our goal is to make Professional Open Source™ the SAFE CHOICE for you. We accomplish this by backing up our open source Java products with technical support services that are delivered by the core developers themselves. We can help you to train your staff and provide you with support at every stage of the application lifecycle - from development and integration through deployment and maintenance. Visit the JBoss Services page for more information.