May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1203) TCPGOSSIP: discovery fails when physical address is not yet known by coordinator

by Bela Ban (JIRA)

TCPGOSSIP: discovery fails when physical address is not yet known by coordinator -------------------------------------------------------------------------------- Key: JGRP-1203 URL: https://jira.jboss.org/jira/browse/JGRP-1203 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.10 In TCPGOSSIP, the GossipRouter stores logical address (UUID), logical name (e.g. "A") and physical address (e.g. 192.168.1.5:7800) of each member. When a member P runs the discovery in TCPGOSSIP, it fetches all of this information, so it can send messages to all members in its cluster. However, when member Q, who hasn't yet run a discovery (e.g. as part of MERGE2), needs to send a message back to P, since P's physical address won't be known yet, this will fail. A concrete uses case is this: - A has joined the cluster, became the coordinator as only member and registered with the GossipRouter - B runs the discovery protocol, fetches information about A from GossipRouter in a first phase - In a second phase, B sends a GET_MBRS_REQ to A, this works as B knows A's physical address - A receives B's request and wants to send a GET_MBRS_RSP back to B - However, as A didn't include its own physical address, A won't be able to send a message back to B ! Therefore B doesn't join the cluster, and will only later be merged with A ! - Only after the periodic merge kicks in, which runs a discovery on A, will A get B's physical address and will be able to talk to B ! ==> SOLUTION: simple, B sends it metadata (physical address, logical name) *with* the GET_MBRS_REQ to A, so A will have B's physical address to send a message back to B. This is actually done in the other discovery protocols as well, e.g. TCPPING or PING... -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6917) Add a apache-log4j-extra functions In Jboss-logging

by Marcio AntÃ£o (JIRA)

Add a apache-log4j-extra functions In Jboss-logging ---------------------------------------------------- Key: JBAS-6917 URL: https://jira.jboss.org/jira/browse/JBAS-6917 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: software platform Reporter: Marcio AntÃ£o Jboss-logging use a apache-log4j-extra . This extras functions is very utils Example : Compress GZ (Log Rotation with Compact logs) Tks -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Commented: (JBAS-2633) JSR-196: JASPI Framework for ClientSide pluggability

by Davide Malpassini (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2633?page=com.atlassian.jira.plug... ] Davide Malpassini commented on JBAS-2633: ----------------------------------------- But the JSR-196 is mandatory for J2EE6? > JSR-196: JASPI Framework for ClientSide pluggability > ---------------------------------------------------- > > Key: JBAS-2633 > URL: https://jira.jboss.org/jira/browse/JBAS-2633 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-5.0.1.GA > Reporter: Anil Saldhana > Assignee: Anil Saldhana > Fix For: Unscheduled > > > JASPI (JSR-196) allows pluggability of external security authentication providers on both the client side as well as the server side. This issue is to cover client side pluggability of external authentication providers. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-506) Release JBossSecurity 2.0.3.SP4

by Anil Saldhana (JIRA)

Release JBossSecurity 2.0.3.SP4 ------------------------------- Key: SECURITY-506 URL: https://jira.jboss.org/jira/browse/SECURITY-506 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Release Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: JBossSecurity_2.0.4.SP4 -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-503) Fix NPE when TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl

by Marcus Moyses (JIRA)

Fix NPE when TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl ------------------------------------------------------------------------------------------------ Key: SECURITY-503 URL: https://jira.jboss.org/jira/browse/SECURITY-503 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta4, JBossSecurity_2.0.4.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5 When TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl (or generic org.jboss.security package) a NPE is thrown if a login module option is empty, e.g. <module-option name="anOption"/> This causes login to fail when TRACE level logging is enabled. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-505) jbosssx-sources.jar is incorrect

by Anil Saldhana (JIRA)

jbosssx-sources.jar is incorrect -------------------------------- Key: SECURITY-505 URL: https://jira.jboss.org/jira/browse/SECURITY-505 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: JBossSecurity_2.0.4.SP4 The Maven build is messing up the sources jar. the directory structure is coming out with java/org/jboss/security when it should be org/jboss/security -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7434) org.jboss.test.cluster.defaultcfg.clusteredentity

by Shelly McGowan (JIRA)

org.jboss.test.cluster.defaultcfg.clusteredentity ------------------------------------------------- Key: JBAS-7434 URL: https://jira.jboss.org/jira/browse/JBAS-7434 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: 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

13 years, 11 months

5
17
0 / 0

[JBoss JIRA] Created: (JBBUILD-611) Proxy remote repositories broken/disabled?

by Heiko Braun (JIRA)

Proxy remote repositories broken/disabled? ------------------------------------------ Key: JBBUILD-611 URL: https://jira.jboss.org/jira/browse/JBBUILD-611 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Heiko Braun A build fails because commons-collections:3.2.1 cannot be found. I checked our local repo, it really doesn't contain it. However the apache repo, which should proxied does so: https://repository.apache.org/index.html#nexus-search;quick~commons-colle... Shouldn't these artifacts be available automatically in our own builds? I.e. being pulled upon demand and stored in a local copy of the apache repo? -- 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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7645) Alphebetize the System Properties logged by ServerInfo in boot.log

by Andrew Lee Rubinger (JIRA)

Alphebetize the System Properties logged by ServerInfo in boot.log ------------------------------------------------------------------ Key: JBAS-7645 URL: https://jira.jboss.org/jira/browse/JBAS-7645 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: System service Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger For readability, alphabetize the sysprop dump -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7981) Use of jgroups.tcpping.initial_hosts in example JGroups configurations

by Brian Stansberry (JIRA)

Use of jgroups.tcpping.initial_hosts in example JGroups configurations ---------------------------------------------------------------------- Key: JBAS-7981 URL: https://jira.jboss.org/jira/browse/JBAS-7981 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M4 The TCP JGroups configurations use the property jgroups.tcpping.initial_hosts for the example TCPPING configurations. <TCPPING timeout="3000" initial_hosts="${jgroups.tcpping.initial_hosts:localhost[7600],localhost[7601]}" port_range="1" num_initial_members="3"/> This is the internal JGroups property that overrides all TCPPING.initial_hosts values. This property should not be used here, as it encourages users to set this property, which has the unintended consequence of overriding *all* TCPPING.initial_hosts values. Investigate jboss.partition.udpGroup as well, although JGroups shouldn't be using properties in the jboss namespace any 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

13 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2010