January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-557) need to include all the transports within the tests.versioning ant target

by Tom Elrod (JIRA)

need to include all the transports within the tests.versioning ant target ------------------------------------------------------------------------- Key: JBREM-557 URL: http://jira.jboss.com/jira/browse/JBREM-557 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Due to a problem with the test setup, some of the versioning tests (for rmi and socket) do not pass when running the versioning tests. Know these actually work when run manually, so need to investigate why automated tests are failing. -- 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: (JBREM-643) configuration for multi-homed server invokers

by Tom Elrod (JIRA)

configuration for multi-homed server invokers --------------------------------------------- Key: JBREM-643 URL: http://jira.jboss.com/jira/browse/JBREM-643 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.0.Alpha4 Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Need to allow explicit configuration for multi-homed systems so can be done via one Connector with multiple bindings. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-3532) Inject DRM and DS into ClusterPartition

by Brian Stansberry (JIRA)

Inject DRM and DS into ClusterPartition --------------------------------------- Key: JBAS-3532 URL: http://jira.jboss.com/jira/browse/JBAS-3532 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta DRM and DS are now independent services. Inject them into ClusterPartiton so they can be exposed via HAPartition. ClusterPartition in create or start must confirm that the injected DRM and DS are using the same JChannelFactory and stack that it is. -- 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

5
8
0 / 0

[JBoss JIRA] Created: (JBAOP-290) Make src/build.xml work

by Kabir Khan (JIRA)

Make src/build.xml work ----------------------- Key: JBAOP-290 URL: http://jira.jboss.com/jira/browse/JBAOP-290 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 Should be part of the dist and it should be possible to build the full aop/aspects releases and run some of the tests -- 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
13
0 / 0

[JBoss JIRA] Created: (JBAS-3815) Deployment Level Principal-Role Mapping passed to authorization layer

by Anil Saldhana (JIRA)

Deployment Level Principal-Role Mapping passed to authorization layer --------------------------------------------------------------------- Key: JBAS-3815 URL: http://jira.jboss.com/jira/browse/JBAS-3815 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Since the JBoss 4.0.x days, the deployment level rolename to principal set mapping is available in the meta data, but there was no usage of this in the authorization layer. There is a need for this information to be passed to the authorization manager/mapping layer. Affects the ejb3, ejb21 and web layers [jboss.xml,jboss-web.xml and jboss-app.xml] -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-3921) Merge JBCLUSTER-150 fixes with 4.0.5.GA tag

by Vivek Lakshmanan (JIRA)

Merge JBCLUSTER-150 fixes with 4.0.5.GA tag ------------------------------------------- Key: JBAS-3921 URL: http://jira.jboss.com/jira/browse/JBAS-3921 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Vivek Lakshmanan Assigned To: Brian Stansberry Fixes from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798 need merging into a branch off the 4.0.5GA tag so they can be picked up by the patch process. No tag needs to be made on this branch as long as the branch's head satisfactorily fixes the JBCLUSTER-150 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

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-3934) Backport JBAS-3460 to Branch_4_2

by Brian Stansberry (JIRA)

Backport JBAS-3460 to Branch_4_2 -------------------------------- Key: JBAS-3934 URL: http://jira.jboss.com/jira/browse/JBAS-3934 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 The additions to jboss-web.xml should be backported. My inclination is not to remove the default snapshot mode/interval config from the Tomcat SAR config though, as 4.2 is not a major release. -- 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: (EJBTHREE-853) Partial StringProperty replacement in ejb 3 container

by Roland R?z (JIRA)

Partial StringProperty replacement in ejb 3 container ----------------------------------------------------- Key: EJBTHREE-853 URL: http://jira.jboss.com/jira/browse/EJBTHREE-853 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - FD Reporter: Roland R?z I tried to change the messageSelector in an EJB 3.0 MDB in the ejb.jar.xml containing partial System Property references (aaa${xyz}bbb). Sadly this didn't work as with ejb 2.1. I think fully supporting system property replacement as with ejb 2.x in EJB 3.0 would be a nice feature. The method org.jboss.ejb3.metamodel.EjbJarDDObjectFactory.getValue(String name, String value) could be changed to { value = org.jboss.util.StringPropertyReplacer.replaceProperties(value); } I would suggest, to implement the string property replacement even better in the class org.jboss.metamodel.descriptor.DDObjectFactory.getValue() and remove the getValue method from JBossDDObjectFactory and EjbJarDDObjectFactory. The idea of using an MBean abstraction to replace system properties is fine but the nice syntax of the StringPropertyReplacer should be still supported (${v1,v2:default}). Returning always the replaced property is one possibility (currently it is not done this way) but probably a new method "getReplaced" would be less surprising. -- 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
1
0 / 0

[JBoss JIRA] Created: (JGRP-375) Paralellize discovery phase

by Bela Ban (JIRA)

Paralellize discovery phase --------------------------- Key: JGRP-375 URL: http://jira.jboss.com/jira/browse/JGRP-375 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 With TCPPING, if we have 10 servers defined in the list, we sequentially send a GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the socket connect call. Also, DNS lookup might take some time, so we might time out if we cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and we will become a singleton node. SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the sending of requests to all 10 servers. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAS-3794) Remove all calls to InetAddress.getHostName() (causes reverse DNS lookup)

by Michael Newcomb (JIRA)

Remove all calls to InetAddress.getHostName() (causes reverse DNS lookup) ------------------------------------------------------------------------- Key: JBAS-3794 URL: http://jira.jboss.com/jira/browse/JBAS-3794 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.4.GA Environment: Java 5 JBoss 4.0.4 Reporter: Michael Newcomb Assigned To: Brian Stansberry Priority: Minor Any call to InetAddress.getHostName() will cause a reverse DNS lookup. If DNS is not configured properly, can cause slow startup/join times between JBoss clusters. The most notable is in ClusterNode.java: public ClusterNode(IpAddress jgAddress) { if (jgAddress.getAdditionalData() == null) { this.id = jgAddress.getIpAddress().getHostAddress() + ":" + jgAddress.getPort(); } else { this.id = new String(jgAddress.getAdditionalData()); } this.originalJGAddress = jgAddress; StringBuffer sb = new StringBuffer(); java.net.InetAddress jgIPAddr = jgAddress.getIpAddress(); if (jgIPAddr == null) sb.append("<null>"); else { if (jgIPAddr.isMulticastAddress()) sb.append(jgIPAddr.getHostAddress()); else ----->>>> sb.append(getShortName(jgIPAddr.getHostName())); } sb.append(":" + jgAddress.getPort()); this.jgId = sb.toString(); } The following: if (jgIPAddr.isMulticastAddress()) sb.append(jgIPAddr.getHostAddress()); else sb.append(getShortName(jgIPAddr.getHostName())); should be replaced with: sb.append(jgIPAddr.getHostAddress()); -- 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
3
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 January 2007