April 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBAS-6717: ---------------------------------- Assignee: Farah Juma (was: Jesper Pedersen) > AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6717 > URL: https://jira.jboss.org/jira/browse/JBAS-6717 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ProfileService > Environment: JBoss Branch_5_x r85739, embjopr r209 > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections. > For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections: > Sub Pool Statistics: > Sub Pool Count: 1 > ------------------------------------------------------ > Track By Transaction: true > Available Connections Count: 12 > Max Connections In Use Count:10 > Connections Destroyed Count:0 > **Connections In Use Count:10** > Total Block Time:0 > Average Block Time For Sub Pool:0 > Maximum Wait Time For Sub Pool:0 > Total Timed Out:0 > The value of "Connections In Use Count" should be 8 in this case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-418) Access MC bean remotely in a type safe manner

by Galder Zamarreño (JIRA)

Access MC bean remotely in a type safe manner --------------------------------------------- Key: JBMICROCONT-418 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-418 Project: JBoss Microcontainer Issue Type: Feature Request Components: AOP Reporter: Galder Zamarreño Provide a mechanism to access an MC bean remotely in a type safe manner. Currently, the only way to access an MC bean remotely is to add a @JMX annotation to it and use the RMIAdaptor method explained in http://www.jboss.org/community/docs/DOC-9901 to access the bean. Another possibility is to bind the MC bean to JNDI via @JNDI annotation but looking up the bean effectively serializes the bean and sends it back to the client. Any invocations on the bean are local to client. One solution would be to either enhance @JNDI annotation or add an MC remote annotation that indicates the JNDI name and the remote proxy class so that MC creates a remote proxy for the bean and binds the proxy itself in JNDI. Clients would then be able to look up the proxy and use it to call the MC remotely in a type safe manner. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-5941) NullPointerException in ClusteredSession

by Radoslav Husar (JIRA)

NullPointerException in ClusteredSession ---------------------------------------- Key: JBAS-5941 URL: https://jira.jboss.org/jira/browse/JBAS-5941 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.CR2 Environment: perf01 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: JBossAS-5.0.0.GA During SOAK (failover, session replication, passivation disabled) testing, after 90 minutes JBoss logs: [JBoss] 11:24:29,329 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing [JBoss] java.lang.NullPointerException [JBoss] at org.jboss.web.tomcat.service.session.ClusteredSession.update(ClusteredSession.java:1097) [JBoss] at org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.update(SessionBasedClusteredSession.java:154) [JBoss] at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.JBossCacheService.loadSession(JBossCacheService.java:344) [JBoss] at org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1432) [JBoss] at org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:491) [JBoss] at org.apache.catalina.connector.Request.isRequestedSessionIdValid(Request.java:2160) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.parseSessionCookiesId(CoyoteAdapter.java:626) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:551) [JBoss] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:322) [JBoss] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) [JBoss] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384) [JBoss] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) [JBoss] at java.lang.Thread.run(Thread.java:619) Hudson build: http://hudson.qa.jboss.com/hudson/job/as5-soak/44/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-6038) Examine use of SessionReplicationContext start/finishCacheActivity

by Brian Stansberry (JIRA)

Examine use of SessionReplicationContext start/finishCacheActivity ------------------------------------------------------------------ Key: JBAS-6038 URL: https://jira.jboss.org/jira/browse/JBAS-6038 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.1.CR1 I don't believe the calls to SessionReplicationContext.startCacheActivity and finishCacheActivity are necessary any longer; confirm this and remove if so. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-6733) Avoid re-reading expired sessions from distributed cache

by Brian Stansberry (JIRA)

Avoid re-reading expired sessions from distributed cache -------------------------------------------------------- Key: JBAS-6733 URL: https://jira.jboss.org/jira/browse/JBAS-6733 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.1.0.CR1 Add logic such that if we don't find a session locally, only check the distributed cache if we haven't previously handled this session id on this request. If we handled it previously but it's no longer local, that means it's been invalidated. If we request an invalidated session from the distributed cache, it will be missing from the local cache but may still exist on other nodes (i.e. if the invalidation hasn't replicated yet because we are running in a tx or with async repl). With buddy replication, asking the local cache for the session will cause the out-of-date session from the other nodes to be gravitated, thus resuscitating the session. Previously releases had logic to deal with this, but only covered requests for the session that come before the code returns from ClusteredSessionValve. Such calls can happen after that, in particular StandardHostValve makes such a call. Fix is to store info on invalidated sessions in a thread local, as was done previously, but to defer clearing the thread local until the Session.recycle method rather than doing it in the ClusteredSessionValve. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1797) remove bandwidth monitoring in SF config for EJB3

by Radoslav Husar (JIRA)

remove bandwidth monitoring in SF config for EJB3 ------------------------------------------------- Key: EJBTHREE-1797 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1797 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1564) add other configurations to hudson+create hudson tasks

by Radoslav Husar (JIRA)

add other configurations to hudson+create hudson tasks ------------------------------------------------------ Key: EJBTHREE-1564 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1564 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTEST-8) add a stop task option to silently ignore shutdown errors

by Aleksandar Kostadinov (JIRA)

add a stop task option to silently ignore shutdown errors --------------------------------------------------------- Key: JBTEST-8 URL: https://jira.jboss.org/jira/browse/JBTEST-8 Project: JBoss Test Issue Type: Feature Request Affects Versions: 1.1.2.GA Reporter: Aleksandar Kostadinov Assignee: Shelly McGowan Fix For: 1.1.3.GA It could be useful to have a stop task option to silently ignore shutdown errors. For example when we know we screwed up a server config with some test and want server manager to kill its process and not complain anyhow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1230) Client failover support if one node of a cluster is cleanly shut down.

by Phillip Thurmond (JIRA)

Client failover support if one node of a cluster is cleanly shut down. ---------------------------------------------------------------------- Key: JBMESSAGING-1230 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1230 Project: JBoss Messaging Issue Type: Feature Request Reporter: Phillip Thurmond Assigned To: Tim Fox Fix For: 1.4.0.SP3.CP01 If one node of a cluster fails in someway, the client will attempt to failover transparently. However, if one node is shutdown cleanly, the client will not automatically failover to another node in the cluster. This functionality would be very useful for "rolling upgrades" where a portion of the cluster is left up while the other nodes are being updated. -- 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

17 years, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-6734) Hot changes not updated in VFS server/tmp directory

by Jeff Wexler (JIRA)

Hot changes not updated in VFS server/tmp directory --------------------------------------------------- Key: JBAS-6734 URL: https://jira.jboss.org/jira/browse/JBAS-6734 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: JBossAS-5.0.1.GA Environment: JBossAS 5.0.1.GA, Windows Server 2003, localhost:8080, seam 2.1.2.GA, Eclipse 3.4.2 with JbossTools 3.0.0.GA, PostgreSQL 8.3 Reporter: Jeff Wexler Assignee: Ales Justin Priority: Critical Create a new seam project as an ear (or war) with Dynamic Seam 2.1. deployed to the default server of JBossAS. Verify Welcome to Seam! message. Change home.xhtml such that message is now Welcome to Seam_Modified1! and save. Wait a number of seconds. Verify that change updated in home.xhtml in the default server of JBossAS. Refresh project/home.seam and you still get Welcome to Seam! rather than Welcome to Seam_Modified1! Check again after an hour and still the old message. Does not seem to update the tmp directory with the changed version unless you touch application.xml or redeploy the whole project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
2
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 April 2009