February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4306) Invalid invoker mbean names in standardjboss.xml

by Scott M Stark (JIRA)

Invalid invoker mbean names in standardjboss.xml ------------------------------------------------ Key: JBAS-4306 URL: http://jira.jboss.com/jira/browse/JBAS-4306 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The following invoker-proxy-binding is useless in terms of defining the invoker-mbean such that it can be used as a ejb container dependency: <invoker-proxy-binding> <name>message-driven-bean</name> <invoker-mbean>default</invoker-mbean> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> <proxy-factory-config> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> <CreateJBossMQDestination>false</CreateJBossMQDestination>  <MinimumSize>1</MinimumSize> <MaximumSize>15</MaximumSize> <KeepAliveMillis>30000</KeepAliveMillis> <MaxMessages>1</MaxMessages> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> <DLQConfig> <DestinationQueue>queue/DLQ</DestinationQueue> <MaxTimesRedelivered>10</MaxTimesRedelivered> <TimeToLive>0</TimeToLive> </DLQConfig> </MDBConfig> </proxy-factory-config> </invoker-proxy-binding> Either there should be an mbean representing the state of the default invoker, or the mdb invoker config specified in another way such that dependencies can be configured. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBAS-3151) Convert HA-JNDI stubs to Remoting

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3151?page=all ] Dimitris Andreadis updated JBAS-3151: ------------------------------------- Fix Version/s: JBossAS-5.1.0.CR1 (was: JBossAS-5.0.0.Beta4) > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: JBAS-3151 > URL: http://jira.jboss.com/jira/browse/JBAS-3151 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assigned To: Ron Sigal > Fix For: JBossAS-5.1.0.CR1 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-424) Convert HA-JNDI stubs to Remoting

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-424?page=all ] Dimitris Andreadis updated JBREM-424: ------------------------------------- Assignee: Ron Sigal (was: Tom Elrod) > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: JBREM-424 > URL: http://jira.jboss.com/jira/browse/JBREM-424 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: External_issues > > -- 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, 3 months

1
0
0 / 0

[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

18 years, 3 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

18 years, 3 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

18 years, 3 months

2
2
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

18 years, 3 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

18 years, 3 months

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

18 years, 3 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

18 years, 3 months

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