Bug 781051 (SOA-3535)
| Summary: | EPR cached on first use of partner link, which makes modifying the EPR part way through a session impossible | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Gary Brown <gary.pi4tech> |
| Component: | riftsaw | Assignee: | Nobody <nobody> |
| Status: | CLOSED UPSTREAM | QA Contact: | Marek Baluch <mbaluch> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.0.ER6 | CC: | jpechane, ldimaggi |
| Target Milestone: | ER1 | ||
| Target Release: | 5.3.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3535 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Once the WS Dispatch had been created for a service, it is reused for subsequent requests. However, even if a different endpoint reference was associated with a partner link, the endpoint reference previously initialized would be reused. In order to fix this issue, the software has been modified so that the dispatcher is now created for each external invocation. As a result, if an endpoint reference is assigned to a partner link, then it will now call that endpoint as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:14:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gary Brown
2011-10-31 15:58:48 UTC
Link: Added: This issue is related to RIFTSAW-458 Link: Added: This issue is related to SOA-3549 This issue has been fixed as part of https://bugzilla.redhat.com/show_bug.cgi?id=807577. The fix has been applied to the 2.3.x branch and will be in the next build.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: Once WS Dispatch had been created for service, it was reused for subsequent requests
Consequence: Regardless of whether a different endpoint reference was associated to a partner link, it would reuse the endpoint reference previously initialized
Fix: The dispatcher is now created for each external invocation
Result: If an endpoint reference is assigned to a partner link, then it will call that endpoint as expected
Confirmed that the dispatcher is re-created. Hi Marek Tom C found a performance issue related to this fix, so I'm currently testing out a change that hopefully addresses that problem. Should I create a new bugzilla, or should we just set the status of this bugzilla to retest on the next build? Regards Gary Hi Gary I think a new BZ will be me more appropriate sice the performance issue is another problem. Btw. could you email me your test process for this issue? I have some problems with mine :(. It's unable to retrieve the port for the assigned service reference. Thanks. Best regards Marek Hi Marek I'm testing in riftsaw (dynpartner quickstart with modified xalan.jar). The problem you are facing is probably the same as with bug 807577, which is awaiting an EAP patch that includes https://issues.jboss.org/browse/JBWS-2937 as far as I am aware. Jim Ma was also going to investigate why cxf was also having problems, but not sure how that is going. Regards Gary Thanks for helping us by writing the draft release note, Gary. Much appreciated.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,4 +1 @@
-Cause: Once WS Dispatch had been created for service, it was reused for subsequent requests
+Once the WS Dispatch had been created for a service, it is reused for subsequent requests. However, even if a different endpoint reference was associated with a partner link, the endpoint reference previously initialized would be reused. In order to fix this issue, the software has been modified so that the dispatcher is now created for each external invocation. As a result, if an endpoint reference is assigned to a partner link, then it will now call that endpoint as expected.-Consequence: Regardless of whether a different endpoint reference was associated to a partner link, it would reuse the endpoint reference previously initialized
-Fix: The dispatcher is now created for each external invocation
-Result: If an endpoint reference is assigned to a partner link, then it will call that endpoint as expected
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |