Component updates for AS5
by Dimitris Andreadis
The following JIRA task contains all the known remaining component updates for AS5 GA as we
need to bring to GA level all the components included in AS. If I have missed something, let
me know.
https://jira.jboss.org/jira/browse/JBAS-5597
For some components it will be simply a matter of tagging/releasing the latest CR version as
GA, but for some others there is still work in progress.
I'd like everyone to take a look and
a) Create dependency links between component updates to reflect the right ordering (e.g. the
MC components are released in the order of: reflect, mdr, man, mc, etc.
b) Create dependency links to show important remaining work. Eg. make dependencies to
profile service enhancement tasks if that is in the critical path of delivering a component.
The deadline of bringing in the majority of component updates is Oct/20th. If you have
problems with this date, please let me know ASAP.
We have also a task to cleanup the AS build as much as possible:
https://jira.jboss.org/jira/browse/JBAS-2563
Also, please make sure your updates *do not to break* the existing tck/testsuites.
Thanks
/Dimitris
17 years, 2 months
Re: deployers + failing bootstrap test
by Ales Justin
Yeah, I know all this stuff.
And I've been following the forum discussion.
;-)
The bottom thing is that tests are failing:
-
https://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/974/te...
-
https://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/974/te...
And I also shouldn't get a failing test when I run simple deployers test
- 'build test -Dtest=deployers' + running 'run -c profileservice'
Looks like to me you're missing exclusions for your test.
Meaning it should be excluded from default, profileservice, ... config
only to be used / picked-up for your custom config.
See how this is done for ProfileService or Spring tests.
Ivo Studensky wrote:
> BootstrapDependenciesTestCase is related to
> https://jira.jboss.org/jira/browse/JBAS-5349 .
>
> In brief, it creates a testing SAR with name
> Aaabootstrapdependencies-jbas5349.sar, includes a testing module into
> it (for example a JAR of EJB3 session bean) and copy this into the
> deploy directory. Then it starts a server and tests whether the
> deployment of testing SAR was successful or not. (the testing SAR is
> deployed as the first service from /deploy directory because of its
> name)
>
> The definitions of testing modules are located in
> testsuite/imports/sections/deployers.xml. The definitions of tests
> are located in
> testsuite/imports/config/tests-bootstrap-dependencies.xml. If the
> test failed you can look at particular configuration to the server
> for the reasons, e.g.
> server/bootstrapdependenciesJBAS5349-EJB3Session.
>
> For more info see related forum:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142232 .
>
>
> Have a nice day...
>
17 years, 2 months
JGroups 2.4.4.GA is released
by Richard Achmatowicz
Hello
JGroups 2.4.4.GA has been released.
The binary and source distribution can be downloaded from
http://sourceforge.net/project/showfiles.php?group_id=6081.
The release notes and change log are below.
Enjoy !
Richard Achmatowicz
*Notes:*
This is a bug fix release.
*Changes:*
Release Notes - JGroups - Version 2.4.4
** Bug
* [JGRP-798] - unable to setup the protocol stack on AIX
** Task
* [JGRP-820] - Change default diagnostics address to 224.0.75.75
17 years, 2 months
deployers + failing bootstrap test
by Ales Justin
While testing new MC releases, I saw
[junit] Running
org.jboss.test.deployers.jbas5349.test.BootstrapDependenciesTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,562 sec
[junit] Test
org.jboss.test.deployers.jbas5349.test.BootstrapDependenciesTestCase FAILED
when testing deployers (build test -Dtest=deployer) with profileservice
config.
Looking at BootstrapDependenciesTestCase,
I don't see that it deploys anything,
but expects some MBean to be present:
public class BootstrapDependenciesTestCase
extends JBossTestCase
{
protected static Logger staticLog =
Logger.getLogger(BootstrapDependenciesTestCase.class);
// Constants -----------------------------------------------------
public final static String bootstrapDependenciesTestMBeanName =
"org.jboss.test.deployers.jbas5349.sar.bootstrap.dependencies.test:service=BootstrapDependenciesTest";
public final static int expectedMBeanState = 3;
public BootstrapDependenciesTestCase(String name)
{
super(name);
}
/**
* Tests the status of deployment of testing SAR.
* If it fails, probably the deployment of a tested module included
in the SAR fails.
* See details in server's log.
*
* @throws Exception Description of Exception
*/
public void testDeploymentStatus() throws Exception
{
assertEquals(expectedMBeanState, checkMBeanState());
}
/**
* Checks the state of testing MBean.
*
* @exception Exception Description of Exception
*/
protected int checkMBeanState() throws Exception
{
Object state = invoke(new
ObjectName(bootstrapDependenciesTestMBeanName), "getState", null, null);
staticLog.debug("state=" + state);
return ((Integer) state).intValue();
}
}
Ivo, how is this supposed to work?
17 years, 2 months
Re: Snapshot dependencies
by Kabir Khan
Forwarding to Paul and dev list
On 7 Oct 2008, at 13:18, Kabir Khan wrote:
> No idea. I don't see those locally? We've only just been mavenised,
> so who knows, I might be missing something. How did you generate
> yours?
>
> [kabir@~/sourcecontrol/JBoss_AOP_2_0_0_CR18]
> $svn info
> Path: .
> URL: https://svn.jboss.org/repos/jbossas/projects/aop/tags/JBoss_AOP_2_0_0_CR18
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 79063
> Node Kind: directory
> Schedule: normal
> Last Changed Author: kabir.khan(a)jboss.com
> Last Changed Rev: 79063
> Last Changed Date: 2008-10-03 11:28:53 +0100 (Fri, 03 Oct 2008)
>
> [kabir@~/sourcecontrol/JBoss_AOP_2_0_0_CR18]
> $mvn dependency:analyze
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] JBoss AOP Parent POM
> [INFO] JBoss AOP Framework
> [INFO] JBoss AOP Pluggable Instrumentor
> [INFO] JBoss AOP Aspects
> [INFO] JBoss AOP AS Integration Core
> [INFO] JBoss AOP AS Integration JMX
> [INFO] JBoss AOP AS Integration MC
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> WAGON_VERSION: 1.0-beta-2
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP Parent POM
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [dependency:analyze]
> [INFO] Skipping pom project
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP Framework
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [dependency:analyze]
> [WARNING] Unused declared dependencies found:
> [WARNING] org.jboss.logging:jboss-logging-log4j:jar:
> 2.0.5.GA:compile
> [WARNING] junit:junit:jar:3.8.1:test
> [WARNING] jboss:jboss-test:jar:1.0.3.GA:test
> [WARNING] jboss.profiler.jvmti:jboss-profiler-jvmti:jar:
> 1.0.0.CR5:test
> [WARNING] log4j:log4j:jar:1.2.14:compile
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP Pluggable Instrumentor
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [dependency:analyze]
> [INFO] No dependency problems found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP Aspects
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [dependency:analyze]
> [WARNING] Unused declared dependencies found:
> [WARNING] junit:junit:jar:3.8.1:compile
> [WARNING] org.jboss.javaee:jboss-jca-api:jar:1.5.0.CR2:test
> [WARNING] org.jboss.javaee:jboss-servlet-api:jar:2.5.0.CR2:test
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP AS Integration Core
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [dependency:analyze]
> [WARNING] Used undeclared dependencies found:
> [WARNING] apache-xerces:xml-apis:jar:2.9.1:compile
> [WARNING] Unused declared dependencies found:
> [WARNING] org.jboss:jboss-common-core:jar:2.2.8.GA:compile
> [WARNING] org.jboss.jbossas:jboss-as-system-jmx:jar:
> 5.0.0.CR2:compile
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP AS Integration JMX
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [dependency:analyze]
> [WARNING] Used undeclared dependencies found:
> [WARNING] apache-xerces:xml-apis:jar:2.9.1:compile
> [WARNING] Unused declared dependencies found:
> [WARNING] org.jboss.aop:pluggable-instrumentor:jar:
> 2.0.0.CR18:compile
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building JBoss AOP AS Integration MC
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] [enforcer:enforce {execution: enforce-versions}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [dependency:analyze]
> [WARNING] Used undeclared dependencies found:
> [WARNING] org.jboss.integration:jboss-classloading-spi:jar:
> 5.0.0.CR2:compile
> [WARNING] apache-xerces:xml-apis:jar:2.9.1:compile
> [WARNING] org.jboss.cl:jboss-classloading:jar:2.0.0.Beta13:compile
> [WARNING] org.jboss.deployers:jboss-deployers-vfs-spi:jar:
> 2.0.0.Beta21:compile
> [WARNING] org.jboss:jboss-vfs:jar:2.0.0.CR1:compile
> [WARNING] org.jboss.deployers:jboss-deployers-core-spi:jar:
> 2.0.0.Beta21:compile
> [WARNING] org.jboss.deployers:jboss-deployers-client-spi:jar:
> 2.0.0.Beta21:compile
> [WARNING] Unused declared dependencies found:
> [WARNING] org.jboss.aop:pluggable-instrumentor:jar:
> 2.0.0.CR18:compile
> [INFO]
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] JBoss AOP Parent POM ..................................
> SUCCESS [5.811s]
> [INFO] JBoss AOP Framework ...................................
> SUCCESS [5.476s]
> [INFO] JBoss AOP Pluggable Instrumentor ......................
> SUCCESS [0.111s]
> [INFO] JBoss AOP Aspects .....................................
> SUCCESS [0.983s]
> [INFO] JBoss AOP AS Integration Core .........................
> SUCCESS [3.117s]
> [INFO] JBoss AOP AS Integration JMX ..........................
> SUCCESS [1.009s]
> [INFO] JBoss AOP AS Integration MC ...........................
> SUCCESS [0.903s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 20 seconds
> [INFO] Finished at: Tue Oct 07 13:15:03 BST 2008
> [INFO] Final Memory: 24M/43M
> [INFO]
> ------------------------------------------------------------------------
>
>
> On 7 Oct 2008, at 12:50, Dimitris Andreadis wrote:
>
>> Why AOP is bringing in those SNAPSHOT dependencies?
>>
>> [INFO] +- org.jboss.aop:jboss-aop-asintegration-core:jar:
>> 2.0.0.CR18:compile
>> [INFO] | \- org.jboss.jbossas:jboss-as-system-jmx:jar:5.0.0-
>> SNAPSHOT:compile (version managed from 5.0.0.CR2)
>> [INFO] | +- org.jboss.jbossas:jboss-as-main:jar:5.0.0-
>> SNAPSHOT:compile
>> [INFO] | | \- urbanophile:java-getopt:jar:1.0.9:compile
>> [INFO] | \- org.jboss.jbossas:jboss-as-system:jar:5.0.0-
>> SNAPSHOT:compile
>> [INFO] | \- org.jboss.jbossas:jboss-as-bootstrap:jar:5.0.0-
>> SNAPSHOT:compile
>> [INFO] +- org.jboss.aop:jboss-aop-asintegration-jmx:jar:
>> 2.0.0.CR18:compile
>> [INFO] | +- org.jboss.jbossas:jboss-as-j2se:jar:5.0.0-
>> SNAPSHOT:compile
>> [INFO] | \- org.jboss.jbossas:jboss-as-jmx:jar:5.0.0-
>> SNAPSHOT:compile
>> [INFO] | +- org.jboss.jbossas:jboss-as-j2se:test-jar:tests:
>> 5.0.0-SNAPSHOT:compile
>> [INFO] | \- org.jboss.jbossas:jboss-as-mbeans:jar:5.0.0-
>> SNAPSHOT:compile
>
17 years, 2 months
New Break the Build Policy - testsuite - discussion
by Adrian Brock
As many of you probably remember during the AS5 development
the testsuite ended up in a horrible state.
This problem was due to a snowball effect. Once one person
broke a few important tests, other developers didn't know
whether their changes also broke things.
I also suspect that people stopped caring about the testsuite
because they knew it was already broken.
We already have a policy that anybody who breaks
the compile or one of the smoke tests can expect to have
their commit rolled back.
Now, we want to extend the policy to the testsuite
as a whole.
The basic policy will be that once we have the Hudson
build running reliably at 100% any commit that breaks
a test can expect to be rolled back.
A branch will be created for the broken build
before rolling back so the commit(s) can be fixed
and tested before re-merging.
To keep things simple, rollbacks will be to the
revision that Hudson says was ok. This means
somebody fixing the build doesn't have to waste
time trying to analyse who broke the build
amongst multiple commits.
Obviously some common sense will be applied.
* If the fix is simple then it should be done
rather than rolling back
* The committer will be given a reasonable
amount time (e.g. until the next Hudson build)
to solve the issue
* We aren't going to rollback if it looks
like a spurious problem with the Hudson build
* If the failing test is one of those
known to be brittle.
e.g. some of the timer or asynchronous tests can fail
just because their wait()s are too short.
But these tests should be fixed anyway to
make them less prone to false negatives.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 2 months
Bulk updates in JIRA and fix versions
by Adrian Brock
If you're going to do bulk updates in JIRA can you remember
to uncheck the box so it doesn't send e-mail.
That way we don't all get mail bombed and
the e-mail servers don't grind to halt. :-)
I personally think bumping issues from release to release
is pointless. It gives a false impression to users
of what your roadmap is.
If you commit to a fix version, then you should deliver! ;-)
-------- Forwarded Message --------
From: Carlo de Wolf (JIRA) <jira-events(a)lists.jboss.org>
To: jira-notifications(a)jboss.com
Subject: [JBoss JIRA] Updated: (EJBTHREE-1328) Fixes for build-test.xml
Date: Fri, 3 Oct 2008 11:06:28 -0400 (EDT)
[ https://jira.jboss.org/jira/browse/EJBTHREE-1328?page=com.atlassian.jira.... ]
Carlo de Wolf updated EJBTHREE-1328:
------------------------------------
Fix Version/s: 1.0.0-Beta5
(was: 1.0.0-Beta4)
<snip/>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 2 months
AS 5 Testsuite doesn't complete
by Carlo de Wolf
The clustered configs aren't working because of:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
TransactionManager -> com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.internal.arjuna.utils.SocketProcessId_2] - SocketProcessId.getpid could not get unique port.
My guess is 78961 by jhalliday: Upgraded JBossTS to 4.4.0.GA, adding JTS elements in the process. JBAS-5919
I'm going to do a revert locally and another run of ejb3-testsuite. If that one is the culprit,
I'll vote roll back at that time.
Carlo
17 years, 2 months
