]
Galder Zamarreño resolved ISPN-1621.
------------------------------------
Fix Version/s: (was: 5.1.0.CR2)
Resolution: Duplicate Issue
SharedResourceMisuseDetector warning
------------------------------------
Key: ISPN-1621
URL:
https://issues.jboss.org/browse/ISPN-1621
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.0.CR1
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Priority: Minor
This warning message can be seen when starting EDG
{code}
node1:
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.
node2:
09:07:45,381 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector]
(HotRodServerMaster-2 ([id: 0x35612600, /10.16.90.107: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.
node3:
09:07:45,526 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector]
(HotRodServerMaster-2 ([id: 0x4263f6ea, /10.16.90.108: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.
node4:
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.
{code}
EDG build:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-...
huson job with the issue:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-PERF/job/edg...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: