[News & Announcements] - JBossAS 4.2.3.GA released
by rrajesh
JBoss Application Server 4.2.3.GA has been released and is available for download from jboss.org
http://www.jboss.org/jbossas/downloads/
JBoss AS 4.2.3.GA Release Notes
This is the 3rd bug fixing release of the JBoss Application Server v4.2 series. The aim of this release is to provide
fixes for bugs reported by the community against previous JBossAS v4.2.x releases. There were some backwards
compatible component upgrades so switching to AS 4.2.3.GA from a previous 4.2.0/4.2.1/4.2.2 release should not
present any problems. Please check out the Detailed Release Notes section for the full details.
A secondary target for this release was to improve support for Java 6. JBossAS 4.2.3.GA can be build with both JDK5
and JDK6. The JDK5 compiled binaries have undergone more rigorous testing, they constitute our certified version and
can run under both Java 5 & 6 VMs (with a few configuration changes for JDK6, see the configuration section below). The
JDK6 compiled binaries include support for the JDBC 4 APIs, but this should be considered experimental at this point.
JBoss AS 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.
JBoss AS 4.2 is also used as the basis for the JBoss Enterprise Application Platform. The Application Platform
bundles JBoss AS and JBoss Seam in a software package for which commercial support is offered by JBoss/Red Hat.
Please read Sacha's blog if you are interested to learn more about the new development, distribution and support
model for JBoss.
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 of JBoss AS 4.2 series
* 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, JBoss Web
falls back to the standard non-native connector mode. The native libraries need to be downloaded and installed
separately in JBOSS_HOME/bin/native.
* 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, although it should be noted that JBoss TM will not be supported in future JBossAS versions.
* JBoss WS is the web services stack for JBoss 4.2 providing Java EE compatible web services.
* JGroups/JBossCache is already configured to support channel multiplexing, when it becomes available.
* JBoss Remoting was upgraded to the latest stable 2.2.x version. This was done in order to align dependencies
with the thirdparty libraries required by the new JBoss Messaging, which means that, if you want, you can replace
the default JBossMQ messaging provider with JBoss Messaging, without having to revert to a scoped deployment.
Compatibility Issues
This lists the changes that could affect compatibility.
According to our product versioning rules, JBossAS 4.2.3 should be fully compatible with previous JBossAS 4.2.x
releases. However you may want to check the release notes of the individual JBoss and Thirdparty libraries updated
with this release. Some related issues from previous JBoss releases that you should be aware of are listed below:
JBossAS 4.2.2.GA
* JBossWS 1.2.1 supported JAX-WS only as a technology preview while JBossWS 2.0.1 used in AS 4.2.2 provides full
JAX-WS support. If you have used in your code the annotation org.jboss.ws.annotation.WebContext this must be
replaced by org.jboss.wsf.spi.annotation.WebContext.
* JBoss WS 1.0.x due to a deployer limitation used a proprietary .jse extension for deploying WS endpoints
nested in .sar files. This was deprecated with JBoss WS 1.2.x. and with JBoss WS 2.x this proprietary extension is
not supported anymore as it is possible to use the standard .war extension for deploying nested WS endpoints. If you
see: INIT_WAITING_DEPLOYER error messages for .jse files, re-package them using a .war extension, JBWS-1854.
* Another known limitation is that EJB3 web service endpoints can only be specified using annotations and not
metadata in jboss.xml. This is something that will be addressed in a future release, JBAS-4852, JBWS-1813.
* Finding the default local business interface on a ejb3 bean may not work in certain inheritance scenarios.
You may workaround this known problem by annotating the local business interface. Read more about this at EJBTHREE-1062.
* EJB Timer related fixes, JBAS-3379, JBAS-4053.
* JBossMQ related fixes, JBAS-4525, JBAS-4555, JBAS-4559, JBAS-4607, JBAS-4625, JBAS-4699
* JSP compiler now set to compile JDK 1.5 source code by default, JBAS-4605.
* The mail-ra.rar resource adapter was missing from the distro, JBAS-4659.
* HSQLDB (which shouldn't be used in production) v1.8.0.8 has a known bug when used in server mode,
JBAS-4694. This doesn't affect the default jboss installation where HSQLDB is used in in-process mode.
* Serialization of HomeHandleImplIIOP has changed. In the unlikely case of a compatibility problem, define the
system property
-Dorg.jboss.proxy.ejb.old.homehandle.serialization=true
to fall back to the legacy serialization mode, JBAS-4801.
JBossAS 4.2.1.GA
* JBoss TS, the new default transaction manager will not let you enlist multiple 1-phase participants in the
same transaction. This was *not* the default behavior with the legacy JBoss TM that would log a warning and continue.
There are good reasons for this change, mainly to avoid heuristic outcomes in the case of system crashes, which is
the primary reason of using a transaction manager anyway! If your come across this problem you should try to fix it
by switching to XA resources or implementing some form of compensating transactions. However, if this is not option
and you are fully aware of the consequences you can override this behavior by setting com.arjuna.ats.jta.allowMultipleLastResources
to true in conf/jbossjta-properties.xml. For more details read the wiki on Multiple1PC, or consult the JBoss
Transactions documentation.
* A major problem related to the cleaning up of threads after user transaction timeouts was corrected in JBAS-4481.
If you happen to be using User Transactions make sure you follow the correct pattern for committing or rolling them back.
* Another serious classloading issue that could lead to a hanging JBoss with a 100% CPU utilization was fixed with JBAS-4441.
JBossAS 4.2.0.GA
* 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.
* When compared to previous 4.0.x releases, 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.
* Since the latest log4j includes a trace level, there is no need to reference the custom jboss TRACE level in
conf/jboss-log4j.xml configs, JBAS-4163.
Instead of:
you can use:
* 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.
* Apache commons http-client and apache-codec were removed from jbossall-client.jar, JBAS-4365.
* The address that is stored in the host portion of the RMI codebase URL can now be set correctly, JBAS-3325.
* The java2ClassLoadingCompliance setting in jboss-web.xml was ignored; this has been fixed, JBAS-3047.
* In JBoss 4.2 the unified invokers based on JBoss Remoting are the default transport for accessing EJBs.
Using the unified invokers JBoss 4.2 can interoperate safely with JBoss AS 4.0.4.GA/4.0.5.GA, using the flag
-Djboss.remoting.pre_2_0_compatible=true on the JBoss 4.2.x side. For interoperating with older JBoss AS versions
(3.2.8.SP1 to 4.0.3.SP1) the legacy rmi or pooled invokers need to be used. See JBAS-4407 and the wiki page on JBoss
Version Compatibility.
Configuration Issues
This lists the changes that could affect configuration.
JBossAS 4.2.3.GA
* JBossAS 4.2.3.GA can be compiled with both Java5 & Java6. The Java5 compiled binary is our primary/recommended
binary distribution. It has undergone rigorous testing and can run under both a Java 5 and a Java 6 runtime. When
running under Java 6 you need to manually copy the following libraries from the JBOSS_HOME/client directory to
the JBOSS_HOME/lib/endorsed directory, so that the JAX-WS 2.0 apis supported by JBossWS are used:
o jboss-jaxrpc.jar
o jboss-jaxws.jar
o jboss-jaxws-ext.jar
o jboss-saaj.jar
o jaxb-api.jar
* If you still have problems using JBoss with a Sun Java 6 runtime, you may want to set -Dsun.lang.ClassLoader.allowArraySyntax=true,
as described in JBAS-4491. Other potential problems under a Java 6 runtime include:
o ORB getting prematurely destroyed when using Sun JDK 6 (see Sun Bug ID: 6520484)
o Unimplemented methods in Hibernate for JDK6 interfaces.
* When JBossAS 4.2.3 is compiled with Java 6, support for the extended JDBC 4 API is included in the binary,
however this can only be used under a Java 6 runtime. In this case no manual configuration steps are necessary. It
should be noted however that the Java 6 compiled distribution of JBoss AS 4.2.3.GA is still in experimental stage.
JBossAS 4.2.2.GA
* Extensions to LdapExtLoginModule, JBAS-4619.
* Escape syntax for mysql and postgresql in jboss CMP, JBAS-4463.
* Introduced a new system property org.jboss.mx.loading.UnifiedLoaderRepository.notifyMode to
provide fine-grained control over the emission of notifications whenever Unified Classloaders are created.
Classloader leaks can appear if those notifications are send to remote jmx agents, so the usage of the flag can
avoid this problem, JBAS-4953.
JBossAS 4.2.1.GA
* %PATH% is not removed from java.library.path in the presence of JAVA_HOME/bin/native, so e.g. native jdbc
drivers can be loaded, JBAS-4418.
JBossAS 4.2.0.GA
* 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 enable remote access by binding JBoss services to a
particular interface, simply run jboss with the -b option. To bind to all available interfaces and re-enable the
legacy behaviour use -b 0.0.0.0. In any case, be aware you still need to secure you server properly.
* There now distinct properties to configure the various mcast ports, JBAS-4021.
* When running under Linux, run.sh forces the use of IPv4, due to a jdk bug, JBAS-4332.
* 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 Red Hat Linux, check out the changes in bin/jboss_init_redhat.sh, JBAS-4041.
* The JBossAS distributions usually 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.
* bin/shutdown.sh no longer sources run.conf, JBAS-4155.
Library Updates
For a full list of the JBoss and thirdparty libraries used with JBoss AS 4.2.3 see build-thirdparty.xml.
JBossAS 4.2.3.GA
JBoss Library Updates
* javassist upgraded to v3.8.0.GA (from v3.6.0.GA)
* jboss cache upgraded to v1.4.1.SP9 (from v1.4.1.SP5)
* jboss jaxr upgraded to v1.2.0.SP1 (from v1.2.0.GA)
* jboss transactions upgraded to v4.2.3.SP7 (from v4.2.3.SP6)
* jboss ws upgraded to v3.0.1 / native v2.0.4 (from v2.0.1.SP2)
* jboss xb upgraded to v1.0.0.SP3 (from v1.0.0.SP1)
* jboss remoting upgraded to v2.2.2.SP8 (from v2.2.2.SP1)
Thirdparty Library Updates
* jfreechart upgraded to v1.0.2 (from v0.9.20)
* oswego-concurrent upgraded to v1.3.4-jboss-update1 (from v1.3.4-jboss)
* sun-jsf upgraded to v1.2_09-b01 (from v1.2_04_P02)
* codehaus-jettison was introduced at v1.0-RC2
JBossAS 4.2.2.GA
JBoss Library Updates
* javassist upgraded to v3.6.0.GA (from v3.5.0.GA)
* jboss aop upgraded to v1.5.6.GA (from 1.5.5.GA)
* jboss cache upgraded to v1.4.1.SP5 (from 1.4.1.SP3)
* jboss common upgraded to v1.2.1.GA (from v1.2.0.GA)
* jboss remoting upgraded to v2.2.2.SP1 (from v2.2.1.GA)
* jboss ts upgraded to v4.2.3.SP6 (from v4.2.3.SP5)
* jboss web upgraded to v2.0.1.GA (from v2.0.0.GA)
* jboss ws upgraded to v2.0.1.SP2 (from v1.2.1.GA)
* jboss xb upgraded to v1.0.0.SP1 (from v1.0.0.GA)
* jgroups upgraded to v2.4.1.SP4 (from v2.4.1.SP3)
Thirdparty Library Updates
* hsqldb upgraded to v1.8.0.8 (from v1.8.0.2)
* jacorb upgraded to v2.3.0jboss.patch5 (from v2.3.0jboss.patch4)
* oswego-concurrent upgraded to v1.3.4-jboss (from v1.3.4)
JBossAS 4.2.1.GA
JBoss Library Updates
* hibernate, upgraded to v3.2.4.SP1_CP01 (from v3.2.3.GA)
* jboss-ts14, upgraded to v4.2.3.SP5 (from v4.2.3.SP3)
* jboss-remoting, upgraded to v2.2.1.GA (from v2.2.0.SP4)
Thirdparty Library Updates
* jacorb, upgraded to v2.3.0jboss.patch4 (from v2.2.4jboss.patch1)
* sun-jsf, upgraded to v1.2_04_P02 (from v1.2_04_P01)
Detailed Release Notes
JBossAS-4.2.3.GA
Feature Request
* [ JBAS-3051 ] change jmx console title to display the name of the jboss server configuration with the machine name
* [ JBAS-4156 ] [jmx-console] Add additional informatin to page header
* [ JBAS-4455 ] LoadBalancePolicy that tries to pin all requests associated with a tx to one server
* [ JBAS-4501 ] JBoss AS 4.2 won't build with JDK 1.6
* [ JBAS-4804 ] GenericHeaderAuthenticator injection of ssoid, sessioncookie name
* [ JBAS-4986 ] Remove compile-time dependency on Debugger from ClusterPartition
* [ JBAS-5035 ] MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver hard coded
* [ JBAS-5139 ] Support injection-target properties within service-ref declarations
* [ JBAS-5704 ] Provide JAAS credentials in org.jboss.ant.JMX task so that calls can be made to security protected MBeans
Bug
* [ JBAS-1901 ] web-console shows dead archives after redeploy
* [ JBAS-2477 ] Exception in web-console j2ee domain after undeploy of application
* [ JBAS-3402 ] Web Console and Firefox
* [ JBAS-3406 ] JMX Console throws 500 exception on regular expressions
* [ JBAS-3637 ] twiddle ignores environment properties when creating its InitialContext
* [ JBAS-4246 ] JBoss logo not displayed for web status when accessed from web console
* [ JBAS-4287 ] run.sh can consume 100% single CPU resources on Solaris
* [ JBAS-4343 ] NullPointerException causing bad password exception in LdapLoginModule when the role attribute is not set for a given entry
* [ JBAS-4453 ] SerializableResultSetMetaData did not have the classname for the column set.
* [ JBAS-4662 ] XADatasource property names are not using the javabean convention
* [ JBAS-4673 ] SARDeployer should throw an error if there is more than one loader repository
* [ JBAS-4753 ] ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
* [ JBAS-4766 ] HTTP session replication failover failures with async buddy replication
* [ JBAS-4805 ] InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
* [ JBAS-4815 ] UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
* [ JBAS-4870 ] Redelivery flags not updated in case of JBossMQ node failure
* [ JBAS-4892 ] WebService ignores java.rmi.server.codebase system property
* [ JBAS-4897 ] CVE-2007-5461: Information Leak in Tomcat Webdav Servlet
* [ JBAS-4911 ] MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
* [ JBAS-4921 ] Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
* [ JBAS-4927 ] Code added in 4.2.1 breaks web app that works in 4.2.0
* [ JBAS-4934 ] JBossCacheWrapper should not re-use data gravitation option
* [ JBAS-4938 ] source tarball contains non free code
* [ JBAS-4943 ] jboss-ds_1_5.dtd is wrong
* [ JBAS-4945 ] Messages transfered from DLQ to working queue will never be resent to DLQ
* [ JBAS-4950 ] Transaction failover authorisation is broken within UnifiedInvokerHAProxy
* [ JBAS-4964 ] txFailoverAuthorizations should be keyed on transaction propagation context
* [ JBAS-4969 ] Security-domain name entry in options map causing exception in custom login modules
* [ JBAS-4975 ] Usage of read-ahead on-find with entity beans containing binary attributes (mapped to BLOB, VARBINAR, ...) breaks eager loading.
* [ JBAS-4994 ] ReplyHeaderFilter reports old versions: Servlet 2.4, Tomcat-5.5
* [ JBAS-5014 ] EJBMethodPermission implies should check for null methodname and methodSig==""
* [ JBAS-5015 ] Deploy entity beans in Oracle 11g on JBoss 4.2.1 and JBoss 4.2.1
* [ JBAS-5020 ] Incorrect system property usage in JMX console clustering service
* [ JBAS-5026 ] NPE in JvmRouteValve.handleJvmRoute
* [ JBAS-5049 ] NoInitialContextException on deployment of EAR that contains MDB and persistence.xml
* [ JBAS-5063 ] JBoss 4.2.2 doesn't work with JSF RI 1.2_07
* [ JBAS-5068 ] Possible NullPointerException in DistributedReplicantManager#_add()
* [ JBAS-5072 ] Fix null pointer exception when getting keys, values, or entry's in the ConcurrentHashmap
* [ JBAS-5080 ] Need to check transaction status on SQL operations
* [ JBAS-5091 ] BuddyCommunicationTimeout is too low
* [ JBAS-5105 ] PostgreSQL Entity Command for jdbc2pm is Not Working Properly
* [ JBAS-5108 ] Twiddle should print out 'invoke' results, even when no propertyeditor for the returned object is found
* [ JBAS-5109 ] Web context and servlet paramters not available in WebMetaData
* [ JBAS-5112 ] WebXMLRewriter leaks input stream
* [ JBAS-5127 ] Hardcoded partition name in cluster-examples-service.xml
* [ JBAS-5142 ] cmp2.x jdbc2 pm: missing a join in a collection path translating "member of"
* [ JBAS-5149 ] 'webservices' meta data (jboss.xml) not available for ejb3 web service endpoints
* [ JBAS-5189 ] Txn-Manager arjuna commits data after timeout in long transactions
* [ JBAS-5206 ] Can't start JBoss 5 with a pure JRE installation
* [ JBAS-5220 ] twiddle not displaying info regarding java.lang:* beans when
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl is used .
* [ JBAS-5228 ] Race condition maintaining acknowledgements when pushing messages to the client
* [ JBAS-5275 ] org.jboss.test.security.test.XMLLoginModulesUnitTestCase failing on Z-servers
* [ JBAS-5317 ] org.jboss.test.security.test.HttpsUnitTestCase failing with the IBM jvm
* [ JBAS-5354 ] Need to improve error handling around thread pool errors
* [ JBAS-5364 ] UnifiedInvokerHAProxy can throw NullPointerException under load
* [ JBAS-5428 ] Addition of undocumented feature has caused a bug in normal behaviour
* [ JBAS-5431 ] PooledInvokerProxy is not using the TPC factory setup by the UserTransaction client
* [ JBAS-5444 ] remove twiddle.bat/shutdown.bat %ARGS% processing in favour of %*
* [ JBAS-5459 ] JDBCStartCommand fails with index already exists
* [ JBAS-5475 ] NullPointerException when no invoker proxy bindings configured
* [ JBAS-5479 ] SSLSessionInterceptor has a copy/paste error in invokeHome method
* [ JBAS-5492 ] ClusteredSingleSignOn dead member cleaner throws NPE
* [ JBAS-5502 ] Enabling JBossMQ XA recovery fails
* [ JBAS-5526 ] DB Connections established which fail check-valid-connection-sql do not immediatly close their connection
* [ JBAS-5528 ] If SingletonStatelessSessionInstancePool is used for a SLSB, container MBean state is reported incorrectly
* [ JBAS-5568 ] sample-binding.xml does not work for jboss-messaging-1.4
* [ JBAS-5571 ] When JBossMQ does XA recovery it should always write the XID to the log
* [ JBAS-5574 ] Don't log an error for BMT Stateful not completing their transactions
* [ JBAS-5608 ] Removing a session from a clustered sso entry removes all sessions
* [ JBAS-5612 ] MySQLValidConnectionChecker is not serializable
* [ JBAS-5613 ] OracleValidConnectionChecker is not serializable
* [ JBAS-5623 ] JMS ActivationSpec 'acknowledgeMode' does not follow spec recommendation
* [ JBAS-5639 ] org.jboss.test.util.test.PropertyEditorsUnitTestCase failing on Z-systems
* [ JBAS-5644 ] Incorrect containerName attribute setting in valves
* [ JBAS-5657 ] JSP source code exposure in jmx-console
* [ JBAS-5670 ] Using MessageConsumers with Message Selector make messages stuck in queue
* [ JBAS-5678 ] closed jdbc connection before transaction rollback is called
* [ JBAS-5696 ] removal of entity with self-referencing CMR and fk-constraint
* [ JBAS-5706 ] Default session metadata replication too infrequent
* [ JBAS-5735 ] Session not reliably bound to SessionReplicationContext if SecurityAssocationValve not present
Task
* [ JBAS-4148 ] Replace Gjt code used in the ejb 2.x validation phase
* [ JBAS-4424 ] WebAuthentication:Generate a SSOID
* [ JBAS-4811 ] Integrate the JBossWS core testsuite in the release QA
* [ JBAS-4874 ] Track JBoss and thirdparty dependencies for JBossAS 4.2.3
* [ JBAS-4876 ] Re-enable JGroups message bundling
* [ JBAS-4918 ] replace ${jboss.server.home.dir}/log references with ${jboss.server.log.dir}
* [ JBAS-5057 ] testsuite regression org.jboss.test.security.test.EJBPermissionUnitTestCase
* [ JBAS-5059 ] Update Service Binding configuration for JBossMessaging
* [ JBAS-5060 ] Upgrade jfreechart to v1.0.2
* [ JBAS-5088 ] Failing org.jboss.test.jbossmq.test.ConnectionConsumerErrorFiredUnitTestCase.testExceptionListenerFiredOnError (jrockit)
* [ JBAS-5094 ] org.jboss.test.jaxr.scout failures
* [ JBAS-5101 ] Re-enable JGroups message bundling
* [ JBAS-5210 ] Expose sub-pool statistics for Improved Management.
* [ JBAS-5226 ] ClientUserTransaction should be configured with Unified invoker
* [ JBAS-5331 ] AOP deployer should include pluggable instrumentor jar(s)
* [ JBAS-5402 ] Keep JBoss Cache jars out of default
* [ JBAS-5485 ] Add mdbsessionpoolclear testcase from EJB3
* [ JBAS-5648 ] Upgrade to jboss-jaxr-1.0.2.SP1
* [ JBAS-5650 ] Merge clustering fixes from EAP branch
* [ JBAS-5677 ] Add discussion of usage of FC to Clustering Guide
* [ JBAS-5702 ] Add JDBC4 support to DataSourceInterceptor
* [ JBAS-5710 ] Get the JBoss-AS-4.2.x-TestSuite-sun15 passing
* [ JBAS-5711 ] Get the JBoss-AS-4.2.x-TestSuite-jrockit15 passing
* [ JBAS-5712 ] Add JDBC4 support to Branch_4_2
* [ JBAS-5720 ] Get a JBoss-AS-4.2.x-TestSuite-sun15-sun16 going
* [ JBAS-5721 ] Get a JBoss-AS-4.2.x-TestSuite-sun16-sun16 going
* [ JBAS-5722 ] Get all the testsuites passing
* [ JBAS-5723 ] Verify JBoss-AS-4.2.x-CompatibilityMatrix
* [ JBAS-5724 ] Verify TCK1.4 tests are passing
* [ JBAS-5725 ] Verify EJB3 tests are passing
* [ JBAS-5726 ] Verify JBossWS testsuite
* [ JBAS-5731 ] JaxWS 2.0 / JaxWS 2.1 support for Branch_4_2
* [ JBAS-5748 ] Update links in ROOT.war/index.html
* [ JBAS-5750 ] Update the interoperability tests matrix with 4.2.2.GA client libs
* [ JBAS-5765 ] Make release notes for 4.2.3.GA
Sub-task
* [ JBAS-4875 ] Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)
* [ JBAS-4877 ] Upgrade JSF to 1.2_08
* [ JBAS-4925 ] Upgrade jboss cache to 1.4.1.SP7 (from 1.4.1.SP5)
* [ JBAS-4933 ] Upgrade to jbossxb 1.0.0.SP3 (from 1.0.0.SP1)
* [ JBAS-4955 ] All the known bind address properties should be set to the default bind address
* [ JBAS-4962 ] Upgrade jboss remoting to v2.2.2.SP5 (from v2.2.2.SP1)
* [ JBAS-4981 ] Transaction variable is not reset in ejb2 inflow interceptor
* [ JBAS-4996 ] Upgrade jbossws to 2.0.4.GA (from 2.0.1.SP2)
* [ JBAS-5082 ] Add a transaction status interface for the connection manager and implement it in TxConnectionManager
* [ JBAS-5083 ] Add the transaction active check to the jdbc resource adapter
* [ JBAS-5084 ] Add the transaction active check to the jms resource adapter
* [ JBAS-5170 ] 4.2.x fix to get HA Singleton election policies working in heterogeneous topologies
* [ JBAS-5498 ] JDK6: org.jboss.test.security.test.LoginModulesUnitTestCase
* [ JBAS-5727 ] Upgrade javassist to 3.8.0.GA
* [ JBAS-5729 ] Upgrade jboss remoting to v2.2.2.SP8 (from v2.2.2.SP5)
* [ JBAS-5753 ] fix org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase
* [ JBAS-5754 ] Get tests-webservice passing
* [ JBAS-5755 ] org.jboss.test.jca.test.StatisticsFormatterUnitTestCase.testXmlFormatterStatistics
* [ JBAS-5758 ] fix iiop tests
* [ JBAS-5764 ] Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08)
* [ JBAS-5768 ] Upgrade JBoss Cache to 1.4.1.SP9
* [ JBAS-5769 ] Fix org.jboss.test.jca.test.BackgroundValidationUnitTestCase.testDeployedBackgroundValidationFailure
* [ JBAS-5770 ] fix 3 org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase failures
* [ JBAS-5772 ] org.jboss.test.cluster.test/FamilyClusterInfoUnitTestCase(Default-TCP)/testSynchronization
Patch
* [ JBAS-4478 ] ignore local ant options when building
* [ JBAS-5073 ] fix build authenticated proxy (there seems to have been a cut and paste error at some point)
* [ JBAS-5527 ] jboss_4_0.dtd should include support for SingletonStatelessSessionInstancePool
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165448#4165448
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165448
17 years, 9 months