March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7810) ERROR [STDERR] javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: The EXECUTE permission was denied on the object 'xp_sqljdbc_xa_init', database 'master', schema 'dbo'..

by SANTIAGO SANCHEZ (JIRA)

ERROR [STDERR] javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: The EXECUTE permission was denied on the object 'xp_sqljdbc_xa_init', database 'master', schema 'dbo'.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-7810 URL: https://jira.jboss.org/jira/browse/JBAS-7810 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: SANTIAGO SANCHEZ ERROR [STDERR] javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: The EXECUTE permission was denied on the object 'xp_sqljdbc_xa_init', database 'master', schema 'dbo'.. 2010-03-15 10:50:57,468 ERROR [STDERR] at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Unknown Source) -- 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

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7577) Commented-out JmxOpsAccessControlFilter in jmx console's web.xml is invalid

by James Livingston (JIRA)

Commented-out JmxOpsAccessControlFilter in jmx console's web.xml is invalid --------------------------------------------------------------------------- Key: JBAS-7577 URL: https://jira.jboss.org/jira/browse/JBAS-7577 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA Reporter: James Livingston Assignee: Darran Lofthouse The JMX console's web.xml file contains a commented-out definition of JmxOpsAccessControlFilter, which can be used to give read-only access to some users. The xml parser in 5 onward is stricter than it was in 4, and complains that the <description> element if the <init-param>s aren't expected if you just uncomment the section. The <description> elements need to be moved to before the <param-name> elements. -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7812) Add method to create unconnected sockets to DomainSocketFactory

by Marcus Moyses (JIRA)

Add method to create unconnected sockets to DomainSocketFactory --------------------------------------------------------------- Key: JBAS-7812 URL: https://jira.jboss.org/jira/browse/JBAS-7812 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA Reporter: Marcus Moyses Assignee: Marcus Moyses Priority: Minor Fix For: JBossAS-6.0.0.M3 Need to add method for creating unconnected sockets to DomainSocketFactory so this socket factory can also be used with Remoting code. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7078) Create SSLSocketFactory that uses a JaasSecurityDomain

by Marcus Moyses (JIRA)

Create SSLSocketFactory that uses a JaasSecurityDomain ------------------------------------------------------ Key: JBAS-7078 URL: https://jira.jboss.org/jira/browse/JBAS-7078 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: JBossAS-5.2.0.Beta1 We need a SSLSocketFactory with a default constructor and a static getDefault method that sets up SSL using a JaasSecurityDomain mbean so it can be used for LDAPS, Remoting, etc. The name of the security domain must be set as a system property. -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2045) Allow singleton container to introduce new metadata bridges for concurrency management

by jaikiran pai (JIRA)

Allow singleton container to introduce new metadata bridges for concurrency management -------------------------------------------------------------------------------------- Key: EJBTHREE-2045 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2045 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.6 Currently the metadata bridges are setup within the BeanContainer (BeanContainer.initialize). This makes it impossible to add new metadata bridges (ex: for singleton container concurrency management). Instead of hardcoding the metadata bridges within the BeanContainer, it would be more flexible to allow the EJBContainer to return the AnnotationRepositoryToMetadata with appropriate metadata bridges setup. This way the common metadata bridge setup can be done within EJBContainer and any additional metadata bridges can then be setup through overridden method in individual containers. The BeanContainer while initializing the advisor can then just ask the EJBContainer for the AnnotationRepositoryToMetadata. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JASSIST-104) Proxy cache fails to guard against circular references which inhibits GC of classloaders

by Andrew Dinn (JIRA)

