October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1089) Upgrade to JGroups 2.5

by Tim Fox (JIRA)

Upgrade to JGroups 2.5 ---------------------- Key: JBMESSAGING-1089 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: AS 5.0 Integration Update to JGroups 2.5 to take advantage of better throughput. We need to ensure the post office code is sufficiently thread safe. We may need to do another release for this -- 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

3
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1027) Timeout method gets called with an unspecified caller identity

by Carlo de Wolf (JIRA)

Timeout method gets called with an unspecified caller identity -------------------------------------------------------------- Key: EJBTHREE-1027 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1027 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: AS 4.2.1.GA Reporter: Carlo de Wolf Having a secured bean with a timeout method with @PermitAll, but without an unauthenticatedIdentity will lead to a 'random' identity being used to call the method or no identity at all. The last one leads to EJBAccessExceptions. Spec 18.2.2: "Since the timeout callback method is an internal method of the bean class, it has no client security context. When getCallerPrincipal is called from within the timeout callback method, it returns the container's representation of the unauthenticated identity." We must disallow all calls to a timeout method if unauthenticatedIdentity is not set. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-919) deplace JBossXB descriptor processing with JAXB

by William DeCoste (JIRA)

deplace JBossXB descriptor processing with JAXB ----------------------------------------------- Key: EJBTHREE-919 URL: http://jira.jboss.com/jira/browse/EJBTHREE-919 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.0 CR1 Reporter: William DeCoste Assigned To: William DeCoste -- 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-4673) SARDeployer should throw an error if there is more than one loader repository

by Adrian Brock (JIRA)

SARDeployer should throw an error if there is more than one loader repository ----------------------------------------------------------------------------- Key: JBAS-4673 URL: http://jira.jboss.com/jira/browse/JBAS-4673 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Fix For: JBossAS-4.2.2.GA, JBossAS-5.0.0.GA The SAR Deployer should be throwing an error if it finds more than one loader-repository config. Currently it just ignores the duplicates and uses the first one. The same problem exists in head in ServiceDeploymentParser::parseLoaderRepositoryConfig() which was copied from the SAR deployer. -- 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

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle

by Owen Taylor (JIRA)

Way to set JNDI properties for twiddle -------------------------------------- Key: JBAS-3637 URL: http://jira.jboss.com/jira/browse/JBAS-3637 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Owen Taylor Priority: Minor It is frequently useful to be able to set JDNI properties when running twiddle - for example, you might want to set jnp.disableDiscovery when checking the status of a particular server that might not be running. Right now, this is difficult to do. You can export a JBOSS_CLASSPATH which contains a jndi.properties file before running twiddle.sh, but then you have to include all the standard jars in it, which is quite annoying. A pssible fixes would be one of: A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default construction (also useful for getting a log4j.properties that doesn't drop twiddle.log in the cwd, perhaps) B) A command line option for specifying a particular properties file to load and pass to 'new InitialContext()' (slightly more convenient than A) C) A command line option to define particular properties: twiddle.sh -jnpProperty=jnp.disableDiscovery=true (Or some better syntax) The twiddle code actually does: Properties props = new Properties(System.getProperties()); props.put(Context.PROVIDER_URL, serverURL); ctx = new InitialContext(props); In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take effect, and system properties won't be looked at in the other code path either. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JGRP-606) Use same properties for start_port/bind_port and end_port/port_range

by Bela Ban (JIRA)

Use same properties for start_port/bind_port and end_port/port_range -------------------------------------------------------------------- Key: JGRP-606 URL: http://jira.jboss.com/jira/browse/JGRP-606 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.7 In UDP, we use bind_port and port_range to define a range of valid ports. In TCP, we use start_port and end_port We should use - bind_port (rather than start_port) to define the port to bind to - end_port to define the range -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-200) AOP/MC Proxies do not include original annotations

by Kabir Khan (JIRA)

AOP/MC Proxies do not include original annotations -------------------------------------------------- Key: JBMICROCONT-200 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-200 Project: JBoss MicroContainer Issue Type: Bug Components: AOP Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC-2.0.0.CR1 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-989) Create performance test suite to test failover

by Manik Surtani (JIRA)

Create performance test suite to test failover ---------------------------------------------- Key: JBCACHE-989 URL: http://jira.jboss.com/jira/browse/JBCACHE-989 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc. -- 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, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-105) Refactor the VFS.isArchive and structural deployers

by Scott M Stark (JIRA)

Refactor the VFS.isArchive and structural deployers --------------------------------------------------- Key: JBMICROCONT-105 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-105 Project: JBoss MicroContainer Issue Type: Task Reporter: Scott M Stark We have been arguing about the ambiguity/utility of the vfs isArchive with regard to determing deployment strucutre. Proper separation of behavior would remove isArchive from the vfs and update the structural deployment spi to allow reuse of the structural parse without having to pull in jboss5/MainDeployer + all deployers. A related structure deployer discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92529 VFS visiting: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92141 VFS isArchive removal: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92139 -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1128) Add a full component-info.xml to source tree

by Brian Stansberry (JIRA)

Add a full component-info.xml to source tree -------------------------------------------- Key: JBCACHE-1128 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.GA The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree. -- 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, 4 months

2
6
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 October 2007