April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5395) Break Clustering Aspects out of AS

by Andrew Lee Rubinger (JIRA)

Break Clustering Aspects out of AS ---------------------------------- Key: JBAS-5395 URL: http://jira.jboss.com/jira/browse/JBAS-5395 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Brian Stansberry Priority: Blocker Fix For: JBossAS-5.0.0.CR1 Should be moved into jbossas/projects/aspects/cluster -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5442) AS ChannelFactory to never return MuxChannel

by Brian Stansberry (JIRA)

AS ChannelFactory to never return MuxChannel -------------------------------------------- Key: JBAS-5442 URL: http://jira.jboss.com/jira/browse/JBAS-5442 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Don't support MuxChannel at all from the AS ChannelFactory. If the stack for a given request doesn't have a singleton_name, create one and add 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5451) Unclean handling of JMX registrations by ChannelFactory

by Brian Stansberry (JIRA)

Unclean handling of JMX registrations by ChannelFactory ------------------------------------------------------- Key: JBAS-5451 URL: http://jira.jboss.com/jira/browse/JBAS-5451 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 First, only MuxChannels are registered. All channels should be registered. This will necessitate adding a ChannelListener to all channels so the factory gets a callback when the channel is closed, at which point it can be deregistered. Second, the AS ChannelFactory's destroy method delegates to org.jgroups.JChannelFactory, which in turn removes everything from JMX that's registered under the jboss.jgroups domain. That includes the ChannelFactory itself. This can cause problems if the pojo factory is destroyed before the JMX proxy to the factory. The deregistration needs to be more fine grained. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1082) jdbc.WrapperDataSource.getConnection is slow

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1082?page=all ] Clebert Suconic updated JBAS-1082: ---------------------------------- Assignee: Jesper Pedersen (was: Clebert Suconic) Transferring this issue to Jesper, since he is the JCA specialist > jdbc.WrapperDataSource.getConnection is slow > -------------------------------------------- > > Key: JBAS-1082 > URL: http://jira.jboss.com/jira/browse/JBAS-1082 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-3.2.6 Final > Reporter: Elias Ross > Assigned To: Jesper Pedersen > Priority: Minor > > SourceForge Submitter: genman . > I've been profiling JMS code. When a JMS message is > added to the server, the persistence manager locates an > appropriate DataSource. > Out of the time spent in > org.jboss.mq.Connection.sendToServer, about 28% of the > time is getting the database connection through > jdbc.WrapperDataSource.getConnection to do its work. > This is after the pool has been initialized, etc. (40% > is actual persistence, though most of it is the message > serialization.) > I suspect a lot of the work is calculating a hashCode > on the javax.security.auth.Subject. SubjectCriKey and > SubjectKey should have this value cached. Ideally, > when one is accessing the local DB, none of this auth > stuff should have to take place. Looking at the source > for Subject.java, the hash code is not kept. > BaseConnectionManager2.allocateConnection %CPU=27.949 > %Time=27.963 calls=411 > Allocations I've seen: > JBossManagedConnectionPool$SubjectActions > is created 3284 times (for 411 getConnection calls) > java.util.Properties (1642 times) > (Disclaimer: This was done through JBoss profiler, > which may or may not create real numbers. It does > look, though, that CX is pretty slow for some operations.) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-195) SecurityContext methods need to be secure with permissions

by Anil Saldhana (JIRA)

SecurityContext methods need to be secure with permissions ---------------------------------------------------------- Key: SECURITY-195 URL: http://jira.jboss.com/jira/browse/SECURITY-195 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2-BETA5 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA6 When running under a security manager, the security context methods need to check for security permissions to go ahead with the call. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Deleted: (JBTEST-2) t2

by Alex Pinkin (JIRA)

[ http://jira.jboss.com/jira/browse/JBTEST-2?page=all ] Alex Pinkin deleted JBTEST-2: ----------------------------- > t2 > -- > > Key: JBTEST-2 > URL: http://jira.jboss.com/jira/browse/JBTEST-2 > Project: JBoss Test > Issue Type: Task > Reporter: Alex Pinkin > Assigned To: Dimitris Andreadis > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JBTEST-3) t3

by Alex Pinkin (JIRA)

[ http://jira.jboss.com/jira/browse/JBTEST-3?page=all ] Alex Pinkin deleted JBTEST-3: ----------------------------- > t3 > -- > > Key: JBTEST-3 > URL: http://jira.jboss.com/jira/browse/JBTEST-3 > Project: JBoss Test > Issue Type: Task > Reporter: Alex Pinkin > Assigned To: Dimitris Andreadis > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBTEST-3) t3

by Alex Pinkin (JIRA)

t3 -- Key: JBTEST-3 URL: http://jira.jboss.com/jira/browse/JBTEST-3 Project: JBoss Test Issue Type: Task Reporter: Alex Pinkin Assigned To: Dimitris Andreadis -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBTEST-2) t1

by Alex Pinkin (JIRA)

t1 -- Key: JBTEST-2 URL: http://jira.jboss.com/jira/browse/JBTEST-2 Project: JBoss Test Issue Type: Task Reporter: Alex Pinkin Assigned To: Dimitris Andreadis -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBSER-101) Serialization detail messages should be logged at "TRACE" level

by David Lloyd (JIRA)

Serialization detail messages should be logged at "TRACE" level --------------------------------------------------------------- Key: JBSER-101 URL: http://jira.jboss.com/jira/browse/JBSER-101 Project: JBoss Serialization Issue Type: Feature Request Reporter: David Lloyd Assigned To: Clebert Suconic Priority: Trivial Fix For: 1.1.0 Beta According to http://wiki.jboss.org/wiki/Wiki.jsp?page=LoggingStandards, http://wiki.jboss.org/wiki/Wiki.jsp?page=Logging, etc., messages that are "per-request" should be logged at level TRACE rather than DEBUG. -- 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, 1 month

1
1
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 2008