[JBoss JIRA] (RTGOV-319) Integration with application server thread-pool
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RTGOV-319?page=com.atlassian.jira.plugin.... ]
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
10 years, 7 months
[JBoss JIRA] (RTGOV-319) Integration with application server thread-pool
by Jochen Cordes (JIRA)
Jochen Cordes created RTGOV-319:
-----------------------------------
Summary: 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
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
10 years, 7 months
[JBoss JIRA] (RTGOV-318) Add index to Context value and type field
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-318?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-318:
----------------------------------
Wait for hibernate 4.3 which should support JPA 2.1, which has support for defining indexes. Tried using the hibernate specific @Index, but couldn't get it to work on the Context table, which is an Embeddable rather than top level Table.
> Add index to Context value and type field
> -----------------------------------------
>
> Key: RTGOV-318
> URL: https://issues.jboss.org/browse/RTGOV-318
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
> An index is required on the Context type and value fields, as otherwise building a call trace becomes very slow due to scanning complete db table.
--
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
10 years, 7 months
[JBoss JIRA] (RTGOV-318) Add index to Context value and type field
by Gary Brown (JIRA)
Gary Brown created RTGOV-318:
--------------------------------
Summary: Add index to Context value and type field
Key: RTGOV-318
URL: https://issues.jboss.org/browse/RTGOV-318
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
An index is required on the Context type and value fields, as otherwise building a call trace becomes very slow due to scanning complete db table.
--
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
10 years, 7 months
[JBoss JIRA] (GADGETS-71) Occasional ConcurrentModificationException when starting up gadget web UI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/GADGETS-71?page=com.atlassian.jira.plugin... ]
Work on GADGETS-71 stopped by Eric Wittmann.
> Occasional ConcurrentModificationException when starting up gadget web UI
> -------------------------------------------------------------------------
>
> Key: GADGETS-71
> URL: https://issues.jboss.org/browse/GADGETS-71
> Project: Gadget Server and Gadgets
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Eric Wittmann
>
> This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs.
> {noformat}
> 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException
> at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07]
> at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07]
> at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:]
> at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:]
> at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> {noformat}
--
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
10 years, 7 months