January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-514) AbstractAspectManager.destroy() should be calling undeployXml() instead of deployXml()

by Kabir Khan (JIRA)

AbstractAspectManager.destroy() should be calling undeployXml() instead of deployXml() -------------------------------------------------------------------------------------- Key: JBAOP-514 URL: http://jira.jboss.com/jira/browse/JBAOP-514 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR3 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.GA -- 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
4
0 / 0

[JBoss JIRA] Assigned: (JBAS-3131) Extension-List MANIFEST attribute not honored during deployment of an EAR

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3131?page=all ] Vicky Kak reassigned JBAS-3131: ------------------------------- Assignee: Vicky Kak > Extension-List MANIFEST attribute not honored during deployment of an EAR > ------------------------------------------------------------------------- > > Key: JBAS-3131 > URL: http://jira.jboss.com/jira/browse/JBAS-3131 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Windows XP SP2, JDK 1.5.0_06 > Reporter: Alexander Sack > Assigned To: Vicky Kak > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > > If a JAR within an EAR specifies an Extension-List MANIFEST attribute, the EAR deployer does not honor it. I have a library, my.jar, that gets deployed that specifies an Extension-Name and Implementation-Version. If any of my jars within an EAR references this library, JBoss ignores the Extension-List attribute. The use of the Extension-List MANIFEST attribute is part of the core J2EE 1.4 spec and the EAR deployment should fail if the Extension-List library is not found (or if it is found and the <name>-Implementatino-Version does not meet the minimal requirements. -- 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-655) Connect failed

by Bela Ban (JIRA)

Connect failed -------------- Key: JGRP-655 URL: http://jira.jboss.com/jira/browse/JGRP-655 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 [Vladimir] I think I got one of the last failures in modified ViewDeliveryDemo. I am testing 2.6 branch on atlanta cluster. It was related to a case where no traffic seems to be going between members after connect failure occurred. A connect failure specifically related to join reject due to a member already being included in a view - this was not port related I believe but rather a race of sending join request. I used port manager. Anyhow, to be honest I did not understand the underlying reasons but I did something that seems to be intuitive. In connect method I reversed stack to original state in case of connect failure. That includes calling stopStack and init(). if(res != null && res instanceof Exception) { try { prot_stack.stopStack(); } catch(Exception e) { if(log.isErrorEnabled()) log.error("exception: " + e); } init(); throw new ChannelException("connect() failed", (Throwable)res); } } After this fix I did not see the problem again an I ran three member test for about two hours. Cheers. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBADMCON-152) Logger class not found loading applet; workaround included

by Scott Dickerson (JIRA)

Logger class not found loading applet; workaround included ---------------------------------------------------------- Key: JBADMCON-152 URL: http://jira.jboss.com/jira/browse/JBADMCON-152 Project: JBoss Admin Console Issue Type: Bug Components: General Console Environment: windows xp; jboss-5.0.0.Beta3 Reporter: Scott Dickerson Priority: Minor The applet fails to load due to ClassNotFound exception loading org.jboss.logging.Logger (?). To fix, do this: copy jboss-5.0.0.Beta3\lib\jboss-common-core.jar to server\default\deploy\management\console-mgr.sar\web-console.war copy jboss-5.0.0.Beta3\lib\jboss-logging-spi.jar to server\default\deploy\management\console-mgr.sar\web-console.war copy jboss-5.0.0.Beta3\server\default\lib\jboss.jar to server\default\deploy\management\console-mgr.sar\web-console.war modify jboss-5.0.0.Beta3\server\default\deploy\management\console-mgr.sar\web-console.war\applet.jsp as follows: from code="org.jboss.console.navtree.AppletBrowser" archive="applet.jar, " to code="org.jboss.console.navtree.AppletBrowser" archive="applet.jar, jboss-common-core.jar, jboss-logging-spi.jar, jboss.jar" -- 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: (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] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2870?page=all ] Brian Stansberry updated JBAS-2870: ----------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) > Separate the HA aspect from the invoker proxy > --------------------------------------------- > > Key: JBAS-2870 > URL: http://jira.jboss.com/jira/browse/JBAS-2870 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369) > HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy. -- 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: (JBAS-2750) Create integration tests using JBossCache and JBoss TM

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2750?page=all ] Brian Stansberry updated JBAS-2750: ----------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Assignee: Brian Stansberry > Create integration tests using JBossCache and JBoss TM > ------------------------------------------------------ > > Key: JBAS-2750 > URL: http://jira.jboss.com/jira/browse/JBAS-2750 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.CR1 > > > Need to add integration tests that confirm that JBossCache works properly with JBoss TM as its transaction manager. The standalone cache unit tests use DummyTransactionManager, as use of JBoss TM requires the app server. Beginning with 4.0.4, the AS web-tier state replication tests also no longer use JBoss TM. > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76306 for an example of the kind of thing such tests should find. -- 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: (JBCACHE-1264) Blue Screen on JBC 2.0.0 startup on Wndows XP

by Mircea Markus (JIRA)

Blue Screen on JBC 2.0.0 startup on Wndows XP ---------------------------------------------- Key: JBCACHE-1264 URL: http://jira.jboss.com/jira/browse/JBCACHE-1264 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Environment: Windows XP only. Does work on Vista, Ubuntu Mac OS, RHEL, Fedora Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 2.1.0.GA An user noticed that default configuration of JBC2.0.0 crashes on WinXP. When starting the cache, blue screen appears. -- 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
8
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 2008