December 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6279) Remove assumption about who master is from HA Singleton test cases

by Brian Stansberry (JIRA)

Remove assumption about who master is from HA Singleton test cases ------------------------------------------------------------------ Key: JBAS-6279 URL: https://jira.jboss.org/jira/browse/JBAS-6279 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.1.CR1 HASingletonControllerBeanUnitTestCase and HASingletonDeployerTestCase both assume node 0 is the singleton master and then make assertions based on that fact. This leads to spurious test failures if some earlier event during the test run caused node 1 to become the coordinator. The tests should determine who the master is and then check the behavior was as expected. -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6270) ManagementView.getDeploymentNames does not show the bootstrap deployment names

by Scott M Stark (JIRA)

ManagementView.getDeploymentNames does not show the bootstrap deployment names ------------------------------------------------------------------------------ Key: JBAS-6270 URL: https://jira.jboss.org/jira/browse/JBAS-6270 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.1.CR1 Although one can query for components from the bootstrap deployments, the names of the bootstrap deployments do not show up in the ManagementView.getDeploymentNames() result. For example, the jboss.system:type=MCServer component has a ManagedDeployment of org.jboss.managed.plugins.ManagedDeploymentImpl@eef3c1{name=file:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.GA/server/profileservice/conf/bootstrap/deployers.xml, types=[jboss-beans, beans], phase=BOOTSTRAP, parent=null,... but the conf/bootstrap/deployers.xml deployment name is not seen in the getDeploymentNames result. -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6271) Create a 'standard' config out of the 'cts' one.

by Dimitris Andreadis (JIRA)

Create a 'standard' config out of the 'cts' one. ------------------------------------------------ Key: JBAS-6271 URL: https://jira.jboss.org/jira/browse/JBAS-6271 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossAS-5.0.0.GA Bundle with the distro the config we use for tck testing. -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1609) ClassHelper needs privileged blocks for all sensistive operations

by Anil Saldhana (JIRA)

ClassHelper needs privileged blocks for all sensistive operations ----------------------------------------------------------------- Key: EJBTHREE-1609 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1609 Project: EJB 3.0 Issue Type: Sub-task Reporter: Anil Saldhana http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194095 -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6154) Verify JAXB version for 5.0.0.GA release

by Shelly McGowan (JIRA)

Verify JAXB version for 5.0.0.GA release ---------------------------------------- Key: JBAS-6154 URL: https://jira.jboss.org/jira/browse/JBAS-6154 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: XML services Reporter: Shelly McGowan Assignee: Alexey Loubyansky Fix For: JBossAS-5.0.0.GA Can you confirm the version of JAXB for 5.0.0.GA. The current version is: <version.sun.jaxb>2.1.4</version.sun.jaxb> dependency> <groupId>sun-jaxb</groupId> <artifactId>jaxb-api</artifactId> <version>${version.sun.jaxb}</version> </dependency> <dependency> <groupId>sun-jaxb</groupId> <artifactId>jaxb-impl</artifactId> <version>${version.sun.jaxb}</version> </dependency> <dependency> <groupId>sun-jaxb</groupId> <artifactId>jaxb-xjc</artifactId> <version>${version.sun.jaxb}</version> </dependency> But the latest release 2.1.9: https://jaxb.dev.java.net/2.1.9/ JBCTS-833 will be done again for the GA release. -- 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

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Resolved: (JBAS-2563) Cleanup the build for jboss5

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2563?page=com.atlassian.jira.plug... ] Dimitris Andreadis resolved JBAS-2563. -------------------------------------- Resolution: Done Close the parent task, I think we are good. > Cleanup the build for jboss5 > ---------------------------- > > Key: JBAS-2563 > URL: https://jira.jboss.org/jira/browse/JBAS-2563 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Scott M Stark > Assignee: Paul Gier > Priority: Critical > Fix For: JBossAS-5.0.0.GA > > > Use this parent task to hold build clean-up tasks. > Scott's original request was related with the cleaning up of the jbossas module that has turned into a new "varia". -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1882) Make Drools Flow nodes configurable

by Kris Verlaenen (JIRA)

Make Drools Flow nodes configurable ----------------------------------- Key: JBRULES-1882 URL: https://jira.jboss.org/jira/browse/JBRULES-1882 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.CR1 Allow configuration of which node types can be used in the graphical editor. -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6235) Delay the join in into a cluster and prevent starting timers, RMI calls ... before 'up and ready' state

by Wolf-Dieter Fink (JIRA)

Delay the join in into a cluster and prevent starting timers, RMI calls ... before 'up and ready' state ------------------------------------------------------------------------------------------------------- Key: JBAS-6235 URL: https://jira.jboss.org/jira/browse/JBAS-6235 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Deployers, Remoting Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If applications become complex it is, more or less, difficult to ensure a save startup or shutdown of a JBoss node especially within a clustered environment. Due to this it might be good to start all services and applications before the node join in into a cluster and accept calls or timer-activation. Also do it vice-versa in case of shutdown. This shortens the time during the application can no work correctly and will throw Exceptions or not work correctly. The behaviour becomes more strange if the 'TransactionSticky' features (since 4.2.3 see JBAS-4455) is used, because the UserTransaction service is deployed 'long' before the application-ears are. -- 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

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6055) Use the enforcer plugin to avoid bringing in duplicate/wrong dependencies

by Dimitris Andreadis (JIRA)

Use the enforcer plugin to avoid bringing in duplicate/wrong dependencies ------------------------------------------------------------------------- Key: JBAS-6055 URL: https://jira.jboss.org/jira/browse/JBAS-6055 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assignee: Paul Gier Priority: Critical Fix For: JBossAS-5.0.0.GA We need to create an exclude list for the enforcer plugin so that artifacts we know are wrong do not enter the build. -- 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

15 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1608) Sync up EJB3 JACC Configuration with AS

by Anil Saldhana (JIRA)

Sync up EJB3 JACC Configuration with AS --------------------------------------- Key: EJBTHREE-1608 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1608 Project: EJB 3.0 Issue Type: Task Components: testsuite Affects Versions: 1.0.0-Beta9 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0-Beta10 -- 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

15 years, 5 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 December 2008