Proxy cache fails to guard against circular references which inhibits GC of classloaders ---------------------------------------------------------------------------------------- Key: JASSIST-104 URL: https://jira.jboss.org/jira/browse/JASSIST-104 Project: Javassist Issue Type: Bug Affects Versions: 3.11.0.GA Reporter: Andrew Dinn Assignee: Andrew Dinn The proxy cache employs a two level map to retain details of created proxies. The primary map is a WeakHashMap which associates classloaders with all proxies created using that classloader. The WeakHashMap is intended to ensure that references to proxies are dropped when a classloader is unloaded. The secondary maps appearing as values in the primary map are just plain hashmaps. These are used to lookup details of a proxy using a name constructed from the names of its superclass and the interfaces it implements. The target of the secondary map is a CacheKey object which stores the munged name, a weak reference to the proxy class, the method filter and the current default handler for instances of the proxy class. Any such proxy class will, of course, reference its classloader, the very same loader used as the WeakHashMap key for the secondary map in which the CacheKey instance resides. A WeakReference to the proxy class breask the reference cycle, ensuring that the WeakHashMap entry can be cleared when all other references to the classloader have been dropped. Unfortunately, this is not enough. Cachekey contains two other fields, handler and filter, which are instances of interfaces MethodHandler and MethodFilter. The values in these fields are supplied by a client application when the proxy is created. In normal use the proxy factory will locate the proxy class in the client application's classloader. In most cases this will be the same classloader that defines the classes used to provide the implementations of MethodHandler and MethodFilter used to populate the handler and filter fields. So, the secondary map must not employ a direct reference to the objects in these fields because this may result in a cyclic reference to the classloader and thereby inhibit GC. There is actually an extra detail in play here which affects any proposed solution. The secondary map key is not actually the munged name. Instead the CacheKey instance is used as both key and value. This is because the equals method for CacheKey checks that the munged name, filter and handler are all equal. Incorporating the filter and handler into the equality check allows caching of proxies for the same class using different filters and handlers. Unfortunately, this is unsafe. The handler field is meant to be updateable by the client after creation of the proxy i.e. after entering it in the cache. Changing this without removing and reinserting the entry risks the integrity of subsequent hash table lookup, replace and remove operations. For example, it is quite easy to end up with two 'equal' entries in the hashtable. A solution would be to employ a WeakHashMap for each secondary map, use the munged name as key and employ a class similar to the current CacheKey as the target of the map with the difference that it contains a list of proxy/handler/filter triples in place of the current 3 individual references. This simplifies the lookup (no special equals or hashcode needed) and also minimises the number of weak references (1 per super/interface set). This will also simplify duplicate detection and elimination when the handler is updated. -- 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

14 years, 10 months

1
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2043) Use proxy component in nointerface implementation

by jaikiran pai (JIRA)

Use proxy component in nointerface implementation ------------------------------------------------- Key: EJBTHREE-2043 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2043 Project: EJB 3.0 Issue Type: Task Components: nointerface Reporter: jaikiran pai Assignee: jaikiran pai Currently nointerface-impl module has its own javassist based proxy factory. This proxy factory has nothing specific to nointerface view and hence shouldn't be residing here. The proxy component created in EJBTHREE-2012 is the right place for this factory. nointerface view should start using the javassist based proxy factory which resides here http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/proxy/tru... -- 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

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1210) Review and clean up locking & states in Remote classes

by David Lloyd (JIRA)

Review and clean up locking & states in Remote classes ------------------------------------------------------ Key: JBREM-1210 URL: https://jira.jboss.org/jira/browse/JBREM-1210 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.CR1 Inbound/OutboundRequest/Client/Stream etc. have an internal state, usually reflected by a nested State enum. Make sure the state is updated whenever an event occurs which changes state; make sure the state is checked at the start of each operation to ensure that unexpected events don't jam up the works; double-check that all synchronized usages are proper. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7558) Upgrade jboss-javaee to 6.0.0.Alpha1

by Shelly McGowan (JIRA)

Upgrade jboss-javaee to 6.0.0.Alpha1 ------------------------------------ Key: JBAS-7558 URL: https://jira.jboss.org/jira/browse/JBAS-7558 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan -- 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

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-7809) Integrate VFS 3.0.0.CR4

by John Bailey (JIRA)

Integrate VFS 3.0.0.CR4 ----------------------- Key: JBAS-7809 URL: https://jira.jboss.org/jira/browse/JBAS-7809 Project: JBoss Application Server Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M2 Reporter: John Bailey Assignee: John Bailey Fix For: JBossAS-6.0.0.M3 -- 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

14 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010