March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1178) GroupRequest: don't send target member list with each request

by Bela Ban (JIRA)

GroupRequest: don't send target member list with each request ------------------------------------------------------------- Key: JGRP-1178 URL: https://jira.jboss.org/jira/browse/JGRP-1178 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.10 Currently, if we invoke an RPC (RpcDispatcher) or a sync group message (MessageDispatcher), we always send the target membership list with the request. The reason is that a member receiving a group request can drop it if it is not in the target list. However, for group requests, usually all of the members are in the target list anyway, and responses sent from members not in the list would get dropped anyway, as the GroupRequest itself keeps track of members from which responses are supposed to be received. For large clusters, the overhead of shipping the target list is too big, e.g. for 100 nodes, the cost of 100 addresses (UUIDs) is roughly 2000 bytes ! SOLUTION: drop the target membership list -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-454) Database Attribute Locator

by Anil Saldhana (JIRA)

Database Attribute Locator -------------------------- Key: SECURITY-454 URL: https://jira.jboss.org/jira/browse/SECURITY-454 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: jbossxacml_2.0.5.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: jbossxacml_2.0.5.CR2 Create an Attribute Locator that uses the Database to retrieve the attributes. -- 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

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-485) XACML Build: remove jaxb2 and stax dependencies

by Anil Saldhana (JIRA)

XACML Build: remove jaxb2 and stax dependencies ----------------------------------------------- Key: SECURITY-485 URL: https://jira.jboss.org/jira/browse/SECURITY-485 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: jbossxacml_2.0.5.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: jbossxacml_2.0.5.CR2 -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBVFS-154) Provide VirtualFile.getStreamURL()

by Thomas Diesler (JIRA)

Provide VirtualFile.getStreamURL() ---------------------------------- Key: JBVFS-154 URL: https://jira.jboss.org/jira/browse/JBVFS-154 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: John Bailey The OSGi third party integration needs to be able to reliably read the bundle bytes from an URL OSGi decouples the location of a bundle (an opaque string) from the actual source of the bundle bytes http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html#i... A remote management agent (i.e. my osgi testsuite) uses an URL to the bundle bytes. The OSGi VFS abstraction therefore provides VirtualFile.getStreamURL() http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/dis... It works such that the VF is automatically mounted and copied to a zip archive, which is then the source of that stream URL. Please consider to provide this functionality at VFS level. http://fisheye.jboss.org/browse/JBossOSGi/projects/vfs/trunk/vfs30/src/ma... http://fisheye.jboss.org/browse/JBossOSGi/projects/vfs/trunk/vfs30/src/ma... -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2831) Allow run-as identity propagation across servers with configurable trust

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2831?page=com.atlassian.jira.plug... ] Anil Saldhana commented on JBAS-2831: ------------------------------------- http://community.jboss.org/wiki/SAMLEJBIntegrationwithPicketLinkSTS > Allow run-as identity propagation across servers with configurable trust > ------------------------------------------------------------------------ > > Key: JBAS-2831 > URL: https://jira.jboss.org/jira/browse/JBAS-2831 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.4RC1 > Reporter: Scott M Stark > Assignee: Anil Saldhana > Fix For: JBossAS-6.0.0.M3 > > > Look to provide propagation of the run-as identity across server calls with control over how the target server trusts this call is correct. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-773) AOPTestDelegate.tearDown() should call super.tearDown()

by Flavia Rainone (JIRA)

AOPTestDelegate.tearDown() should call super.tearDown() ------------------------------------------------------- Key: JBAOP-773 URL: https://jira.jboss.org/jira/browse/JBAOP-773 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.2.0.GA Currently, the missing call is commented with a TODO: //TODO Figure out cause of security exception when making this call // super.tearDown(); If this call is uncommented, we get a securityException telling that System.setSecurityManager cannot be invoked (see JBoss Forum Reference for more details). -- 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

16 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7861) user-type-mapped types are not working in ejbql aggregate functions

by Alexey Loubyansky (JIRA)

user-type-mapped types are not working in ejbql aggregate functions ------------------------------------------------------------------- Key: JBAS-7861 URL: https://jira.jboss.org/jira/browse/JBAS-7861 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-6.0.0.M2 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossAS-6.0.0.M3 While these types can be used as query parameters, in the order by clause, etc they can't be used in, e.g., MIN or MAX functions (a CCE will be thrown from a result set reader). -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2461) Optional metadata can be assigned to verifier components

by Toni Rikkola (JIRA)

Optional metadata can be assigned to verifier components -------------------------------------------------------- Key: JBRULES-2461 URL: https://jira.jboss.org/jira/browse/JBRULES-2461 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Toni Rikkola Assignee: Toni Rikkola For example Guvnor metadata can be added to rule component. Metadata contains a map of the data and the path to the component that it is related to. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7667) java.lang.IllegalAccessException: Failed to find connection exception in multithreaded environment

by Smita Nimbalkar (JIRA)

java.lang.IllegalAccessException: Failed to find connection exception in multithreaded environment -------------------------------------------------------------------------------------------------- Key: JBAS-7667 URL: https://jira.jboss.org/jira/browse/JBAS-7667 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: JBoss Version: jboss-5.1.0.GA, OS: Linux (2.6.18-164.el5), Architecture: amd64 64bit, JVM: Java HotSpot(TM) 64-Bit Server VM (14.0-b16, mixed mode) Reporter: Smita Nimbalkar I have a method which takes java.sql.Connection from connection pool do some operation on DB and then close connection (i.e. return to the pool). There are multiple threads which are executing this method. Every time I execute this in multithreaded environment I get java.lang.IllegalAccessException: Failed to find connection exception on line connection.prepareStatement(query) of my class. But this issue goes away if I synchronize (on class object) code block which closes DB connection. Following is a exception trace: Caused by: java.lang.IllegalAccessException: Failed to find connection: 2365173 at org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.invoke(WrapperDataSourceService.java:212) at sun.reflect.GeneratedMethodAccessor283.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) at sun.reflect.GeneratedMethodAccessor282.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) ... 15 more -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1175) Replace System.out.println with logging

by Martin Zdila (JIRA)

Replace System.out.println with logging --------------------------------------- Key: JGRP-1175 URL: https://jira.jboss.org/jira/browse/JGRP-1175 Project: JGroups Issue Type: Feature Request Affects Versions: 2.9 Reporter: Martin Zdila Assignee: Bela Ban Please replace outstanding System.out.println-s with org.jgroups.logging.Log logging-s. For example in org/jgroups/protocols/pbcast/GMS.java line 912. -- 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

16 years, 4 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 March 2010