Bug 781120 (SOA-3617)

Summary: JCA EndpointProxy must handle toString method
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Rick Wagner <rwagner>
Component: unspecifiedAssignee: Rick Wagner <rwagner>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0 GA   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3617
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-04 16:20:12 UTC Type: Support Patch
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Rick Wagner 2011-11-21 22:49:32 UTC 
Support Case Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007pEhb&sfdc.override=1
project_key: SOA

Some JCA providers will call toString on the EndpointProxy, for example WSMQ, leading to the following exception

(WorkManager(2)-7) java.lang.IllegalStateException: Multiple message delivery between before and after delivery is not allowed for message endpoint category: write service: updatejms jca adapter: wmq.jmsra.rar
(WorkManager(2)-7) 	at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:231)
(WorkManager(2)-7) 	at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:150)
(WorkManager(2)-7) 	at $Proxy227.toString(Unknown Source)
(WorkManager(2)-7) 	at com.ibm.msg.client.commonservices.trace.TableBuilder.append(TableBuilder.java:236)

We should handle this within the proxy and, in addition, include hashcode and equals
Comment 1 Rick Wagner 2011-11-21 22:49:32 UTC 
Link: Added: This issue Cloned from SOA-3616
Comment 2 Rick Wagner 2011-11-21 22:51:44 UTC 
Link: Added: This issue Cloned to SOA-3618
Comment 3 Rick Wagner 2011-11-21 22:53:31 UTC 
Link: Removed: This issue Cloned to SOA-3618
Comment 4 Rick Wagner 2011-11-21 23:05:13 UTC 
Link: Added: This issue Cloned to SOA-3619
Comment 5 Douglas Palmer 2012-01-04 15:51:28 UTC 
This was fixed in ESB 4.10.CP2; SOA-P 5.2.0 shipped with ESB 4.11.
Comment 6 Rick Wagner 2012-01-04 16:20:12 UTC 
Unneeded.  SOA-P 5.2 shipped with the fix in place.