[
http://jira.jboss.com/jira/browse/JBMESSAGING-742?page=all ]
Clebert Suconic updated JBMESSAGING-742:
----------------------------------------
Patch Instructions:
PATCH NAME:
JBMESSAGING-742
PRODUCT NAME:
JBoss Messaging
VERSION:
1.0.1.SP2
SHORT DESCRIPTION:
This Patch will fix the reference to JMSDestination from Messages after a queue is
restarted or redeployed, as well fixes introduced by Remoting Alpha4
LONG DESCRIPTION:
Prior to this fix, when a queue was restarted, you would get a null reference on
message.getJMSDestination when receiving a message.
MANUAL INSTALL INSTRUCTIONS:
Replace jboss-messaging.jar and jboss-remoting.jar under jboss-messaging.sar
Also replace eventual usages of jboss-messaging-client.jar.
COMPATIBILITY:
This patch is compatible with 1.0.1.SP2. No issues were introduced by this patch.
CREATOR:
Clebert Suconic
DATE:
Jan, 11th 2007
Update of JBossRemoting to Alpha4 and JBMESSAGING-741
-----------------------------------------------------
Key: JBMESSAGING-742
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-742
Project: JBoss Messaging
Issue Type: Support Patch
Affects Versions: 1.0.1.SP2
Reporter: Clebert Suconic
Fix For: 1.0.2.CR1, 1.0.1.SP2, 1.0.2.GA
Attachments: jboss-messaging-client.jar, jboss-messaging.jar, jboss-remoting.jar
PATCH NAME:
JBMESSAGING-742
PRODUCT NAME:
JBoss Messaging
VERSION:
1.0.1.SP2
SHORT DESCRIPTION:
This Patch will fix the reference to JMSDestination from Messages after a queue
is restarted or redeployed, as well fixes introduced by Remoting Alpha4
LONG DESCRIPTION:
Prior to this fix, when a queue was restarted, you would get a null reference on
message.getJMSDestination when receiving a message.
MANUAL INSTALL INSTRUCTIONS:
Replace jboss-messaging.jar and jboss-remoting.jar under jboss-messaging.sar
Also replace eventual usages of jboss-messaging-client.jar.
COMPATIBILITY:
This patch is compatible with 1.0.1.SP2. No issues were introduced by this
patch.
CREATOR:
Clebert Suconic
DATE:
Jan, 11th 2007
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira