Bug 768411 - SharedResourceMisuseDetector warning
Summary: SharedResourceMisuseDetector warning
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 6.0.0
Assignee: Tristan Tarrant
QA Contact: Michal Linhard
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-16 15:26 UTC by Michal Linhard
Modified: 2014-03-17 04:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-08 12:55:09 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-1611 0 Blocker Resolved Hotrod server memory leak after enable idle timeout 2015-08-17 16:14:56 UTC
Red Hat Issue Tracker ISPN-1621 0 Minor Resolved SharedResourceMisuseDetector warning 2015-08-17 16:14:56 UTC

Description Michal Linhard 2011-12-16 15:26:54 UTC 
This warning message can be seen when starting EDG

09:07:45,110 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (MemcachedServerMaster-2 ([id: 0x4d815146, /10.16.90.106:11222])) You are creating too many HashedWheelTimer instances.  HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.

09:07:48,125 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (HotRodServerMaster-2 ([id: 0x7d05e560, /10.16.90.109:11222])) You are creating too many HashedWheelTimer instances.  HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
Comment 1 Michal Linhard 2011-12-16 15:35:43 UTC 
EDG BUILD:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg-from-source/68/artifact/edg-srcbuild.zip
Comment 2 Michal Linhard 2012-03-05 17:11:31 UTC 
This can no longer be observed in JDG 6.0.0 ER2
Note You need to log in before you can comment on or make changes to this bug.