[jboss-cvs] JBossAS SVN: r83098 - projects/docs/enterprise/4.3.4/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jan 19 23:06:28 EST 2009
Author: irooskov at redhat.com
Date: 2009-01-19 23:06:28 -0500 (Mon, 19 Jan 2009)
New Revision: 83098
Modified:
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated with new JIRAs
Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-20 03:18:46 UTC (rev 83097)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-20 04:06:28 UTC (rev 83098)
@@ -42,8 +42,80 @@
JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application Platform 4.3 and will now provide a complete implementation of JAX-WS.
</para>
</section>
-
</section>
+ <section id="Component_Versions">
+ <title>Component Versions</title>
+ <para>
+ This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ JBoss Application Server 4.3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate 3.2.4.SP1.CP07
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Annotations 3.2.1.CP04
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Entity Manager 2.2.1.CP05
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JAF 1.2_10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Cache 1.4.1.SP11
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss JAXR 1.2.0.SP2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Messaging 1.4.0.SP3-CP05
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Remoting 2.2.2.SP11
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web 2.0.0-6.CP09
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JGroups 2.4.5
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JSF 1.2_10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Xalan 2.7.0.patch02
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section id="Installation_Notes">
<title>Installation and Migration Notes</title>
<para>
@@ -292,74 +364,54 @@
</listitem>
<listitem>
<para>
-
+ Client connection parameters were not passed to the JBoss Remoting layer, forcing Remoting to use default values instead of user configured values. In order to use the correct values, <filename>JMSRemotingConnection.java</filename> has been updated so that the <methodname>Client.addConnectionListener</methodname> method is used with <varname>listener</varname> and <varname>serverLocator.gerParameters()</varname> as parameters.
</para>
</listitem>
<listitem>
<para>
-
+ Messages which are sheduled for delivery in the future were not being removed correctly when the <methodname>removeAllMessages()</methodname> method was being called, causing the messages to bre requeued as soon as the application server or queue is restarted. <filename>ChannelSupport.java</filename> has been updated to import the <filename>TimeoutExt</filename> library in order to cast the timeout value to <filename>TimeoutExt</filename> in order to obtain the reference value via the <methodname>getTimeoutTarget()</methodname> method. With this new reference value information, the sheduled messages can be correctly removed from the queue.
</para>
</listitem>
<listitem>
<para>
-
+ There was an occurance where a user may deploy a clustered queue in a single node instead of in all the nodes and the failover process would not work because of this. When this occurred an <exceptionname>IllegalStateException</exceptionname> would be generated, however this was not considered enough of a prominent warning about not deploying clustered queues correctly. <filename>MessagingPostOffice.java</filename> has now been updated to log a warning which outlies that clustered destinations must be deployed on all nodes of a cluster, instead of generating an <exceptionname>IllegalStateException</exceptionname>.
</para>
</listitem>
<listitem>
<para>
-
+ The <classname>ClientAOPStackLoader</classname>, <classname>SecurityAspect.check()</classname> and <classname>ServerConnectionFactoryEndpoint</classname> needed to be able to optain TCL within a privileged block, otherwise an <exceptionname>AccessControlException</exceptionname> is produced. To fix this bug, the <methodname>setTCL</methodname>, <methodname>getTCL</methodname> and other TCL methods have been set within security blocks; this prevents access denied exceptions from <classname>ClientAOPStackLoader</classname>, <classname>SecurityAspect.check()</classname> and <classname>ServerConnectionFactoryEndpoint</classname>.
</para>
</listitem>
<listitem>
<para>
-
+ The logging of actions within JBoss Messaging did not include the logging of messages when they are moved to the expiry or dead letter queues as this was only logged at trace level. In order to add this enhanced level of logging, the <filename>ClientConsumer.java</filename> file has been updated to log warning messages and debug information pertaining to the move of messages to the expiry or dead letter queues; <filename>ServerSessionEndpoint.java</filename> has also been updated in the same mannor.
</para>
</listitem>
<listitem>
<para>
-
+ There was an error when a message was received under a XA tx and the JBoss Messaging XAResource is prepared but not committed, a message could be received by another consumer in another transaction while the first is still in progress. The correct behaviour is for JBoss Messaging to hold the message until the associated transaction is committed or rolled back, enabling duplication of message deliveries to be avoided. In the <filename>Delivery.java</filename> file, messages are now marked with a boolean value detailing if they are for delivery with a XA transaction and if this transaction is prepared and <filename>SimpleDelivery.java</filename> now implements this new information.
</para>
</listitem>
<listitem>
<para>
-
+ The <methodname>shutdownNow()</methodname> method was not synchronized and may cause a <exceptionname>NoSuchElementException</exceptionname> during runtime as a result. A synchronization block has been placed around the <methodname>shutdownNow()</methodname> code within <filename>OrderedExecutorFactory.java</filename>.
</para>
</listitem>
<listitem>
<para>
-
+ There was an issue with the <classname>org.jboss.jms.server.messagecounter.MessageCounter</classname> class not being serializable as it caused an <exceptionname>UndeclaredThrowableException</exceptionname>. <filename>MessageCounter.java</filename> has been updated to now import and implement the <literal>Serializable</literal> library and be given a <varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms.server.messagecounter.MessageCounter</classname> class to be serializable.
</para>
</listitem>
<listitem>
<para>
-
+ When the methods <methodname>unregisterSucker()</methodname> or <methodname>registerSucker()</methodname> was called a <exceptionname>ConcurrentModificationException</exceptionname> would be generated by the time the <literal>HashSet</literal> containing the <literal>suckers</literal> was iterated. The issue would present itself on clusters with a magnitude of nodes (for instance it appeared on a 8 node cluster but not a 4 node cluster). This bug was corrected by creating an iterator that used a private set of <literal>suckers</literal> for iteration through the <literal>HashSet</literal> of <literal>suckers</literal> in order to avoid the exception.
</para>
</listitem>
<listitem>
<para>
-
+ The bridge within JBoss Messaging would only retry connection creation to a remote destination after startup and if the remote provider was not available at startup, the bridge would fail to start. The <filename>Bridge.java</filename> and <filename>BridgeService.java</filename> files have undergone extensive modification and now the <literal>factory</literal> is set to the <literal>bridge</literal> which undertakes the lookup itself instead of looking up the destinations.
</para>
</listitem>
- <listitem>
- <para>
-
- </para>
- </listitem>
- <listitem>
- <para>
-
- </para>
- </listitem>
- <listitem>
- <para>
-
- </para>
- </listitem>
- <listitem>
- <para>
-
- </para>
- </listitem>
</itemizedlist>
</listitem>
</itemizedlist>
@@ -760,6 +812,11 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1521">JBPAPP-1521</ulink>: The <classname>CleanShutdownInterceptor</classname> class would log a <exceptionname>GenericClusteringException</exceptionname> when the container had failed to shut down correctly or failed to start correctly and because of this behavior the error message displayed because of the exception should be updated to indicate that it may be an issue with the container failing to start instead of only failing to shut down. In this latest EAP update, the error message has been updated to reflect both situations which may be the cause of the exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1458">JBPAPP-1458</ulink>: The JTA recovery configuration did not contain a line to enable JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though it is stated in the JBM user guide. This CP release modifies the <filename>build-distr.xml</filename> file to all <classname>XAResourceRecovery</classname> to be enabled for JTA recovery.
</para>
</listitem>
@@ -902,6 +959,16 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1224">JBPAPP-1224</ulink>: Attribute default values in EJB were not set when in use with <literal>@Service</literal> and <literal>XMBean XML</literal> . In order to correct this the behavior has been re-written to improve the mimicking of <classname>ServerCreator</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1170">JBPAPP-1170</ulink>: When the <methodname>getMBeanInfo</methodname> method is called within <classname>MBeanServerImpl</classname> and <classname>RawDynamicInvoker</classname>, the underlying exception to <exceptionname>NotCompliantMBeanException</exceptionname> is not expressed to the user. <filename>RawDynamicInvoker.java</filename> has now been updated to provide this useful information to the user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurance and so this logging measure has been removed in this EAP update.
</para>
</listitem>
More information about the jboss-cvs-commits
mailing list