Bug 780010 (SOA-2370) - Unable to configure jms-message-filter as durable subscriber to a Topic
Summary: Unable to configure jms-message-filter as durable subscriber to a Topic
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2370
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 19:25 UTC by Toshiya Kobayashi
Modified: 2011-11-01 20:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-01 20:17:04 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779715 0 high CLOSED Unable to configure jms-message-filter as durable subscriber to a Topic 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2370 0 None None None Never

Internal Links: 779715

Description Toshiya Kobayashi 2010-10-01 19:25:56 UTC 
Affects: Release Notes
project_key: SOA

See linked SOA task
Comment 1 Kevin Conner 2010-10-01 19:26:16 UTC 
Link: Added: This issue is related to SOA-2077
Comment 2 Darran Lofthouse 2010-10-04 10:16:05 UTC 
Toshiya - Do not set the fix version when opening Jira issues, leave the fix version unassigned so it can be picked up to be triaged.

Looking at the linked Jira issue this is already resolved for 5.1 and is a duplicate?  Or is there further work for this issue?
Comment 3 Kevin Conner 2010-10-04 10:27:28 UTC 
Toshiya didn't create this issue, I did.  The linked issue had both affects versions and was split in to two.

This had already been triaged for 5 and may be invalid for 4.3, but that is a decision for another day.
Comment 5 Kevin Conner 2010-10-04 11:05:08 UTC 
Help Desk Ticket Reference: Removed: https://enterprise.redhat.com/issue-tracker/849363
Note You need to log in before you can comment on or make changes to this bug.