[overlord-issues] [JBoss JIRA] (RTGOV-319) Integration with application server thread-pool

[RH Bugzilla Integration (JIRA)]

     [ https://issues.jboss.org/browse/RTGOV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated RTGOV-319:
------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1032935

    
> Integration with application server thread-pool
> -----------------------------------------------
>
>                 Key: RTGOV-319
>                 URL: https://issues.jboss.org/browse/RTGOV-319
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>          Components: Activity Collector
>    Affects Versions: 1.0.0.M3
>         Environment: RHEL 6.4, Fuse Service Works 6.0.0 Beta, OpenJDK 1.7u45
>            Reporter: Jochen Cordes
>            Assignee: Gary Brown
>            Priority: Minor
>              Labels: JBoss, RTGov, threads
>
> Description of problem:
> It looks like the RTGov threads are un-managed, i.e. not managed by JBoss EAP.
> Below you can find an example for a thread
> thread which seems not be
> integrated with the JBoss EAP thead-pool:
> "Thread-130" daemon prio=10 tid=0x89171400 nid=0x3c52 waiting on
> condition [0x8269d000]
>     java.lang.Thread.State: WAITING (parking)
>          at sun.misc.Unsafe.park(Native Method)
>          - parking to wait for  <0xaabee058> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>          at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
>          at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
>          at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:322)
>          at
> org.overlord.rtgov.activity.collector.activity.server.ActivityServerLogger$1.run(ActivityServerLogger.java:97)
>          at java.lang.Thread.run(Thread.java:662)
> Version-Release number of selected component (if applicable):
> 6.0.0 Beta
> How reproducible:
> Always
> Steps to Reproduce:
> 1. Startup FSW
> 2. Activate services
> 3. Do a threaddump
> Actual results:
> Threads are not managed by the JBoss EAP thread-pool
> Expected results:
> Threads should be managed by the JBoss EAP thread-pool.
> Additional info:

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira