May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5079) Add a stuck thread feature to the application server that scans for stuck threads

by Jay Howell (JIRA)

Add a stuck thread feature to the application server that scans for stuck threads --------------------------------------------------------------------------------- Key: JBAS-5079 URL: http://jira.jboss.com/jira/browse/JBAS-5079 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.2.GA Reporter: Jay Howell Many Other application servers have a stuck thread reaper that looks at threads and the times that they have been taking. If they take too long they are either logged as a warning or they are killed. This is a very dangerous safeguard, but it's a feature that does come in quite handy if a thread gets stuck on an object lock. We've seen some of these in support especially around the Jbosscache when customers misconfigure JbossCache with ejb3/hibernate. It also happens with customers do strange things with jms inside the app server. The configuration might be something like. StuckThreadInterval - interval at which the scanner should scan for stuck threads. Higher amounts will give more time before the event(log or inturrupt) is fired. -1 means it's disabled. StuckThreadNotification - class to be called if a thread gets stuck default would be org.jboss....StuckThreadLogger the default behavior should log the stuck thread. But we should also have another class that can be plugged in the StuckThreadNotification that inturrups the thread. Maybe we can call it org.jboss.....StuckThreadInturrupter Log should always log it, but with a configuration change, it should be able to inturrupt it. We've had multiple requests for this feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBCACHE-11) Memory based eviction policy

by Peter Kovgan (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-11?page=comments#action_12413646 ] Peter Kovgan commented on JBCACHE-11: ------------------------------------- Alexandre Russel hi! In general I agree on that. It's good idea. But, Why not start partly eviction in first point? (Not changing maxNodes) Then on second point start complete eviction + change MaxNodes(how much - parameter)? Peter. > Memory based eviction policy > ---------------------------- > > Key: JBCACHE-11 > URL: http://jira.jboss.com/jira/browse/JBCACHE-11 > Project: JBoss Cache > Issue Type: Feature Request > Components: Eviction > Reporter: Bela Ban > Assigned To: Mircea Markus > Fix For: 3.0.0 > > Attachments: memoryBaseEviction.txt > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > (maybe only in JDK 1.5, which has > triggers for low memory) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2037) Bug in the JBoss HTML adaptor.

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2037?page=all ] Dimitris Andreadis updated JBAS-2037: ------------------------------------- Component/s: Web/JMX Console (was: JMX) > Bug in the JBoss HTML adaptor. > ------------------------------ > > Key: JBAS-2037 > URL: http://jira.jboss.com/jira/browse/JBAS-2037 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web/JMX Console > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2 Final, JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1 > Reporter: jean deruelle > Assigned To: Amit Bhayani > > "The set of characters in a value is also limited. If > special characters may occur, it is recommended that the > value be quoted, using ObjectName.quote. If the value for a > given key is sometimes quoted, then it should always be > quoted. By default, if a value is a string (rather than a > number, say), then it should be quoted unless you are sure > that it will never contain special characters." quoted from > java management best practices (see > http://java.sun.com/products/JavaManagement/best-practices.html#mozTocId6... > in section ObjectNameSyntax) > When a JMX value is quoted, it causes problems to invoke methods through thr Jboss jmx web console : > So my feeling is that the problem comes from the jboss jmx > console jsp pages. > The thing is that the quotes in the jmx object name are not > encoded to the html format in the jsp pages and so the first > opening quote is interpreted as the final quote of the html > field. > Here is a quick fix for Jboss-3.2.6 : > Add the following lines to > %JBOSS_HOME%\server\all\deploy\jmx-console.war\inspectMBean.jsp > after line 141 > <%objectNameString=objectNameString.replaceAll("\"","""); > //objectNameString=URLEncoder.encode(objectNameString);%> > It was a quick fix to fit my needs but the > line should really be the one commented but in that case the > HtmlAdaptorServlet from Jboss cannot handle it correctly > because it doesn't do a URLDecoder.decode of the > objectNameString stored in the request parameter called "name". > But I might be wrong here in saying that it comes from > jboss, maybe I missed something along the way. > Can someone confirm this bug or help me out there ? > Thx > Best regards > Jean -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1323) The JMX Console should handle null values

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1323?page=all ] Dimitris Andreadis updated JBAS-1323: ------------------------------------- Component/s: Web/JMX Console (was: JMX) > The JMX Console should handle null values > ----------------------------------------- > > Key: JBAS-1323 > URL: http://jira.jboss.com/jira/browse/JBAS-1323 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web/JMX Console > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Scott M Stark > > At the moment it is not possible to call a MBean via the JMX Console and provide null parameters. > Please add a check box that indicates that the value should be null and handle it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3877) The JMX HtmlAdaptor does not display the exception message

by Lior Shamir (JIRA)

The JMX HtmlAdaptor does not display the exception message ---------------------------------------------------------- Key: JBAS-3877 URL: http://jira.jboss.com/jira/browse/JBAS-3877 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Lior Shamir Assigned To: Scott M Stark Priority: Minor In JBoss 3.2.x when exception occurred, the HtmlAdaptor display the exception message. In JBoss 4.0.x the HtmlAdaptor display only a generic error message. This is obviously a regression. Can you add the message back? Here is an example: 4.0.4: javax.servlet.ServletException: Failed to invoke operation org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:269) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause javax.management.MBeanException org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163) org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) org.jboss.mx.server.Invocation.invoke(Invocation.java:86) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258) org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 3.2.6: javax.servlet.ServletException: Failed to invoke operation org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:248) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) root cause MBeanException: com.koko.KOKOException: Invalid type Cause: com.koko.KOKOException: Invalid type org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:91) org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:64) org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) org.jboss.mx.server.Invocation.invoke(Invocation.java:82) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:236) org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:202) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:241) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5067) Enhance JCA Security Integration

by Anil Saldhana (JIRA)

Enhance JCA Security Integration -------------------------------- Key: JBAS-5067 URL: http://jira.jboss.com/jira/browse/JBAS-5067 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service, Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Adrian Brock Fix For: JBossAS-5.0.1.CR1 Some attention needs to be given to Adrian's rant/suggestions for the JCA security integration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-5539) ConnectionFactoryBuilder should have set/get SubjectFactory rather than get/SetSecurityManagement

by Anil Saldhana (JIRA)

ConnectionFactoryBuilder should have set/get SubjectFactory rather than get/SetSecurityManagement ------------------------------------------------------------------------------------------------- Key: JBAS-5539 URL: http://jira.jboss.com/jira/browse/JBAS-5539 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 Copy/paste issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4749) HTML object tag should be used instead of applet

by Sylvain Avril (JIRA)

HTML object tag should be used instead of applet ------------------------------------------------ Key: JBAS-4749 URL: http://jira.jboss.com/jira/browse/JBAS-4749 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.2.2.GA Reporter: Sylvain Avril Assigned To: Darran Lofthouse Priority: Minor The HTML applet tag is deprecated. It can lead to strange behavior. For exemple for my Windows PC, it try to use the 1.3.1 JVM instead of the 1.5.0 which is the default for applets. Some doc could be found here : http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_ta... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

3
3
0 / 0

[JBoss JIRA] Assigned: (JBAS-1832) Improving JBoss WebConsole's snapshots

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1832?page=all ] Clive Saldanha reassigned JBAS-1832: ------------------------------------ Assignee: Jon Prindiville (was: Clive Saldanha) > Improving JBoss WebConsole's snapshots > -------------------------------------- > > Key: JBAS-1832 > URL: http://jira.jboss.com/jira/browse/JBAS-1832 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.0 Final > Environment: Not relevant > Reporter: Mathieu Bourrier > Assigned To: Jon Prindiville > Priority: Minor > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The snapshots in the Webconsole cannot be started automatically on startup, as the Recording field isn't an attribute. > 2 classes need to be modified, and the changes are quite small. > Given topic describes changes to be made in order to manage it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2008) web console statistics view does not show properly in Firefox

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2008?page=all ] Clive Saldanha reassigned JBAS-2008: ------------------------------------ Assignee: Jon Prindiville (was: Clive Saldanha) > web console statistics view does not show properly in Firefox > ------------------------------------------------------------- > > Key: JBAS-2008 > URL: http://jira.jboss.com/jira/browse/JBAS-2008 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.2 Final > Environment: Firefox > Reporter: Kevin Barfield > Assigned To: Jon Prindiville > Priority: Minor > > The statistics view in the web console has a box though it when viewed through the Firefox browser. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2008