September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-312) Make testsuite configurable to run with different stack configurations

by Bela Ban (JIRA)

Make testsuite configurable to run with different stack configurations ---------------------------------------------------------------------- Key: JGRP-312 URL: http://jira.jboss.com/jira/browse/JGRP-312 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 All test programs should use a system property (with a default if the system property is not defined). The testsuite can then be run with the system property, so all tests use TCP, for example. We could also use multiple targets, one for each major stack configuration. An 'all-unittests' target would run all of them. -- 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

19 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-321) CloseTest.testShutdown() fails with -Dconfig=tcp.xml

by Bela Ban (JIRA)

CloseTest.testShutdown() fails with -Dconfig=tcp.xml ---------------------------------------------------- Key: JGRP-321 URL: http://jira.jboss.com/jira/browse/JGRP-321 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-156) consistent packaging

by Kurt Stam (JIRA)

consistent packaging -------------------- Key: JBESB-156 URL: http://jira.jboss.com/jira/browse/JBESB-156 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Can we do some more refactoring of package names? For example I'd like to see everything in 'product/core/common' directory to be rooted in the org.jboss.soa.esb.common.* package. 'product/core/services' directory to be rooted in the org.jboss.soa.esb.services.* package. Somehow it's all mixed up right now and I keep on having to click around to find classes. -- 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

19 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-145) Automate the trailblazer as part of QA

by Mark Little (JIRA)

Automate the trailblazer as part of QA -------------------------------------- Key: JBESB-145 URL: http://jira.jboss.com/jira/browse/JBESB-145 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples, Testing Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Daniel Brum Fix For: 4.0 -- 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

19 years, 4 months

1
10
0 / 0

[JBoss JIRA] Created: (JBESB-133) Hosting trailblazer on docs site

by Mark Little (JIRA)

Hosting trailblazer on docs site -------------------------------- Key: JBESB-133 URL: http://jira.jboss.com/jira/browse/JBESB-133 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Testing Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Daniel Brum Priority: Minor Fix For: 4.0 We should look at hosting the TB here along with some good writeup on it, diagrams explaining each step of the way, etc... http://www.jboss.com/docs/demos -- 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

19 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBADMCON-149) Support JBoss Messaging

by chi lin (JIRA)

Support JBoss Messaging ----------------------- Key: JBADMCON-149 URL: http://jira.jboss.com/jira/browse/JBADMCON-149 Project: JBoss Admin Console Issue Type: Feature Request Components: General Console Affects Versions: 1.1 alpha Reporter: chi lin Assigned To: chi lin Fix For: 1.1 alpha Since JBoss Messaging will be the default JMS provider for JBoss AS 5.x, the Admin Console should support JBoss Messaging instead of (or in addition to) JBossMQ. -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3398) Non exploded sar containing war cannot undeploy the war file properly

by Julien Viet (JIRA)

Non exploded sar containing war cannot undeploy the war file properly --------------------------------------------------------------------- Key: JBAS-3398 URL: http://jira.jboss.com/jira/browse/JBAS-3398 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final Environment: JBoss-4.0.4.GA MacOSX Tiger Java 1.4.2 Reporter: Julien Viet Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.GA A sar file containing a war file non exploded is dropped in AS before startup. Start JBoss Shutdown JBoss The MainDeployer wants to stop() / destroy() the war file. The Web deployer is already gone and it produces an javax.management.InstanceNotFoundException when it tries to stop() / destroy() the war deployer Because the war is nested in a sar file, the web deployer is undeployed before the sar containing the war is undeployed. Note : this does not happen with exploded sar (like http invoker sar that contains the invoker.war) because the war is added to the MainDeployer.deploymentList list. This does not happen with non exploded because the war file is not in the local directory but rather in tmp and thus does not get added to the deployment list. Here are some field values : the string used to discriminate wether it's in local or tmp - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/ a war in non exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/tmp51485jboss-portal.sar-contents/portal-core.war invoker.war in exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/deploy/http-invoker.sar/invoker.war/ -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3615) failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase

by Dimitris Andreadis (JIRA)

failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase ------------------------------------------------------------------------------ Key: JBAS-3615 URL: http://jira.jboss.com/jira/browse/JBAS-3615 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testMalformed Failure invalid object name: domain:=,foo=bar junit.framework.AssertionFailedError: invalid object name: domain:=,foo=bar at org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase$FullNameTEST.testMalformed(MalformedTestCase.java:152) -- 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

19 years, 4 months

2
16
0 / 0

[JBoss JIRA] Created: (JBPM-695) Have the GPD add all default attributes to nodes instead of leaving them out

by Ronald van Kuijk (JIRA)

Have the GPD add all default attributes to nodes instead of leaving them out ---------------------------------------------------------------------------- Key: JBPM-695 URL: http://jira.jboss.com/jira/browse/JBPM-695 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Environment: N/A Reporter: Ronald van Kuijk Assigned To: Tom Baeyens It would be nice if the GPD added the defaults of attributes to nodes (e.g. task-end="false" on a tasknode) this way, even with no graphical support, users often think further, search for it etc, that it would help (even for me!!! ;-)) -- 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

19 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-157) Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time

by Esteban Schifman (JIRA)

Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time --------------------------------------------------------------------------------------------------------------------------- Key: JBESB-157 URL: http://jira.jboss.com/jira/browse/JBESB-157 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Reporter: Esteban Schifman Assigned To: Esteban Schifman Fix For: 4.0 GpListener has at present two mechanisms to reload it's configuration parameters: a) timer driven 2) message driven. At parameter reload time, the controlling instance of GpListener will try to instantiate new child processes according to the new configuration values. It will allow active child threads to gracetully finish. New listener classes that are accepting connections on specific sockets will have a conflict when the new instance tries to listen on a port that is being used by the active instance. -- 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

19 years, 4 months

2
7
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 September 2006