Bug 781120 (SOA-3617) - JCA EndpointProxy must handle toString method
Summary: JCA EndpointProxy must handle toString method
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-3617
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Rick Wagner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 22:49 UTC by Rick Wagner
Modified: 2012-01-04 16:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-04 16:20:12 UTC
Type: Support Patch

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781119 1 None None None 2021-10-15 11:51:30 UTC
Red Hat Bugzilla 781121 0 high NEW JCA EndpointProxy must handle toString method 2021-10-15 11:51:43 UTC
Red Hat Issue Tracker SOA-3617 0 Major Closed JCA EndpointProxy must handle toString method 2013-01-13 21:00:37 UTC

Internal Links: 781119 781121

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.
Note You need to log in before you can comment on or make changes to this bug.