Bug 745865 (EDG-14)
| Summary: | ServerWorker thread naming problem | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Michal Linhard <mlinhard> |
| Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | VERIFIED --- | QA Contact: | Nobody <nobody> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0.0 | CC: | galder.zamarreno, jdg-bugs, nobody |
| Target Milestone: | ER8 | Keywords: | Reopened |
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/EDG-14 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If a server is used for both Hot Rod and Memcached, it is not possible to distinguish between the worker threads for each protocol because they are all named "MemcachedServerWorker". This does not affect the functionality of the server.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-03 08:40:54 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
Michal Linhard
2011-03-14 13:09:51 UTC
I'm looking into this and I don't think the issue is to do with static or singleton properties. The NettyTransport class that would in theory correspond to the Hot Rod server is receiving threadNamePrefix="Memcached" in the constructor. Actually no, forget what I said, it is indeed a limitation in Netty. The second time it sets the delimiter, it overrides it with a delimiter associated with the Memcached transport, and so has the properties of the NettyTransport class associated with Memcached in spite of trying to generate a thread name for Hot Rod. Trying to see if there's a workaround... Link: Added: This issue depends NETTY-336 There's little else I can do at this point. Maybe I could get rid of the prefix but we might need it at some point, and the prefix is still valid for standalone use cases. So, I'm leaving this open and keeping it unassigned. What would be the desired behavior? Do you want Netty not to rename threads at all? Hmm Trustin, the problem is explained in NETTY-336 and you have fixed it now? Not sure I understand your question. Michal, I'm closing this, marking as deferred and putting a note for the release notes. We should maybe have a JIRA of future upgrades that are needed to get around issues like this or JBPAPP-6928. Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: Due to a limitation of one of the libraries used within EDG, thread naming of Memcached and Hot Rod endpoints might appear mixed up. In fact, the Hot Rod endpoint executions might appear to be executed by a thread whose named starts with 'Memcached'. This no impact though on the functionality EDG provides. Link: Added: This issue relates to JBPAPP-6957 Release Notes Docs Status: Removed: Not Yet Documented Release Notes Text: Removed: Due to a limitation of one of the libraries used within EDG, thread naming of Memcached and Hot Rod endpoints might appear mixed up. In fact, the Hot Rod endpoint executions might appear to be executed by a thread whose named starts with 'Memcached'. This no impact though on the functionality EDG provides. This is still an issue in JDG 6.0.0.ER1, not very hot one, but wrong thread names might be confusing to users ... Still issue in JDG 6.0.0.ER5 Still issue in JDG 6.0.0.ER6
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:
When a server is being used both for HotRod and Memcached, it will not be possible to distinguish the worker threads dedicated to each protocol since they will all be named "MemcachedServerWorker". This does not affect functionality.
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 +1 @@
-When a server is being used both for HotRod and Memcached, it will not be possible to distinguish the worker threads dedicated to each protocol since they will all be named "MemcachedServerWorker". This does not affect functionality.+If a server is used for both Hot Rod and Memcached, it is not possible to distinguish between the worker threads for each protocol because they are all named "MemcachedServerWorker". This does not affect the functionality of the server.
Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-1954 Michal, the issue is fixed but in Netty 4.x and not in the 3.2.x branch that we're using. No Netty 4.x versions have been released yet. Netty 3.3 does not fix this. Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-1954 I've emailed Trustin to double check, but I'm pretty sure this is only in 4.x and will take a while to get released. Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-1954 Trustin replied and indeed indicated that it only went into Netty 4.x which has had no releases yet. So, this won't happen for a while. This bug is nominated for inclusion in the JDG 6 GA Release Notes as a known issue. Setting needinfo for assignee to clarify or ACK technical note information about this issue and any possible workarounds. The technical note is still valid. There are no workarounds. ttarrant will add jira links as appropriate. Verified. Memcached and Hotrod worker threads have correct names in JDG 6.1.0.ER8 (8.1) |