February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-684) PING: allow for multiple GossipRouters to get pinged for initial membership discovery

by Bela Ban (JIRA)

PING: allow for multiple GossipRouters to get pinged for initial membership discovery ------------------------------------------------------------------------------------- Key: JGRP-684 URL: http://jira.jboss.com/jira/browse/JGRP-684 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6.2, 2.7 Add a flag ping_hosts, example: ping_hosts="192.168.2.5[12000],192.168.2.5[12001] -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-682) TUNNEL: reconnector thread is not started in certain scenarios

by Bela Ban (JIRA)

TUNNEL: reconnector thread is not started in certain scenarios -------------------------------------------------------------- Key: JGRP-682 URL: http://jira.jboss.com/jira/browse/JGRP-682 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.6.2, 2.7 This is in TUNNEL.StubConnectionListener: public void connectionStatusChange(int newState) { if(currentState == RouterStub.STATUS_CONNECTED && newState == RouterStub.STATUS_CONNECTION_LOST){ startReconnecting(); } else if(currentState != RouterStub.STATUS_CONNECTED && newState == RouterStub.STATUS_CONNECTED){ stopReconnecting(); Thread receiver = new Thread(Util.getGlobalThreadGroup(), new TunnelReceiver(), "TUNNEL receiver"); receiver.setDaemon(true); receiver.start(); } currentState = newState; } # 1: why do we need 3 states ? Why not just CONNECTED and DISCONNECTED ? #2: the logic above is incorrect, as it doesn't handle *all* state transitions ! For example, if we go from DISCONNECTED to CONNECTION_LOST, we will *not* start the reconnector thread ! We can reproduce #2 through the following steps: - Start node A (channel with with tunnel.xml) (GossipRouter is not running) - Start node B (start GossipRouter then channel with tunnel.xml) ==> The nodes will not merge. Reason: there is never a CONNECT from node A, only REGISTER calls. If there is no CONNECT, we never set the GossipRouter$AddressEntry.output field and therefore can never send anything ! -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4756) Fix org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase failures

by Brian Stansberry (JIRA)

Fix org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase failures ----------------------------------------------------------------------------- Key: JBAS-4756 URL: http://jira.jboss.com/jira/browse/JBAS-4756 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 Seeing intermittent failures with all the tests in org.jboss.test.cluster.multicfg.web.test.ScopedAttrBasedTestCase when running with a TCP config -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-116) Move SecurityConstants to SPI

by Anil Saldhana (JIRA)

Move SecurityConstants to SPI ----------------------------- Key: SECURITY-116 URL: http://jira.jboss.com/jira/browse/SECURITY-116 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Move it to SPI for usage in JBoss AS5. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-119) Role Mapping Providers should use RoleGroup

by Anil Saldhana (JIRA)

Role Mapping Providers should use RoleGroup ------------------------------------------- Key: SECURITY-119 URL: http://jira.jboss.com/jira/browse/SECURITY-119 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 The RoleMapping Providers currently use Group. They need to use RoleGroup. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-115) Move SecurityContextAssociation to SPI

by Anil Saldhana (JIRA)

Move SecurityContextAssociation to SPI -------------------------------------- Key: SECURITY-115 URL: http://jira.jboss.com/jira/browse/SECURITY-115 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Move it to SPI for usage in JBoss AS5. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-108) Replace Roles from Data Map in Security Context with RoleGroup in SubjectInfo

by Anil Saldhana (JIRA)

Replace Roles from Data Map in Security Context with RoleGroup in SubjectInfo ----------------------------------------------------------------------------- Key: SECURITY-108 URL: http://jira.jboss.com/jira/browse/SECURITY-108 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Identity, JBossSX, Security SPI Affects Versions: 2.0.2-BETA3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA4 Migrate the previous roles storage in the Security Context data map into a RoleGroup construct in SubjectInfo. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-121) Remove PrincipalToRoleMappingProvider

by Anil Saldhana (JIRA)

Remove PrincipalToRoleMappingProvider ------------------------------------- Key: SECURITY-121 URL: http://jira.jboss.com/jira/browse/SECURITY-121 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 No usage. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-120) Remove PolicyContextIdRoleMappingProvider

by Anil Saldhana (JIRA)

Remove PolicyContextIdRoleMappingProvider ----------------------------------------- Key: SECURITY-120 URL: http://jira.jboss.com/jira/browse/SECURITY-120 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 No usage. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1748) hot deploying JMX invoker service fails

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1748?page=all ] Dimitris Andreadis updated JBAS-1748: ------------------------------------- Fix Version/s: JBossAS-5.1.0.CR1 (was: JBossAS-5.0.0.Beta4) > hot deploying JMX invoker service fails > --------------------------------------- > > Key: JBAS-1748 > URL: http://jira.jboss.com/jira/browse/JBAS-1748 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.2 Final > Reporter: Norman Richards > Assigned To: Vicky Kak > Priority: Minor > Fix For: JBossAS-5.1.0.CR1 > > > jmx-invoker-service.xml cannot be hot deployed. Trying to hot deploy it causes a failure when redeploying the web console. After this failure, I the JMX invoker cannot be contacted. Here's the resulting web console error: > 22:49:04,904 ERROR [WebModule] Starting failed jboss.web.deployment:id=-1500951031,war=web-console.war > java.lang.NullPointerException > at org.jboss.web.WebModule.startModule(WebModule.java:67) > at org.jboss.web.WebModule.startService(WebModule.java:46) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy8.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194) -- 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2008