core-jgi/jboss/readme.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><!-- $Id: readme.html,v 1.1.2.36 2006/05/13 15:42:36 dimitris Exp $ -->
<meta content="text/html" http-equiv="content-type"><meta content="JBoss Inc." name="author"><title>JBoss
4.2.3.GA Readme</title></head>
<body><a href="http://www.jboss.com"><img src="http://www.jboss.com/themes/jbosstheme/img/logo.gif" alt="JBoss - A Division of Red Hat" border="0"></a><h1>JBoss
AS 4.2.3.GA
Release Notes</h1>
<p>This is the 3rd&nbsp;bug fixing release of the <a href="http://www.jboss.org/jbossas/">JBoss Application
Server</a> v4.2 series.&nbsp;The aim of this release is to
provide fixes for&nbsp;bugs reported by the
community&nbsp;against previous JBossAS
v4.2.x releases.&nbsp;There were some backwards compatible <a href="#Libraries">component
upgrades</a> 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&nbsp;the <a href="readme.html#Details">Detailed
Release Notes</a> section for the full details.</p>
<p>A secondary target for this release was to
improve&nbsp;support for Java 6. JBossAS 4.2.3.GA can be build with
both JDK5 <span style="font-style: italic;">and</span><span style="font-weight: bold; font-style: italic;"> </span>JDK6.
The JDK5 compiled binaries have undergone more rigorous testing, they
constitute our certified version and can run under both Java 5
&amp; 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.</p><p>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.</p>
<p>JBoss AS 4.2 is also used as the basis for the<a href="http://www.redhat.com/jboss/platforms/application/">
JBoss Enterprise Application Platform.</a> The <i>Application
Platform</i> bundles <span style="text-decoration: underline;"></span><a href="http://www.jboss.org/jbossas/">JBoss AS&nbsp;</a>and
<a href="http://www.jboss.org/jbossseam/">JBoss Seam</a>&nbsp;
in a software package for which commercial support
is offered
by JBoss/Red Hat. Please read
<a href="http://blogs.jboss.com/blog/slabourey/2007/04/24/New+Development,+Distribution+and+Support+Model+for+JBoss.txt">Sacha's
blog</a> if you are interested to learn more about the new
development, distribution and support model for JBoss.</p>
<p>For information on the APIs that make up Java EE 1.4, see <a href="http://java.sun.com/j2ee/1.4/docs/index.html"> Java EE
v1.4 Documentation</a>. For a comprehensive tutorial on Java EE
1.4, see <a href="http://java.sun.com/j2ee/1.4/docs/tutorial-update2/doc/index.html">
The Java EE&trade; 1.4 Tutorial</a>. A jboss-4.2.x getting
started guide that is based on contents from the tutorial can be found
in <a href="http://www.jboss.org/jbossas/docs">JBoss
Application Server Documentation Library</a></p>
<p> <em>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.</em></p>
<!-- ======================================================= --><h2>Overview</h2>
<ul><li><a href="#Highlights">Highlights</a></li>
<li><a href="#Compatibility">Known Compatibility
Issues</a></li>
<li><a href="#Configuration">Known Configuration
Issues</a></li>
<li><a href="#Libraries">JBoss/Thirdparty
Library Updates</a></li>
<li><a href="#Details">Detailed Release Notes</a></li>
<li><a href="#Documentation">Additional Docs and
Help</a></li>
<li><a href="#Licenses">Licenses</a></li>
<li><a href="#About">About JBoss</a></li>
</ul><!-- ======================================================= --><h2><a name="Highlights">Highlights of
JBoss AS 4.2
series</a></h2>
<ul><li><a href="http://www.jboss.org/portal/jbossejb3">JBoss
EJB3</a> 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.</li><li><a href="http://www.jboss.com/products/jbossweb">JBoss
Web</a> 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 <a href="http://www.jboss.org/jbossweb/downloads">downloaded</a>
and installed separately in JBOSS_HOME/bin/native.</li>
<li><a href="http://www.jboss.com/products/transactions">JBoss
Transactions</a> 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&nbsp;JBoss TM will not be supported in future JBossAS versions.</li>
<li><a href="http://labs.jboss.com/portal/jbossws">JBoss
WS</a>
is the web services stack for JBoss 4.2 providing Java EE compatible
web services.</li>
<li><a href="http://labs.jboss.com/portal/jgroups">JGroups</a>/<a href="http://www.jboss.org/products/jbosscache">JBossCache</a>
is already configured
to support channel multiplexing, when it becomes available.</li>
<li><a href="http://labs.jboss.com/jbossremoting/">JBoss
Remoting</a> 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 <a href="http://labs.jboss.com/jbossmessaging/">JBoss Messaging</a>,
which means that, if you want, you can replace the default <a href="http://www.jboss.org/wiki/Wiki.jsp?page=JBossMQ">JBossMQ</a>
messaging provider with JBoss Messaging, without having to revert to a
scoped deployment.</li>
</ul><!-- ======================================================= --><h2><a name="Compatibility">Compatibility
Issues</a></h2>
This lists the changes that could affect compatibility.<br>
<br>According to our <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning">product
versioning rules</a>, 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&nbsp;<a href="readme.html#Libraries">JBoss
and Thirdparty libraries</a> updated with this release. Some
related issues from previous JBoss releases that you should be aware of
are listed below:<br>
<h3>JBossAS 4.2.2.GA</h3><ul><li>JBossWS 1.2.1
supported JAX-WS only as
a technology preview while JBossWS&nbsp;2.0.1 used in AS 4.2.2
provides
full JAX-WS support. If you have used in your code
the&nbsp;annotation <span style="font-family: monospace;">org.jboss.ws.annotation.WebContext</span>&nbsp;this
must&nbsp;be&nbsp;replaced by <span style="font-family: monospace;">org.jboss.wsf.spi.annotation.WebContext.</span></li><li>JBoss
WS 1.0.x&nbsp;due to a deployer limitation used a proprietary .jse
extension&nbsp;for deploying WS endpoints&nbsp;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&nbsp;.war extension for deploying nested WS endpoints.
If
you see:&nbsp;INIT_WAITING_DEPLOYER error messages for .jse files,
re-package them using a .war extension, <a href="http://jira.jboss.com/jira/browse/JBWS-1854">JBWS-1854</a>.<span style="font-family: monospace;"></span></li><li>Another
known limitation is that&nbsp;EJB3 web service endpoints can only
be
specified using annotations and not metadata in jboss.xml. This is
something that will be addressed&nbsp;in a future release, <a href="http://jira.jboss.com/jira/browse/JBAS-4852">JBAS-4852</a>,
<a href="http://jira.jboss.com/jira/browse/JBWS-1813">JBWS-1813</a>.</li><li>Finding
the default local business interface on a ejb3 bean may not work in
certain inheritance scenarios. You may workaround this known
problem&nbsp;by&nbsp;annotating the local business interface.
Read more
about this at <a href="http://jira.jboss.com/jira/browse/EJBTHREE-1062">EJBTHREE-1062</a>.<span style="font-family: monospace;"><br></span></li><li>EJB
Timer
related fixes, <a href="http://jira.jboss.com/jira/browse/JBAS-3379">JBAS-3379</a>,
<a href="http://jira.jboss.com/jira/browse/JBAS-4053">JBAS-4053</a>.</li><li>JBossMQ
related fixes, JBAS-4525, JBAS-4555, JBAS-4559, JBAS-4607, JBAS-4625,
JBAS-4699</li><li>JSP compiler now set to compile JDK 1.5
source code by default, <a href="http://jira.jboss.com/jira/browse/JBAS-4605">JBAS-4605</a>.</li><li>The
mail-ra.rar resource adapter was missing from the distro, <a href="http://jira.jboss.com/jira/browse/JBAS-4659">JBAS-4659</a>.</li><li>HSQLDB
(which shouldn't be used in production) v1.8.0.8 has a known bug when
used in server mode, <a href="http://jira.jboss.com/jira/browse/JBAS-4694">JBAS-4694</a>.
This doesn't affect the default jboss installation where HSQLDB is used
in in-process mode.</li><li>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, <a href="http://jira.jboss.com/jira/browse/JBAS-4801">JBAS-4801</a>.
</li></ul><h3>JBossAS
4.2.1.GA
</h3><ul><li>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 <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=Multiple1PC">Multiple1PC</a>,
or consult the <a href="http://labs.jboss.com/jbosstm/docs/index.html">JBoss
Transactions documentation</a>.</li>
<li>A major problem related to the cleaning up of threads after
user transaction timeouts was corrected in <a href="http://jira.jboss.com/jira/browse/JBAS-4481">JBAS-4481</a>.
If you happen to be using User Transactions make sure you follow the <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=WhatIsTheCorrectPatternForUserTransactions">correct
pattern</a> for committing or rolling them back.</li>
<li>Another serious classloading issue that could lead to a
hanging JBoss with a 100% CPU utilization was fixed with <a href="http://jira.jboss.com/jira/browse/JBAS-4441">JBAS-4441</a>.</li>
</ul><h3>JBossAS 4.2.0.GA</h3>
<ul><li><strong>A JavaSE 5 runtime is </strong><strong>required</strong>
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, <a href="http://jira.jboss.com/jira/browse/JBAS-4161">JBAS-4161</a>.</li>
<li>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.</li>
<li>Tomcat 6 is now bundled as part of JBoss Web.
deploy/jbossweb-tomcat55.sar has been replaced by
deploy/jboss-web.deployer.</li>
<li>conf/log4j.xml has been renamed to conf/jboss-log4j.xml, to
allow log4j.properties override from scoped deployments, <a href="http://jira.jboss.com/jira/browse/JBAS-1853">JBAS-1853</a>.</li>
<li>log4j and commons-logging have both been upgraded.
commons-logging is patched in addition, <a href="http://jira.jboss.com/jira/browse/JBAS-2823"> JBAS-2823</a>.</li>
<li>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, <a href="http://jira.jboss.com/jira/browse/JBAS-4163">JBAS-4163</a>.<br>
Instead of: &lt;category
name="org.jboss.system"&gt;&lt;priority value="TRACE"
class="org.jboss.logging.XLevel"/&gt;&lt;/category&gt;<br>
you can use: &lt;category
name="org.jboss.system"&gt;&lt;priority
value="TRACE"/&gt;&lt;/category&gt;</li>
<li>Better integration with WebSphere MQ 5.x, <a href="http://jira.jboss.com/jira/browse/JBAS-3183">JBAS-3183</a>.</li>
<li>The MyFaces JSF implementation has been replaced by the
Glassfish JSF 1.2 one, <a href="http://jira.jboss.com/jira/browse/JBAS-3897">JBAS-3897</a>.</li>
<li>Hibernate, hibernate-annotations and
hibernate-entity-manager have all been upgraded. to v3.2.1.</li>
<li>The default invoker for EJBs has been changed from the
rmi-invoker to the unified-invoker, provided by JBoss Remoting, <a href="http://jira.jboss.com/jira/browse/JBAS-3950">JBAS-3950</a>.</li>
<li>Apache commons http-client and apache-codec were removed
from jbossall-client.jar, <a href="http://jira.jboss.com/jira/browse/JBAS-4365"> JBAS-4365</a>.</li>
<li>The address that is stored in the host portion of the RMI
codebase URL can now be set correctly,<a href="http://jira.jboss.com/jira/browse/JBAS-3325"> JBAS-3325</a>.</li>
<li>The java2ClassLoadingCompliance setting in jboss-web.xml
was ignored; this has been fixed, <a href="http://jira.jboss.com/jira/browse/JBAS-3047"> JBAS-3047</a>.</li>
<li>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 <a href="http://jira.jboss.com/jira/browse/JBAS-4407">JBAS-4407</a>
and the wiki page on <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossVersionCompatibilityMatrix">
JBoss Version Compatibility</a>.</li>
</ul><!-- ======================================================= --><h2><a name="Configuration">Configuration
Issues</a></h2>
This lists the changes that could affect configuration.<br>
<h3>JBossAS 4.2.3.GA</h3><ul><li>JBossAS
4.2.3.GA can be compiled with both Java5 &amp; 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:</li><ul><li>jboss-jaxrpc.jar</li><li>jboss-jaxws.jar</li><li>jboss-jaxws-ext.jar</li><li>jboss-saaj.jar</li><li>jaxb-api.jar</li></ul><li>If
you still have problems using JBoss with a Sun Java 6
runtime,&nbsp;you may want to set&nbsp; <span style="font-family: monospace;">-Dsun.lang.ClassLoader.allowArraySyntax=true</span>,
as described in <a href="http://jira.jboss.com/jira/browse/JBAS-4491">JBAS-4491</a>.
Other potential problems under a Java 6 runtime include:</li><ul><li>ORB
getting prematurely destroyed when using Sun JDK 6 (see Sun Bug ID: <a href="http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=fd40a0e2c4c9b79adab12ca088bd?bug_id=6520484">6520484)</a></li><li>Unimplemented
methods in Hibernate for JDK6 interfaces.</li></ul><li>When&nbsp;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&nbsp;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.</li></ul><h3>JBossAS
4.2.2.GA</h3><ul><li>Extensions to
LdapExtLoginModule, <a href="http://jira.jboss.com/jira/browse/JBAS-4619">JBAS-4619</a>.</li><li>Escape
syntax for mysql and postgresql in jboss CMP,<a href="http://jira.jboss.com/jira/browse/JBAS-4463"> JBAS-4463</a>.</li><li>Introduced
a new system
property org.jboss.mx.loading.UnifiedLoaderRepository.notifyMode to
provide fine-grained control over the emission of notifications
whenever&nbsp;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,&nbsp;<a href="http://jira.jboss.com/jira/browse/JBAS-4593">JBAS-4953</a>.
</li></ul><h3>JBossAS 4.2.1.GA</h3>
<ul><li>%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, <a href="http://jira.jboss.com/jira/browse/JBAS-4418">JBAS-4418</a>.</li>
</ul><h3>JBossAS 4.2.0.GA
</h3><ul><li>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 s<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">ecured
their servers properly</a>.
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,&nbsp;be aware you still need
to <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">secure
you server properly</a>.</li>
<li>There now distinct properties to configure the various
mcast ports, <a href="http://jira.jboss.com/jira/browse/JBAS-4021">JBAS-4021</a>.</li>
<li>When running under Linux, run.sh forces the use of IPv4,
due to a jdk bug, <a href="http://jira.jboss.com/jira/browse/JBAS-4332">JBAS-4332</a>.</li>
<li>JBoss EJB3 is now included by default. If you don't
need/want EJB3 support, simply remove deploy/ejb3.deployer.</li>
<li>When using native libraries for JBoss Web store them in
JBOSS_HOME/bin/native, which is automatically included in the
classpath, <a href="http://jira.jboss.com/jira/browse/JBAS-4162">JBAS-4162</a>.</li>
<li>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.</li>
<li>If you are on Red Hat Linux, check out the changes in
bin/jboss_init_redhat.sh, <a href="http://jira.jboss.com/jira/browse/JBAS-4041">JBAS-4041</a>.</li>
<li>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.</li>
<li>bin/shutdown.sh no longer sources run.conf, <a href="http://jira.jboss.com/jira/browse/JBAS-4155">JBAS-4155</a>.</li>
</ul><!-- ======================================================= --><h2><a name="Libraries">Library Updates</a></h2>
For a full list of the JBoss and thirdparty libraries used
with JBoss AS 4.2.3 see &nbsp;<a href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_3_GA/build/build-thirdparty.xml">build-thirdparty.xml.</a>
<h3>JBossAS 4.2.3.GA</h3><p>JBoss Library Updates</p><ul><li>javassist
upgraded to v3.8.0.GA (from v3.6.0.GA)</li><li>jboss cache
upgraded to v1.4.1.SP9 (from v1.4.1.SP5)</li><li>jboss jaxr
upgraded to v1.2.0.SP1 (from v1.2.0.GA)</li><li>jboss
transactions upgraded to v4.2.3.SP7 (from v4.2.3.SP6)</li><li>jboss
ws upgraded to v3.0.1 / native v2.0.4 (from v2.0.1.SP2)</li><li>jboss
xb upgraded to v1.0.0.SP3 (from v1.0.0.SP1)</li><li>jboss
remoting upgraded to v2.2.2.SP8 (from v2.2.2.SP1)</li></ul><p>Thirdparty
Library Updates</p><ul><li>jfreechart upgraded to
v1.0.2 (from v0.9.20)</li><li>oswego-concurrent upgraded to
v1.3.4-jboss-update1 (from v1.3.4-jboss)</li><li>sun-jsf
upgraded to v1.2_09-b01 (from v1.2_04_P02)</li><li>codehaus-jettison
was introduced at v1.0-RC2</li></ul><h3>JBossAS
4.2.2.GA</h3>JBoss Library Updates
<ul><li>javassist upgraded to v3.6.0.GA (from v3.5.0.GA)</li><li>jboss
aop upgraded to v1.5.6.GA (from 1.5.5.GA)</li><li>jboss
cache upgraded to v1.4.1.SP5 (from 1.4.1.SP3)</li><li>jboss
common upgraded to v1.2.1.GA (from v1.2.0.GA)</li><li>jboss
remoting upgraded to v2.2.2.SP1 (from v2.2.1.GA)</li><li>jboss
ts upgraded to v4.2.3.SP6 (from v4.2.3.SP5)</li><li>jboss
web upgraded to v2.0.1.GA (from v2.0.0.GA)</li><li>jboss ws
upgraded to v2.0.1.SP2 (from v1.2.1.GA)</li><li>jboss xb
upgraded to v1.0.0.SP1 (from v1.0.0.GA)</li><li>jgroups
upgraded to v2.4.1.SP4 (from v2.4.1.SP3)</li></ul>Thirdparty
Library Updates
<ul><li>hsqldb upgraded to v1.8.0.8 (from v1.8.0.2)</li><li>jacorb
upgraded to v2.3.0jboss.patch5 (from v2.3.0jboss.patch4)</li><li>oswego-concurrent
upgraded to v1.3.4-jboss (from v1.3.4)</li></ul><h3>JBossAS
4.2.1.GA</h3>
JBoss Library Updates
<ul><li>hibernate, upgraded to v3.2.4.SP1_CP01
(from&nbsp;v3.2.3.GA)</li>
<li>jboss-ts14, upgraded to v4.2.3.SP5
(from&nbsp;v4.2.3.SP3)</li>
<li>jboss-remoting, upgraded to v2.2.1.GA (from v2.2.0.SP4)</li>
</ul>Thirdparty Library Updates
<ul><li>jacorb, upgraded to v2.3.0jboss.patch4 (from
v2.2.4jboss.patch1)</li>
<li>sun-jsf, upgraded to&nbsp;v1.2_04_P02 (from v1.2_04_P01)</li>
</ul><!-- ======================================================= --><h1><a name="Details">Detailed Release Notes</a>
</h1><h3>JBossAS-4.2.3.GA<br></h3><h2>Feature
Request</h2> <ul> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-3051">JBAS-3051</a>
] change jmx console title to display the name of the jboss server
configuration with the machine name </li><li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4156">JBAS-4156</a>
] [jmx-console] Add additional informatin to page header </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4455">JBAS-4455</a>
] LoadBalancePolicy that tries to pin all requests associated with a tx
to one server </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4501">JBAS-4501</a>
] JBoss AS 4.2 won't build with JDK 1.6 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4804">JBAS-4804</a>
] GenericHeaderAuthenticator injection of ssoid, sessioncookie name </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4986">JBAS-4986</a>
] Remove compile-time dependency on Debugger from ClusterPartition </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5035">JBAS-5035</a>
] MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver
hard coded </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5139">JBAS-5139</a>
] Support injection-target properties within service-ref declarations </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5704">JBAS-5704</a>
] Provide JAAS credentials in org.jboss.ant.JMX task so that calls can
be made to security protected MBeans </li> </ul>
<h2>Bug</h2> <ul> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-1901">JBAS-1901</a>
] web-console shows dead archives after redeploy </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-2477">JBAS-2477</a>
] Exception in web-console j2ee domain after undeploy of application </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-3402">JBAS-3402</a>
] Web Console and Firefox </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-3406">JBAS-3406</a>
] JMX Console throws 500 exception on regular expressions </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-3637">JBAS-3637</a>
] twiddle ignores environment properties when creating its
InitialContext </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4246">JBAS-4246</a>
] JBoss logo not displayed for web status when accessed from web
console </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4287">JBAS-4287</a>
] run.sh can consume 100% single CPU resources on Solaris </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4343">JBAS-4343</a>
] NullPointerException causing bad password exception in
LdapLoginModule when the role attribute is not set for a given entry </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4453">JBAS-4453</a>
] SerializableResultSetMetaData did not have the classname for the
column set. </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4662">JBAS-4662</a>
] XADatasource property names are not using the javabean convention </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4673">JBAS-4673</a>
] SARDeployer should throw an error if there is more than one loader
repository </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4753">JBAS-4753</a>
] ExternalContext can pass duplicate interfaces to
Proxy.newProxyInstance(loader, interfaces, handler) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4766">JBAS-4766</a>
] HTTP session replication failover failures with async buddy
replication </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4805">JBAS-4805</a>
] InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4815">JBAS-4815</a>
] UnifiedInvokerProxyHA - Client instance check and assignment should
be atomic </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4870">JBAS-4870</a>
] Redelivery flags not updated in case of JBossMQ node failure </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4892">JBAS-4892</a>
] WebService ignores java.rmi.server.codebase system property </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4897">JBAS-4897</a>
] CVE-2007-5461: Information Leak in Tomcat Webdav Servlet </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4911">JBAS-4911</a>
] MSSQLValidConnectionChecker throws exception with MS SQL Server 2005
JDBC driver </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4921">JBAS-4921</a>
] Web service deployment: web.xml modified to web.xml.org - Subsequent
runs fail </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4927">JBAS-4927</a>
] Code added in 4.2.1 breaks web app that works in 4.2.0 </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4934">JBAS-4934</a>
] JBossCacheWrapper should not re-use data gravitation option </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4938">JBAS-4938</a>
] source tarball contains non free code </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4943">JBAS-4943</a>
] jboss-ds_1_5.dtd is wrong </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4945">JBAS-4945</a>
] Messages transfered from DLQ to working queue will never be resent to
DLQ </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4950">JBAS-4950</a>
] Transaction failover authorisation is broken within
UnifiedInvokerHAProxy </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4964">JBAS-4964</a>
] txFailoverAuthorizations should be keyed on transaction propagation
context </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4969">JBAS-4969</a>
] Security-domain name entry in options map causing exception in custom
login modules </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4975">JBAS-4975</a>
] Usage of read-ahead on-find with entity beans containing binary
attributes (mapped to BLOB, VARBINAR, ...) breaks eager loading. </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4994">JBAS-4994</a>
] ReplyHeaderFilter reports old versions: Servlet 2.4, Tomcat-5.5 </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5014">JBAS-5014</a>
] EJBMethodPermission implies should check for null methodname and
methodSig=="" </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5015">JBAS-5015</a>
] Deploy entity beans in Oracle 11g on JBoss 4.2.1 and JBoss 4.2.1 </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5020">JBAS-5020</a>
] Incorrect system property usage in JMX console clustering service </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5026">JBAS-5026</a>
] NPE in JvmRouteValve.handleJvmRoute </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5049">JBAS-5049</a>
] NoInitialContextException on deployment of EAR that contains MDB and
persistence.xml </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5063">JBAS-5063</a>
] JBoss 4.2.2 doesn't work with JSF RI 1.2_07 </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5068">JBAS-5068</a>
] Possible NullPointerException in DistributedReplicantManager#_add() </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5072">JBAS-5072</a>
] Fix null pointer exception when getting keys, values, or entry's in
the ConcurrentHashmap </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5080">JBAS-5080</a>
] Need to check transaction status on SQL operations </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5091">JBAS-5091</a>
] BuddyCommunicationTimeout is too low </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5105">JBAS-5105</a>
] PostgreSQL Entity Command for jdbc2pm is Not Working Properly </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5108">JBAS-5108</a>
] Twiddle should print out 'invoke' results, even when no
propertyeditor for the returned object is found </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5109">JBAS-5109</a>
] Web context and servlet paramters not available in WebMetaData </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5112">JBAS-5112</a>
] WebXMLRewriter leaks input stream </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5127">JBAS-5127</a>
] Hardcoded partition name in cluster-examples-service.xml </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5142">JBAS-5142</a>
] cmp2.x jdbc2 pm: missing a join in a collection path translating
"member of" </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5149">JBAS-5149</a>
] 'webservices' meta data (jboss.xml) not available for ejb3 web
service endpoints </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5189">JBAS-5189</a>
] Txn-Manager arjuna commits data after timeout in long transactions </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5206">JBAS-5206</a>
] Can't start JBoss 5 with a pure JRE installation </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5220">JBAS-5220</a>
] twiddle not displaying info regarding java.lang:* beans when
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
is used . </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5228">JBAS-5228</a>
] Race condition maintaining acknowledgements when pushing messages to
the client </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5275">JBAS-5275</a>
] org.jboss.test.security.test.XMLLoginModulesUnitTestCase failing on
Z-servers </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5317">JBAS-5317</a>
] org.jboss.test.security.test.HttpsUnitTestCase failing with the IBM
jvm </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5354">JBAS-5354</a>
] Need to improve error handling around thread pool errors </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5364">JBAS-5364</a>
] UnifiedInvokerHAProxy can throw NullPointerException under load </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5428">JBAS-5428</a>
] Addition of undocumented feature has caused a bug in normal behaviour
</li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5431">JBAS-5431</a>
] PooledInvokerProxy is not using the TPC factory setup by the
UserTransaction client </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5444">JBAS-5444</a>
] remove twiddle.bat/shutdown.bat %ARGS% processing in favour of %* </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5459">JBAS-5459</a>
] JDBCStartCommand fails with index already exists </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5475">JBAS-5475</a>
] NullPointerException when no invoker proxy bindings configured </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5479">JBAS-5479</a>
] SSLSessionInterceptor has a copy/paste error in invokeHome method </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5492">JBAS-5492</a>
] ClusteredSingleSignOn dead member cleaner throws NPE </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5502">JBAS-5502</a>
] Enabling JBossMQ XA recovery fails </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5526">JBAS-5526</a>
] DB Connections established which fail check-valid-connection-sql do
not immediatly close their connection </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5528">JBAS-5528</a>
] If SingletonStatelessSessionInstancePool is used for a SLSB,
container MBean state is reported incorrectly </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5568">JBAS-5568</a>
] sample-binding.xml does not work for jboss-messaging-1.4 </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5571">JBAS-5571</a>
] When JBossMQ does XA recovery it should always write the XID to the
log </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5574">JBAS-5574</a>
] Don't log an error for BMT Stateful not completing their transactions
</li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5608">JBAS-5608</a>
] Removing a session from a clustered sso entry removes all sessions </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5612">JBAS-5612</a>
] MySQLValidConnectionChecker is not serializable </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5613">JBAS-5613</a>
] OracleValidConnectionChecker is not serializable </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5623">JBAS-5623</a>
] JMS ActivationSpec 'acknowledgeMode' does not follow spec
recommendation </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5639">JBAS-5639</a>
] org.jboss.test.util.test.PropertyEditorsUnitTestCase failing on
Z-systems </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5644">JBAS-5644</a>
] Incorrect containerName attribute setting in valves </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5657">JBAS-5657</a>
] JSP source code exposure in jmx-console </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5670">JBAS-5670</a>
] Using MessageConsumers with Message Selector make messages stuck in
queue </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5678">JBAS-5678</a>
] closed jdbc connection before transaction rollback is called </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5696">JBAS-5696</a>
] removal of entity with self-referencing CMR and fk-constraint </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5706">JBAS-5706</a>
] Default session metadata replication too infrequent </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5735">JBAS-5735</a>
] Session not reliably bound to SessionReplicationContext if
SecurityAssocationValve not present </li> </ul> <h2>Task</h2>
<ul> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4148">JBAS-4148</a>
] Replace Gjt code used in the ejb 2.x validation phase </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4424">JBAS-4424</a>
] WebAuthentication:Generate a SSOID </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4811">JBAS-4811</a>
] Integrate the JBossWS core testsuite in the release QA </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4874">JBAS-4874</a>
] Track JBoss and thirdparty dependencies for JBossAS 4.2.3 </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4876">JBAS-4876</a>
] Re-enable JGroups message bundling </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4918">JBAS-4918</a>
] replace ${jboss.server.home.dir}/log references with
${jboss.server.log.dir} </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5057">JBAS-5057</a>
] testsuite regression
org.jboss.test.security.test.EJBPermissionUnitTestCase </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5059">JBAS-5059</a>
] Update Service Binding configuration for JBossMessaging </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5060">JBAS-5060</a>
] Upgrade jfreechart to v1.0.2 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5088">JBAS-5088</a>
] Failing
org.jboss.test.jbossmq.test.ConnectionConsumerErrorFiredUnitTestCase.testExceptionListenerFiredOnError
(jrockit) </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5094">JBAS-5094</a>
] org.jboss.test.jaxr.scout failures </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5101">JBAS-5101</a>
] Re-enable JGroups message bundling </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5210">JBAS-5210</a>
] Expose sub-pool statistics for Improved Management. </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5226">JBAS-5226</a>
] ClientUserTransaction should be configured with Unified invoker </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5331">JBAS-5331</a>
] AOP deployer should include pluggable instrumentor jar(s) </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5402">JBAS-5402</a>
] Keep JBoss Cache jars out of default </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5485">JBAS-5485</a>
] Add mdbsessionpoolclear testcase from EJB3 </li> <li> [
<a href="https://jira.jboss.org/jira/browse/JBAS-5648">JBAS-5648</a>
] Upgrade to jboss-jaxr-1.0.2.SP1 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5650">JBAS-5650</a>
] Merge clustering fixes from EAP branch </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5677">JBAS-5677</a>
] Add discussion of usage of FC to Clustering Guide </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5702">JBAS-5702</a>
] Add JDBC4 support to DataSourceInterceptor </li> <li> [
<a href="https://jira.jboss.org/jira/browse/JBAS-5710">JBAS-5710</a>
] Get the JBoss-AS-4.2.x-TestSuite-sun15 passing </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5711">JBAS-5711</a>
] Get the JBoss-AS-4.2.x-TestSuite-jrockit15 passing </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5712">JBAS-5712</a>
] Add JDBC4 support to Branch_4_2 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5720">JBAS-5720</a>
] Get a JBoss-AS-4.2.x-TestSuite-sun15-sun16 going </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5721">JBAS-5721</a>
] Get a JBoss-AS-4.2.x-TestSuite-sun16-sun16 going </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5722">JBAS-5722</a>
] Get all the testsuites passing </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5723">JBAS-5723</a>
] Verify JBoss-AS-4.2.x-CompatibilityMatrix </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5724">JBAS-5724</a>
] Verify TCK1.4 tests are passing </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5725">JBAS-5725</a>
] Verify EJB3 tests are passing </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5726">JBAS-5726</a>
] Verify JBossWS testsuite </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5731">JBAS-5731</a>
] JaxWS 2.0 / JaxWS 2.1 support for Branch_4_2 </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5748">JBAS-5748</a>
] Update links in ROOT.war/index.html </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5750">JBAS-5750</a>
] Update the interoperability tests matrix with 4.2.2.GA client libs </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5765">JBAS-5765</a>
] Make release notes for 4.2.3.GA </li> </ul> <h2>Sub-task</h2>
<ul> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4875">JBAS-4875</a>
] Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6) </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4877">JBAS-4877</a>
] Upgrade JSF to 1.2_08 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4925">JBAS-4925</a>
] Upgrade jboss cache to 1.4.1.SP7 (from 1.4.1.SP5) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4933">JBAS-4933</a>
] Upgrade to jbossxb 1.0.0.SP3 (from 1.0.0.SP1) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4955">JBAS-4955</a>
] All the known bind address properties should be set to the default
bind address </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4962">JBAS-4962</a>
] Upgrade jboss remoting to v2.2.2.SP5 (from v2.2.2.SP1) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4981">JBAS-4981</a>
] Transaction variable is not reset in ejb2 inflow interceptor </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-4996">JBAS-4996</a>
] Upgrade jbossws to 2.0.4.GA (from 2.0.1.SP2) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5082">JBAS-5082</a>
] Add a transaction status interface for the connection manager and
implement it in TxConnectionManager </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5083">JBAS-5083</a>
] Add the transaction active check to the jdbc resource adapter </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5084">JBAS-5084</a>
] Add the transaction active check to the jms resource adapter </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5170">JBAS-5170</a>
] 4.2.x fix to get HA Singleton election policies working in
heterogeneous topologies </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5498">JBAS-5498</a>
] JDK6: org.jboss.test.security.test.LoginModulesUnitTestCase </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5727">JBAS-5727</a>
] Upgrade javassist to 3.8.0.GA </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5729">JBAS-5729</a>
] Upgrade jboss remoting to v2.2.2.SP8 (from v2.2.2.SP5) </li> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-5753">JBAS-5753</a>
] fix org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5754">JBAS-5754</a>
] Get tests-webservice passing </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5755">JBAS-5755</a>
]
org.jboss.test.jca.test.StatisticsFormatterUnitTestCase.testXmlFormatterStatistics
</li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5758">JBAS-5758</a>
] fix iiop tests </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5764">JBAS-5764</a>
] Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08) </li>
<li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5768">JBAS-5768</a>
] Upgrade JBoss Cache to 1.4.1.SP9 </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5769">JBAS-5769</a>
] Fix
org.jboss.test.jca.test.BackgroundValidationUnitTestCase.testDeployedBackgroundValidationFailure
</li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5770">JBAS-5770</a>
] fix 3
org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase
failures </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5772">JBAS-5772</a>
]
org.jboss.test.cluster.test/FamilyClusterInfoUnitTestCase(Default-TCP)/testSynchronization
</li> </ul> <h2>Patch</h2> <ul> <li>
[ <a href="https://jira.jboss.org/jira/browse/JBAS-4478">JBAS-4478</a>
] ignore local ant options when building </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5073">JBAS-5073</a>
] fix build authenticated proxy (there seems to have been a cut and
paste error at some point) </li> <li> [ <a href="https://jira.jboss.org/jira/browse/JBAS-5527">JBAS-5527</a>
] jboss_4_0.dtd should include support for
SingletonStatelessSessionInstancePool </li> </ul> <hr>
<h3>JBossAS-4.2.2.GA</h3>
<h2>Feature Request</h2> <ul> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4093">JBAS-4093</a>
] Example XA datasource configuration for Sybase </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4465">JBAS-4465</a>
] Rename hsqldb-jdbc-state-service.xml to jdbc-state-service.xml </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4479">JBAS-4479</a>
] It'd be nice for listThreadDump() to return a timestamp as well </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4490">JBAS-4490</a>
] Update and document all HA Failover features for the jca datasources </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4595">JBAS-4595</a>
] Inconclusive exception thrown by HttpNamingContextFactory </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4619">JBAS-4619</a>
] Add parseRoleNameFromDN option to LdapExtLoginModule </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4752">JBAS-4752</a>
] Session Expiration should also flush the JBoss Authentication Cache </li>
</ul> <h2>Bug</h2> <ul> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3379">JBAS-3379</a>
] BigIntegerTimerIdGenerator may create dupplicate timer IDs after
server crash </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4000">JBAS-4000</a>
] <endpoint-interceptors> should come before <activation-config>
in standardjboss.xml </activation-config></endpoint-interceptors></li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4053">JBAS-4053</a>
] EJB TimerService createTimer swallows underlying exception </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4404">JBAS-4404</a>
] Tests testJdbc and testControlFlags in
org.jboss.test.security.test.LoginModulesUnitTestCase may fail
incorrectly </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4422">JBAS-4422</a>
] org.jboss.test.util.test.TwiddleUnitTestCase can't connect to host </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4463">JBAS-4463</a>
] escape syntax </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4464">JBAS-4464</a>
] NPE on shutdown in jacorb connection layer </li> <li> [
<a href="http://jira.jboss.com/jira/browse/JBAS-4492">JBAS-4492</a>
] NullPointerException in org.jboss.util.propertyeditor.DateEditor
setValue(...) </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4525">JBAS-4525</a>
] JBossMQ WriteTask in UIL2 could block forever </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4528">JBAS-4528</a>
] jboss-ds-1.5.dtd is not up-to-date </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4536">JBAS-4536</a>
] Isolated classloading is incorrectly isolating java.* classes </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4540">JBAS-4540</a>
] Port 8083, HTTP request revealing installation directory </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4541">JBAS-4541</a>
] Authentication Service (AS) Context stored in CSIv2 encoded IORs
shouldn't indicate EstablishTrustInClient supported when
AUTH_METHOD_NONE </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4546">JBAS-4546</a>
] Fix RunAsSecurityInterceptor </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4555">JBAS-4555</a>
] Connection.close() taking 2 minutes in JBossMQ </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4559">JBAS-4559</a>
] JBossMQ security manager should have a dependency on the Jaas service
</li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4575">JBAS-4575</a>
] resourceadapter-class should be optional </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4593">JBAS-4593</a>
] Leak in org/jboss/mx/loading/UnifiedClassLoader3 </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4597">JBAS-4597</a>
] CacheInvalidator.areInvalid doesn't lock partitions </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4605">JBAS-4605</a>
] JSP compiler won't compile JDK 1.5 source </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4607">JBAS-4607</a>
] Transaction timeout is not raising a JMSException in the JBossMQ
Persistence manager or StateManager </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4611">JBAS-4611</a>
] HTTP Session Repl Cache configured with CacheLoader can cause slow AS
shutdowns </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4614">JBAS-4614</a>
] UnifiedInvokerHAProxy does not implement InvokerProxyHA </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4615">JBAS-4615</a>
] NamingContext caches stale Naming stub </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4622">JBAS-4622</a>
] Can't flush bad naming stub if no java.naming.provider.url specified </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4623">JBAS-4623</a>
] org.jboss.web.tomcat.service.session.JBossCacheCluster creates
MBeanServer with incorrent domain name </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4625">JBAS-4625</a>
] Connection leak if failure to setup connection in jms inbound
resource adapter </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4655">JBAS-4655</a>
] HandleImplIIOP not retrieving EJBObject correctly </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4659">JBAS-4659</a>
] jboss-4.2.1.GA.zip distribution doesn't include mail-ra.rar </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4667">JBAS-4667</a>
] Wrong logic in
CachedConnectionManager.getCloseConnectionSynchronization() </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4680">JBAS-4680</a>
] Update example for JBossWS Message TRACE in jboss-log4j.xml </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4681">JBAS-4681</a>
] Generated Corba stub throws BAD_OPERATION on toString() when not
connected to the ORB </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4691">JBAS-4691</a>
] JACC: Unchecked WebUserDataPermission(s) for excluded and transport
guarantee use cases </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4697">JBAS-4697</a>
] Use of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.toArray()
is not thread safe and should be replace with
java.util.concurrent.ConcurrentHashMap when using MQ transactions. </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4701">JBAS-4701</a>
] JaasSecurityDomain doesn't handle encrypted truststore passwords
properly </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4719">JBAS-4719</a>
] Implementations of Invoker should implement equals as an equality
check rather than relying on Object.equals, this is important for
cluster fail-over support </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4729">JBAS-4729</a>
] HARMIClient fails over on UnmarshalException </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4748">JBAS-4748</a>
] TransactionLocal.get() not sufficiently pluggable</li><li>[
<a href="http://jira.jboss.com/jira/browse/JBAS-4801">JBAS-4801</a>
] HomeHandleImplIIOP not using the HandleDelegate</li> </ul>
<h2>Task</h2> <ul> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3142">JBAS-3142</a>
] Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4092">JBAS-4092</a>
] Clean up the tests-webservice-ssl target </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4523">JBAS-4523</a>
] Verify installation of jbossws tools jars </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4526">JBAS-4526</a>
] JBossMQ UIL2 Read/Write Tasks should not be doing initialization </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4549">JBAS-4549</a>
] Track JBoss and thirdparty dependencies for JBossAS 4.2.2 </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4572">JBAS-4572</a>
] EJB 3 testsuite 100% </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4600">JBAS-4600</a>
] Rename JBossMQ variables from jboss-messaging to
jboss.messaging-mq.lib </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4601">JBAS-4601</a>
] Add example sybase-xa-ds.xml from the forums </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4638">JBAS-4638</a>
] fix org.jboss.test.web.test.ssl.SSLUnitTestCase caused by upgrade to
JBoss Web 2.0.1.CR6. </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4640">JBAS-4640</a>
] JmsActivation reconnection could start multiple threads </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4641">JBAS-4641</a>
] Move XMLJUnitMultipleResultFormatter from testsuite module to test
module </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4649">JBAS-4649</a>
] Upgrade to JBoss Cache 1.4.1.SP4 </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4695">JBAS-4695</a>
] Update the release notes for JBossAS 4.2.2.GA </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4696">JBAS-4696</a>
] Arrange community documents for 4.2.2.GA </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4698">JBAS-4698</a>
] Oswego Concurrent needs checking for bug fixes </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4699">JBAS-4699</a>
] JBossMQ should use XA_RMFAIL as the default XA error code </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4737">JBAS-4737</a>
] Include the CSIv2-patched JacORB </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4754">JBAS-4754</a>
] Do a full CTS1.4 run to check for regressions. </li> </ul>
<h2>Sub-task</h2> <ul> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3572">JBAS-3572</a>
] Fix the NPEs (better error handling) identified by the new
ServiceController testsuite </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3613">JBAS-3613</a>
] failing test in
org.jboss.test.iiop.test.ParameterPassingStressTestCase </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4152">JBAS-4152</a>
] Upgrade to hsql 1.8.0.8 causes
org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2
to fail </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4550">JBAS-4550</a>
] Upgrade to JBossWeb 2.0.1 (from 2.0.0.GA) </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4578">JBAS-4578</a>
] Upgrade jboss remoting to v2.2.2.SP1 (from v2.2.1.GA) </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4663">JBAS-4663</a>
] Replace JBossClusteredTestCase usage of RMIAdaptor </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4664">JBAS-4664</a>
] Move JBossClusteredTestCase to test module in Branch_4_2 </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4675">JBAS-4675</a>
] TransactionLocal cannot be locked when transaction is marked rollback
only </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4690">JBAS-4690</a>
] TransactionLocal tests are not run against the proper transaction
manager </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4694">JBAS-4694</a>
] Upgrade hsqldb to v1.8.0.8 (from 1.8.0.2) </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4715">JBAS-4715</a>
] Upgrade jboss common to 1.2.1.GA (from 1.2.0.GA) </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4723">JBAS-4723</a>
] Upgrade JGroups to 2.4.1.SP4 </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4731">JBAS-4731</a>
] Upgrade to JBoss Cache 1.4.1.SP5 </li> <li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4740">JBAS-4740</a>
] HARMIClient to give preference to wrapping NoSuchObjectException </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4759">JBAS-4759</a>
] Upgrade jboss transactions to 4.2.3.SP6 (from 4.2.3.SP5) </li>
<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4760">JBAS-4760</a>
] Upgrade to javassist 3.6.0.GA (from 3.5.0.GA) </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4761">JBAS-4761</a>
] Upgrade to JBoss AOP 1.5.6.GA (from 1.5.5.GA) </li> <li>
[ <a href="http://jira.jboss.com/jira/browse/JBAS-4767">JBAS-4767</a>
] Upgrade jbossws to 2.0.1 (from 1.2.1.GA) </li> </ul><!-- ======================================================= -->
<hr><h3>JBossAS-4.2.1.GA</h3>
<h2>Feature Request</h2>
<ul><li>[<a href="http://jira.jboss.com/jira/browse/JBAS-3158">JBAS-3158</a>]
- Need a way to detect collisions between JSF RI and JSF MyFaces</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4408">JBAS-4408</a>]
- LIMIT/OFFSET support in StoreManager2</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4454">JBAS-4454</a>]
- Upgrade to JSF RI 1.2_04 P02</li>
</ul><h2>Bug</h2>
<ul><li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4415">JBAS-4415</a>]
- ClusterFileTransferTestCase.testFarmDeploy fails to delete and copy</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4418">JBAS-4418</a>]
- run.bat should include %PATH% in java.library.path when bin/native
exists</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4425">JBAS-4425</a>]
- ConnectionFactoryTemplate.xsl incorrectly sets isSameRM-override-value</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4427">JBAS-4427</a>]
- Misnamed FK index name for CMP2</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4429">JBAS-4429</a>]
- Classloader leak to JBossTS ReaperThread</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4441">JBAS-4441</a>]
- Jboss hangs at startup with 100% CPU utilization</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4444">JBAS-4444</a>]
- The invoker-proxy-binding in the base container configuration is
ignored on sub-configurations.</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4461">JBAS-4461</a>]
- new InitialContext().rebind("x", null) throws NullPointerException</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4462">JBAS-4462</a>]
- mod() function not supported in SQL server 2005</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4473">JBAS-4473</a>]
- Java to IDL mapping erroneously treats a 'get' method as an attribute</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4481">JBAS-4481</a>]
- Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction
object bound to the thread</li>
</ul><h2>Task</h2>
<ul><li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4198">JBAS-4198</a>]
- Align EJB3 Security with JEE 1.4 Behavior</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4420">JBAS-4420</a>]
- Separate classloader leak tests from the 'all' tests</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4442">JBAS-4442</a>]
- Need to update exception handling code in HypersonicDatabase.java</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4467">JBAS-4467</a>]
- Document in the release notes a configuration for multiple 1PC with
JBossTS</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4480">JBAS-4480</a>]
- Upgrade hibernate to v3.2.4.SP1_CP01</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4482">JBAS-4482</a>]
- Add compatibility runs against 4.2.0.GA in Branch_4_2</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4503">JBAS-4503</a>]
- Update the release notes for JBossAS 4.2.1.GA</li>
<li>[<a href="http://jira.jboss.com/jira/browse/JBAS-4510">JBAS-4510</a>]
- Upgrade jboss remoting to v2.2.1.GA (from v2.2.0.SP4)</li>
</ul><!-- ======================================================= --><hr><h2><a name="Documentation">Documentation
and Help</a></h2>The&nbsp;<a href="http://www.jboss.org/jbossas/">JBossAS community
project</a> is hosted on jboss.org . Documentation and help
may
be obtained from the following locations.
<ul><li><a href="http://www.jboss.org/jbossas/docs">JBoss
AS Documentation</a></li>
<li><a href="http://wiki.jboss.org">JBoss Wiki</a></li>
<li><a href="http://jira.jboss.org/jira/browse/JBAS">JBoss
JIRA</a></li>
<li><a href="http://www.jboss.org/index.html?module=bb">JBoss
Forums</a></li>
</ul><!-- ======================================================= --><h2><a name="Licenses">Licenses</a></h2>
<p>JBoss Application Server&nbsp; is licensed under the <a href="lgpl.html">LGPL</a>,
as explained in the <a href="JBossORG-EULA.txt">JBoss End
User License Agreement</a>. The licence texts for JBoss and the
thirdparty components it uses may be found in the docs/licenses
directory of the distribution. <a href="docs/licenses">Browse
Licences</a>
</p><!-- ======================================================= --><h2><a name="About">About JBoss, a
division of RedHat</a></h2>
<p>JBoss, a division of <a href="http://www.redhat.com/jboss/">Red
Hat</a>, is in the business of providing
superior technical support to our customers. Our goal is to make
Professional Open Source&trade; the <b>SAFE CHOICE</b>
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 <a href="http://www.jboss.org/services/index">JBoss
Services</a> page for more information.</p>
</body></html>