atomic collections
by Ales Justin
In MC's Deployers I found a couple of usages where I would need two+
steps on a Collection/Map to be atomic in this next sense:
Collection<T> addAllAndClear()
{
Collection<T> target = new HashSet<T>();
synchronize(delegate)
{
target.addAll(delegate);
delegate.clear();
}
return target;
}
Does it make sense to introduce something like this in jboss-common
or should this just be handled locally in the project via some helper
methods?
Or is AtomicCollection in order?
e.g.
public interface AtomicCollection<E> extends Collection<E>
{
/**
* Add all and clear.
*
* @return new copy
*/
Collection<E> addAllAndClear();
// TODO - add more 'atomic' ops here
}
16 years, 3 months
Re: jbossmx and mc's system-jmx
by Adrian Brock
Please keep it on the mailing lists.
On Mon, 2009-02-23 at 14:17 +0100, Ales Justin wrote:
> Is MC part in system-jmx going here as well?
>
No. Once I've plit out jbossmx, I'm going to create a jmx-mc-int in the
MC project. That will only be a part of system-jmx (the service
controller). The jmx deployer(s) can then move to the deployers project.
They'll still likely be a few things left in system-jmx that
are AS specific, e.g. the barrier controller.
But I'll explain it better as I do the different stages.
e.g. One of my aims is to allow to people boot the ServiceController
using the JDK's MBeanServer rather than JBossMX.
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 23 Feb 2009 07:56:50 -0500
> > From: jboss-cvs-commits(a)lists.jboss.org
> > Subject: [jboss-cvs] JBossAS SVN: r84614 - trunk and 1 other
> > directory.
> > To: jboss-cvs-commits(a)lists.jboss.org
> > Message-ID: <E1LbaMc-0002Wz-32(a)committer01.frg.pub.inap.atl.jboss.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Author: adrian(a)jboss.org
> > Date: 2009-02-23 07:56:49 -0500 (Mon, 23 Feb 2009)
> > New Revision: 84614
> >
> > Added:
> > projects/jbossmx/mbeans/
> > Removed:
> > trunk/mbeans/
> > Log:
> > [JBMX-1] - factored out jbossmx project
> >
> > Copied: projects/jbossmx/mbeans (from rev 84613, trunk/mbeans)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
16 years, 3 months
Continuing Maven migration
by Paul Gier
I'd like to continue with the Maven migration of the app server build. So
starting next week, I will be switching over one or two modules at a time in the
order that they are currently built.
So for example, the first to switch will be the "bootstrap" module followed by
the "main" module. The build/build.sh file will call maven to run the mavenized
modules first, and then continue with the non-mavenized modules. That way the
later modules can depend on the output of the earlier mavenized modules.
Once a module has been mavenized and is working without any issues, I will
remove the build.xml file from the directory, and you will have to build using
maven.
Please let me know of questions or concerns.
16 years, 3 months
AS 5.1 Component Project Schedule
by Jason T. Greene
Project Leads,
The next planned AS release is 5.1 Beta which we are targeting for a
March release, and a following GA in April (provided no major problems).
I need to know what versions of your respective components you would
like included in this release. These would preferably be of CR or better
quality, although a beta release may be OK if you are confident you can
get a GA shortly thereafter. It would also be helpful if you could limit
the scope of whatever version you are targeting for AS inclusion to be
the features that benefit AS.
Keep in mind that we are transitioning to a frequent release cycle for
the AS, so there is no need to rush your project to make this release.
The more stable the project releases are, the less time it takes getting
the AS ready to release.
Thanks!
--
Jason T. Greene
JBoss, a division of Red Hat
16 years, 3 months
No more snapshots in 5.0!
by Jason T. Greene
We need to stop using snapshots in this Branch, as it's making it
difficult for everyone to figure out why their tests are suddenly
breaking. As an example, Brian is now trying to find the cause of a
deadlock issue that just appeared on a testrun without any changes occuring.
We need to use releases so that a test run can be correlated to a
component change. Even if you don't call it an official release, just
make up something like M132 or Beta17, etc.
--
Jason T. Greene
JBoss, a division of Red Hat
16 years, 3 months
AS 5.1 Beta 1 Code Freeze (and other release dates)
by Jason T. Greene
5.1 Beta1
---------
Code Freeze: March 9th
Release: March 16th
The primary/required goal for this release is completion of all Profile
Service blockers, to facilitate the inclusion of the console:
https://jira.jboss.org/jira/browse/JBAS-6470
All other planned component updates for this release are located here:
https://jira.jboss.org/jira/browse/JBAS-6156
If one of these subtasks is assigned to you, and you can not complete
this in *2 weeks*, please let me know, so I can reschedule it to CR1.
Also please review the JIRA issues assigned to you and reschedule them
if you can not complete them for this release.
5.1 CR1
-------
Code Freeze: April 6th (Tentative)
Release: April 13th (Tentative)
The primary/required goal is inclusion of the embedded console. A
secondary goal is including JBM 2 as either an optional or main JMS
provider. These dates could slip a few more weeks depending on the
console timeline.
All major component upgrades need to be completed and in CR quality for
this release (with the exception of tech preview features.
5.1 GA
------
Code Freeze: May 4th (Tentative)
Release: May 18th (Tentative)
The primary/required goal is of course all tests (including TCK) cleared
and all assigned bugs resolved.
Any questions, feedback?
--
Jason T. Greene
JBoss, a division of Red Hat
16 years, 3 months
Be extra careful when changing/using base libraries.
by Dimitris Andreadis
I think the type of testsuite/tck failures we have been experiencing the last couple of
weeks are indicative of how important those base libraries are (VFS/MC/Deployers/etc.)
Although APIs may look constant it is inevitable that users of this code will depend on
internal implementation details or specific dynamic behavior (e.g. threading invariances).
So the lessons to be learned here are:
- Be extra careful and conservative when changing base libraries. Local testing will almost
certainly not reveal all the possible runtime outcomes and uses of the base library.
- Good integration testing should always take place higher up the chain, either through some
temporary Beta/CR release, or a versioned snapshot. E.g when changing jboss-common, the
change might work for you but not for the other 15 projects using it.
- Do your homework when using APIs from other projects. Ask for best practices in the
forums, the authors are there to help.
Looking at the stream of commit messages in the base project often gives me the shivers. It
could be I'm just getting older but at the same time you need to remember that AS5 is
already GA and should be treated as such.
/Dimitris
16 years, 3 months
Re: [jboss-dev] AS 5.1 Beta 1 Code Freeze (and other release dates)
by Charles Crouch
Please see comments inline
Thanks
Charles
----- "Jason T. Greene" <jason.greene(a)redhat.com> wrote:
> 5.1 Beta1
> ---------
> Code Freeze: March 9th
> Release: March 16th
Last I heard the release date was March 10th? Did this move or was the 10th tentative?
>
> The primary/required goal for this release is completion of all
> Profile
> Service blockers, to facilitate the inclusion of the console:
> https://jira.jboss.org/jira/browse/JBAS-6470
>
> All other planned component updates for this release are located
> here:
> https://jira.jboss.org/jira/browse/JBAS-6156
>
> If one of these subtasks is assigned to you, and you can not complete
>
> this in *2 weeks*, please let me know, so I can reschedule it to CR1.
>
> Also please review the JIRA issues assigned to you and reschedule them
>
> if you can not complete them for this release.
>
> 5.1 CR1
> -------
> Code Freeze: April 6th (Tentative)
> Release: April 13th (Tentative)
>
> The primary/required goal is inclusion of the embedded console. A
> secondary goal is including JBM 2 as either an optional or main JMS
> provider. These dates could slip a few more weeks depending on the
> console timeline.
We're planning the console release right now, but I would expect a move to the right of several weeks from the dates you have above (assuming the Beta1 dates don't change). We should have a firm console schedule early next week.
>
> All major component upgrades need to be completed and in CR quality
> for
> this release (with the exception of tech preview features.
>
> 5.1 GA
> ------
> Code Freeze: May 4th (Tentative)
> Release: May 18th (Tentative)
>
> The primary/required goal is of course all tests (including TCK)
> cleared
> and all assigned bugs resolved.
>
>
> Any questions, feedback?
>
>
> --
> Jason T. Greene
> JBoss, a division of Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
16 years, 3 months
