Bug 777938 (SOA-466)

Summary: org.jboss.soa.esb.actions.Notifier - NotifyQueues - fails if the queue to be notified has a listener defined
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, JBossESBAssignee: Len DiMaggio <ldimaggi>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 GA   
Target Milestone: ---   
Target Release: 4.2 CP01   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-466
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
/opt/GA/soa-4.2.0.GA.zip /opt/GA/standalone-soa-4.2.0.GA.zip
Last Closed: 2008-04-01 17:29:44 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
jboss-esb.xml
none
server.log none

Description Len DiMaggio 2008-03-14 23:59:57 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-03-16 16:46:11
project_key: SOA

org.jboss.soa.esb.actions.Notifier - NotifyQueues - fails if the queue to be notified has a listener defined

To recreate this issue - using the SOA-P GA notifications quickstart:

1) Replace the QS's jboss-esb.xml with the file attached to this JIRA.
2) ant deploy
3) ant run
4) Look in the log - this exception is raised:

ERROR [JmsComposer] Unsupported JMS message type: org.jboss.jms.message.TextMessageProxy

(server.log - for standalone server/default profile) is attached.
Comment 1 Len DiMaggio 2008-03-15 00:02:33 UTC 
Attachment: Added: jboss-esb.xml
Attachment: Added: server.log
Comment 2 Len DiMaggio 2008-03-15 00:04:56 UTC 
Link: Added: This issue is a dependency of JBQA-1399
Comment 3 Len DiMaggio 2008-03-15 00:06:13 UTC 
Link: Added: This issue is a dependency of JBESB-1606
Comment 4 Mark Little 2008-03-16 20:43:58 UTC 
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Comment 5 Mark Little 2008-03-16 20:46:11 UTC 
Not a bug so much as a restriction on the current architecture: Notifiers are for communication with ESB-unaware endpoints (think of them as the reciprocal of a gateway).
Comment 6 Len DiMaggio 2008-04-01 17:29:44 UTC 
Verified in CP01 that the programmers' guide includes:

Notifiers are the way in which success or error information may be propagated to ESB-unaware
endpoints. You should not use Notifiers for communicating with ESB-aware endpoints. This may
mean that you cannot have ESB-aware and ESB-unaware endpoints listening on the same
channel. Consider using Couriers or the ServiceInvoker within your Actions if you want to
communicate with ESB-aware endpoints.