Bug 778568 (SOA-1040) - Default JMS ReplyTo address can be based on the wrong uri
Summary: Default JMS ReplyTo address can be based on the wrong uri
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1040
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 CP02
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2 CP03
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-20 14:06 UTC by Kevin Conner
Modified: 2014-05-27 01:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-13 11:46:25 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778569 0 medium CLOSED Default JMS ReplyTo address can be based on the wrong uri 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1040 0 None None None Never

Internal Links: 778569

Description Kevin Conner 2008-11-20 14:06:35 UTC
Date of First Response: 2008-12-04 22:53:18
project_key: SOA

Platform issue for JBESB-2197

Comment 1 Kevin Conner 2008-11-20 14:08:12 UTC
Link: Added: This issue depends JBESB-2197


Comment 2 Kevin Conner 2008-11-20 14:19:36 UTC
Link: Added: This issue is related to SOA-1041


Comment 3 Dana Mison 2008-12-05 03:53:18 UTC
Regards Release Notes: I need a clarification of on how this behaves now

Comment 4 Kevin Conner 2008-12-05 11:32:19 UTC
Hiya Darrin.

Part of the information in the JMS ReplyTo address was being initialised using the wrong information.  While this information was never used in the underlying transport it was inconsistent and could give the impression that a message was destined for a queue on a different server instance.

While this had no functional impact, the information within the JMS ReplyTo address is now consistent.

Comment 5 Dana Mison 2008-12-08 00:27:38 UTC
Release Note: A currently unused part of the JMS ReplyTo address was being initialized with incorrect information.  This has been corrected.

Comment 6 Len DiMaggio 2009-01-12 23:08:30 UTC
Verified code change from corresponding JBESB fix is in SOA-P CP03 branch:

svn co https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/platform/soa_tags/SOA-4.2.0.CP3_2/
svn co https://svn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_2_1_GA_CP/

Fix JmsEPR address for replyto: JBESB-2197
branches/JBESB_4_2_1_GA_CP/product/rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java 23984 history download (+32 -7) diffs
branches/JBESB_4_2_1_GA_CP/product/rosetta/tests/src/org/jboss/soa/esb/addressing/eprs/JMSEprUnitTest.java 23984 history download (+50 -0) diffs 

[ldimaggi@ldimaggi 42_CP03_CR7_src]$ find . -name JMSEpr.java -ls
2654608   28 -rw-rw-r--   1 ldimaggi ldimaggi    24318 Jan 12 15:41 ./JBESB_4_2_1_GA_CP/product/rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java
8684663   28 -rw-rw-r--   1 ldimaggi ldimaggi    24318 Jan 12 15:14 ./SOA-4.2.0.CP3_2/product/rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java

[ldimaggi@ldimaggi 42_CP03_CR7_src]$ diff ./JBESB_4_2_1_GA_CP/product/rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java ./SOA-4.2.0.CP3_2/product/rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java



Comment 7 Kevin Conner 2009-01-13 11:46:24 UTC
Verified fix is present


Note You need to log in before you can comment on or make changes to this bug.