Privacy_bytestreamPatch_22.09.11.patch
[SPARK-1437] Bug in PrivacyManager that can break smack communication Created: 23/Sep/11 Updated: 28/Oct/20 Resolved: 23/Sep/11 |
|
| Status: | Closed |
| Project: | Spark |
| Components: | General |
| Affects versions: | 2.6.3 |
| Fix versions: | 2.7.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Tim Jentz | Assignee: | Tim Jentz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
Privacy_bytestreamPatch_22.09.11.patch
|
| Ignite Forum URL: | http://community.igniterealtime.org/message/216828#216828 |
| Description |
|
The PrivacyManager in Spark creates a new DiscoveryManager to check if privacy is supported. This new ServiceDiscoveryManager will, in addition to the standard Manager, reply on all disco#info requests. This results in the issue, that disco#info requests are replied twice. In some circumstances this will cause that Bytestream fails and IBB is choosen. I created a patch for Spark to make the PrivacyManager use the standard DiscoveryManager instead creating a new one. |
| Comments |
| Comment by Tim Jentz [ 23/Sep/11 ] |
|
I created a patch for Spark to make the PrivacyManager use the standard DiscoveryManager instead creating a new one. |
| Comment by Holger Bergunde [ 23/Sep/11 ] |
|
patched into trunk |