February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1478) inconsistent test suite performance

by Aleksandar Kostadinov (JIRA)

inconsistent test suite performance ----------------------------------- Key: JBMESSAGING-1478 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1478 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.4.0.SP3.CP04 Reporter: Aleksandar Kostadinov Assignee: Tim Fox I see inconsistent performance running the JBM test suite. Here I have 2 builds on the same physical machine (windows), using local disk storage so environment should be pretty stable. The mysql database is shared but I doubt it is the culprit. I run the test suite with the following options: property( name: "functional.tests.database", value: dbname ) property( name: "stress.tests.database", value: dbname ) property( name: "clustering.tests.database", value: dbname ) property( name: "test.target", value: "report" ) property( name: "test.bind.address", value: properties["env.MYTESTIP_1"] ) property( name: "jboss.messaging.groupname", value: properties["env.BUILD_TAG"]) property( name: "jboss.messaging.datachanneludpaddress", value: properties["env.MCAST_ADDR"] ) property( name: "jboss.messaging.controlchanneludpaddress", value: properties["env.MCAST_ADDR"] ) Are there any other options I can add to increase isolation from other processes in the same LAN? Would you be able to look at these 2 builds and based on the logs, say why is the first one taking longer and eventually timeout? http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbm/163/ http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbm/164/ -- 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

13 years, 3 months

4
24
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1401) Unverified: Restarting a Queue will delete persistent messages in the queue.

by Jay Howell (JIRA)

Unverified: Restarting a Queue will delete persistent messages in the queue. ---------------------------------------------------------------------------- Key: JBMESSAGING-1401 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1401 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Jay Howell Assignee: Tim Fox Restarting a queue in a running server will delete persistent messages out of the database. This bug was found while troubleshooting a case. When a customer restarted the queues, they noticed that all of the persistent messages in the database were gone. I have yet to verify this and will verify as soon as possible. I wanted to make sure that I didn't forget to put it in. So at this point this is an unverified bug. -- 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

13 years, 3 months

5
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1517) Malformed HTTP POST from Post Office management page in JMX Console

by Paul Kaiser (JIRA)

Malformed HTTP POST from Post Office management page in JMX Console ------------------------------------------------------------------- Key: JBMESSAGING-1517 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1517 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP03 Environment: All Reporter: Paul Kaiser Assignee: Tim Fox When trying to submit changes to the configuration of the Messaging Post Office from the JMX Console interface, the improper quoting of configuration strings results in an improper HTTP POST. This prevents the submission of any updates to the component. -- 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

13 years, 3 months

4
24
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1513) Database maintenance scripts

by Len DiMaggio (JIRA)

Database maintenance scripts ---------------------------- Key: JBMESSAGING-1513 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1513 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: 1.4.2.GA.SP1 Reporter: Len DiMaggio Assignee: Tim Fox Project JIRA for SOA-P platform JIRA: https://jira.jboss.org/jira/browse/SOA-310 -- 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

13 years, 3 months

4
20
0 / 0

[JBoss JIRA] Created: (JBBUILD-357) Eclipse PDE integration into Maven and unit test failure

by Mark Proctor (JIRA)

Eclipse PDE integration into Maven and unit test failure -------------------------------------------------------- Key: JBBUILD-357 URL: http://jira.jboss.com/jira/browse/JBBUILD-357 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Mark Proctor Assigned To: Paul Gier Eclipse plugin building and testing is automated by ant, executed by the Eclipse antRunner. Inside of Maven we have antRunner called in two different phases. When the test phase has unit test failures, they are not propagated up to maven, so failures are not flagged and a sucecssful build reported. Look in the drools-eclipse module of jboss rules for more details. -- 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

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-470) Release plugin doesn't pickup compile plugin configuration from parent

by Carlo de Wolf (JIRA)

Release plugin doesn't pickup compile plugin configuration from parent ---------------------------------------------------------------------- Key: JBBUILD-470 URL: http://jira.jboss.com/jira/browse/JBBUILD-470 Project: JBoss Build System Issue Type: Bug Environment: 4-beta2 Reporter: Carlo de Wolf Assigned To: Paul Gier Compile configuration defined in a parent pom does not get picked up by the release plugin during 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

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree

by Andrew Lee Rubinger (JIRA)

Move JBossAS Maven Plugins into their own tree ---------------------------------------------- Key: JBASMP-12 URL: https://jira.jboss.org/jira/browse/JBASMP-12 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Currently under maven/plugins/jboss/trunk is: drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire -rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml Those prefixed with "maven-jboss-as" should be in their own tree -- 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

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-7) Break out Deployment-related Plugins into their own Project

by Andrew Lee Rubinger (JIRA)

Break out Deployment-related Plugins into their own Project ----------------------------------------------------------- Key: JBASMP-7 URL: http://jira.jboss.com/jira/browse/JBASMP-7 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-plugin Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 0.1.0 The Control Plugin currently houses Deployment Mojos; these should have their own Plugin. -- 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

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-478) Create "deploy" Mojo for maven-jboss-as-control-plugin

by Andrew Lee Rubinger (JIRA)

Create "deploy" Mojo for maven-jboss-as-control-plugin ------------------------------------------------------ Key: JBBUILD-478 URL: http://jira.jboss.com/jira/browse/JBBUILD-478 Project: JBoss Build System Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop". We need to add a "deploy" Mojo which delegates to congruent functionality from jboss-test. Existing Mojos: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-c... Root Checkout Location: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk After the "deploy" Mojo is created, configuration to use it should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM. This is the self-documenting usage project which may also prove its validity. -- 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

13 years, 3 months

3
14
0 / 0

[JBoss JIRA] Created: (JBASMP-5) Rename folder structure of modules

by Andrew Lee Rubinger (JIRA)

Rename folder structure of modules ---------------------------------- Key: JBASMP-5 URL: http://jira.jboss.com/jira/browse/JBASMP-5 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Modules are currently namespaced with "maven-jboss-as-", which is unnecessary due to the groupId and folder structure. For instance: maven-jboss-as-build ...should become: build -- 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

13 years, 3 months

2
1
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 February 2009