January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-738) @SecurityDomain should throw Exception if "java:/jaas/..."

by Wolfgang Knauf (JIRA)

@SecurityDomain should throw Exception if "java:/jaas/..." ---------------------------------------------------------- Key: EJBTHREE-738 URL: http://jira.jboss.com/jira/browse/EJBTHREE-738 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Reporter: Wolfgang Knauf Priority: Minor Security Domains in J2EE 1.4 environment were always specified as "java:/jaas/MySecurityDomain", but the @SecurityDomain requires only "MySecurityDomain". To avoid this trapdoor a simple check "if (value.startsWith ("java:/jaas/") ) throw Exception" would probably avoid some errors in updating from EJB2.1 to EJB3. Same check makes sense for the annotation "<security-domain>" in jboss.xml. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-279) Move web page from SourceForge to labs.jboss.org

by Bela Ban (JIRA)

Move web page from SourceForge to labs.jboss.org ------------------------------------------------ Key: JGRP-279 URL: http://jira.jboss.com/jira/browse/JGRP-279 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3624) <security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans

by David Green (JIRA)

<security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3624 URL: http://jira.jboss.com/jira/browse/JBAS-3624 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.GA Reporter: David Green Assigned To: Bill Burke Specifying a <security-domain> in the jboss-app.xml incorrectly sets the @SecurityDomain on EJB3 session beans. In the jboss-app.xml the security domain is specified as follows: <jboss-app> <security-domain>java:/jaas/hch</security-domain> </jboss-app> In Ejb3DescriptorHandler the security-domain is copied directly into the SecurityDomainImpl instance as "java:/jaas/hch", however the @SecurityDomain annotation should be populated with the value "hch" (without the leading "java:/jaas/" prefix). This causes the EJB3 session bean authentication to behave unexpectedly, since the authentication for the bean reverts to the default domain instead of the specified one. The only way I've found to workaround this issue is to specify the @SecurityDomain individually on every session bean in the project. -- 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, 5 months

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-3997) getManagedConnection retries

by Adrian Brock (JIRA)

getManagedConnection retries ---------------------------- Key: JBAS-3997 URL: http://jira.jboss.com/jira/browse/JBAS-3997 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Assigned To: Weston Price We should add the ability to retry getManagedConnection() when there is a resource exception from the pool. This will allow the ConnectionManagers to be more tolerant of transient failures. I'd suggest two new attributes on the connection manager, with the suggested defaults: <allocate-retry>1</allocate-retry> <allocate-retry-wait-millis>5000</allocate-retry-wait-millis> I also think the connection manager needs a "shutdown" boolean (maintained by start/stop) i.e. so don't wait 5 seconds if we get a resource exception caused by the CM/Pool getting undeployed, e.g. at JBoss shutdown. This would turn into the following *untested* code in BaseConnectionManager2: protected ConnectionListener getManagedConnection(Transaction transaction, Subject subject, ConnectionRequestInfo cri) throws ResourceException { ResourceException failure = null; if (shutdown.get()) throw new ResourceException("The connection manager is shutdown " + jndiName); // First attempt try { return poolingStrategy.getConnection(transaction, subject, cri); } catch (ResourceException e) { failure = e; // Retry? for (int i = 0; i < allocationRetries; ++i) { if (shutdown.get()) throw new ResourceException("The connection manager is shutdown " + jndiName); try { if (allocationWait != 0) wait(allocationWait); return poolingStrategy.getConnection(transaction, subject, cri); } catch (ResourceException e1) { failure = e1; } catch (InterruptedException e1) { JBossResourceException.rethrowAsResourceException("getManagedConnection retry wait was interrupted " + jndiName, e1); } } } // If we get here all retries failed, throw the lastest failure throw failure; } -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3916) Update source code headers.

by Dimitris Andreadis (JIRA)

Update source code headers. --------------------------- Key: JBAS-3916 URL: http://jira.jboss.com/jira/browse/JBAS-3916 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta2 Update the source code headers, like it was done for Branch_4_0 in JBAS-3601 -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3928) Replace jmx-invoker-service.xml with jmx-remoting.sar

by Scott M Stark (JIRA)

Replace jmx-invoker-service.xml with jmx-remoting.sar ----------------------------------------------------- Key: JBAS-3928 URL: http://jira.jboss.com/jira/browse/JBAS-3928 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Remoting Reporter: Scott M Stark Assigned To: Scott M Stark We need to complete the org.jboss.mx.remoting.service.JMXConnectorServerService jmx invoker to be at least as complete as the RMIAdaptor so we can replace the jmx-invoker-service.xml with the jmx-remoting.sar. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-439) Abiltity to change priority of messages in a queue/durable sub

by Tim Fox (JIRA)

Abiltity to change priority of messages in a queue/durable sub -------------------------------------------------------------- Key: JBMESSAGING-439 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-439 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.0.2 A "nice to have" would be to allow the priority of messages in a destination to be changed by an administrator - this should be available via the normal management interfaces. -- 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, 6 months

5
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-732) Improve message counter functionality

by Tim Fox (JIRA)

Improve message counter functionality ------------------------------------- Key: JBMESSAGING-732 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-732 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.2.1 MessageCounter functionality can be improved by returning counters and history as XML as well as HTML, or in some other "machine friendly" format. Also the history should be made "rolling", so only a moving window of data is retained to prevent a large buildup -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-856) Use Buddy Replication for clustered SFSBs

by Brian Stansberry (JIRA)

Use Buddy Replication for clustered SFSBs ----------------------------------------- Key: EJBTHREE-856 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC11 - FD Optimize the replicated SFSB cache for use with Buddy Replication. Basically means checking cache calls to ensure unwanted data gravitations do not occur. -- 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, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-3858) Update tc6-cluster.aop to match the current configuration

by Brian Stansberry (JIRA)

Update tc6-cluster.aop to match the current configuration --------------------------------------------------------- Key: JBAS-3858 URL: http://jira.jboss.com/jira/browse/JBAS-3858 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Ben Wang Fix For: JBossAS-5.0.0.Beta1 The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in tc6-cluster.aop. We need to sync up. We want to maintain support for the old Tomcat-specific interface markers as well. -- 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, 6 months

6
12
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 January 2007