Bug 745906 (EDG-109) - JGroups getNumTimerTasks WARNING
Summary: JGroups getNumTimerTasks WARNING
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-109
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 11:49 UTC by Michal Linhard
Modified: 2014-03-17 04:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-03 15:39:20 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-109 0 None None None Never

Description Michal Linhard 2011-07-19 11:49:37 UTC
Workaround: Workaround Exists
Workaround Description: <transport ...>
  <property name="timer.num_threads">1</property>
</transport>
project_key: EDG

http://hudson.qa.jboss.com/hudson/view/EDG6/job/edg-60-stress-client-hotrod-size4/37/console-perf17/consoleText

{code}
07:42:39,535 WARNING [org.jgroups.protocols.UDP] (DiagnosticsHandler,default,perf17-37478) Could not retrieve value of attribute (method) getNumTimerTasks: java.lang.reflect.InvocationTargetException
[JBoss] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
[JBoss] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
[JBoss] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
[JBoss] 	at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
[JBoss] 	at org.jgroups.stack.Protocol.dumpStats(Protocol.java:272) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at org.jgroups.stack.ProtocolStack.dumpStats(ProtocolStack.java:310) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at org.jgroups.JChannel.dumpStats(JChannel.java:687) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at org.jgroups.JChannel$MyProbeHandler.handleProbe(JChannel.java:2099) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2165) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2137) [jgroups-2.12.1.Final.jar:]
[JBoss] 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
[JBoss] Caused by: java.lang.UnsupportedOperationException
[JBoss] 	at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.getExecutor(TimerSchedulerAdapter.java:168) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
[JBoss] 	at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.size(TimerSchedulerAdapter.java:153) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
[JBoss] 	at org.jgroups.protocols.TP.getNumTimerTasks(TP.java:714) [jgroups-2.12.1.Final.jar:]
[JBoss] 	... 11 more
{code}

Comment 1 Michal Linhard 2011-07-19 11:52:03 UTC
EDG6 Alpha1 SNAPSHOT rev67
infinispan 5.0.0-SNAPSHOT - last commit 265687277baee7d1c0ea4adb71c7e33d3f11774f  Mon Jul 18 20:05:25 2011 +0200
AS 7.1.0.Alpha1-SNAPSHOT - last commit 1eeb03a3fa0e795980a6ed96473df3ad0115902b Mon Jul 18 18:10:27 2011 +0100


Comment 3 Paul Ferraro 2011-07-19 16:40:47 UTC
Looks like a bug in the jgroups subsystem.  It looks like the threading subsystem starting returning "protected" decorators, which prevents the jgroups subsystem from accessing the underlying thread pool properties.  I'll post a workaround - basically configure the timer directly in jgroups.

Comment 4 Paul Ferraro 2011-07-19 16:43:06 UTC
Workaround Description: Added: <transport ...>
  <property name="timer.num_threads">1</property>
</transport>
Workaround: Added: [Workaround Exists]


Comment 5 Paul Ferraro 2011-07-20 01:35:55 UTC
Link: Added: This issue Cloned to JBPAPP-6863


Comment 6 Paul Ferraro 2011-07-20 01:37:35 UTC
Link: Added: This issue depends AS7-1344


Comment 7 Paul Ferraro 2011-07-20 01:37:45 UTC
Link: Removed: This issue Cloned to AS7-1344 


Comment 8 Galder Zamarreño 2011-08-03 07:26:31 UTC
Michal, we're waiting for 7.0.1 upgrade to fix this?

Comment 9 Michal Linhard 2011-08-03 15:39:20 UTC
this wasn't very critical. I used Paul's workaround but now it should be fixed. closing.

Comment 10 Galder Zamarreño 2011-08-04 10:15:40 UTC
Michal, you should update the resolution. Won't Fix is probably the best option.

Comment 11 Anne-Louise Tangring 2011-10-11 17:09:32 UTC
Docs QE Status: Removed: NEW 



Note You need to log in before you can comment on or make changes to this bug.