JBoss-4.0.5.GA update
by Dimitris Andreadis
Hello,
http://jira.jboss.com/jira/browse/JBAS
We are some 14 tasks away from the jboss 4.0.5.GA release. The initial
plan for this release was on the 29th/Sep, but I'm moving this to Monday
9th/Oct due to:
- QA in need of 1 week flat to perform the final QA / packaging, plus
specj performance/regression testing.
- Instability in the last week of testsuite runs with OOMEs that affect
the real fail rate, with otherwise succesful tests showing up as
failures.
The testsuite runs with jdk1.4 were in a very good shape a couple of
weeks ago (1 failure using the sun jdk, 6 failures with the jrockit
jdk), but now the results look a bit non-deterministic. My feeling is it
could be related to clustering configuration changes.
http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-sun-1
.4 (sun)
http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-1.4
(jrockit)
There is this task for testsuite runs on Solaris 10, for which I haven't
got any input yet.
http://jira.jboss.com/jira/browse/JBAS-3651
And the task to improve the ejb3 testsuite runs, if needed.
http://jira.jboss.com/jira/browse/JBAS-3582
So the drop-dead date for testsuite fixes and changes to Branch_4_0 is
Monday Oct/2nd (i.e. tag date). Please,
- Do no schedule more issues for 4.0.5.GA
- Help identify the OOMEs in the testsuite
- Help fixing failing tests in your area
- Finish with your tasks by Friday 29th
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI
d=12310181
Any questions/objections, let me know.
Thanks
/Dimitris
17 years, 7 months
RE: [JBoss-dev] httpd and tomcatClustering gives 404 during redeploy.
by Dimitris Andreadis
The scanner could use the MainDeployerMBean interface, or there could be
a DeployerExt extending Deployer, with the missing methods added.
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Jean-frederic Clere
> Sent: Friday, September 22, 2006 6:02 PM
> To: JBoss.org development list
> Subject: Re: [JBoss-dev] httpd and tomcatClustering gives 404
> during redeploy.
>
> On Fri, 2006-09-22 at 16:24 +0200, Sacha Labourey wrote:
> > What you are looking for is for what happens at line 391-392 here:
> >
> http://fisheye.jboss.org/browse/JBoss/jboss-system/src/main/org/jboss/
> > deployment/scanner/URLDeploymentScanner.java?r=1.1
>
> The problem is the URLDeploymentScanner uses the interface
> Deployer to reach MainDeployer.
> It is not possible to add a redeploy method to Deployer
> because that would break the interface (may be customer have
> their own Deployer).
> The undeploy method in Deployer is:
> void undeploy(URL url) throws DeploymentException; The
> information must be stored somewhere.
>
> Any hints?
>
> Cheers
>
> Jean-Frederic
>
> >
> > Jean-frederic Clere wrote:
> > > On Thu, 2006-09-21 at 07:27 -0700, Scott M Stark wrote:
> > >
> > >> Redeploy is not used during a hot-redeploy. The
> > >> URLDeploymentScanner simply does an undeploy/deploy the
> same as the redeploy in main.
> > >>
> > >
> > > Well URLDeploymentScanner only passes the URL, how do I get the
> > > information that it is a redeployement in MainDeployer?
> > >
> > > Cheers
> > >
> > > Jean-Frederic
> > >
> > >
> > >> Both
> > >> the scanner and main deployer need to be marking a
> deployment as in
> > >> the process of being redeployed. This should be
> propagated via the
> > >> DeploymentInfo and WebApplication.
> > >>
> > >> Sacha Labourey wrote:
> > >>
> > >>> That is what I mean: the MainDeployer could "share"
> this knowledge
> > >>> that it is a redeploy with any other piece of code,
> including the
> > >>> tomcatdeployer, by setting a temporary thread local
> variable that
> > >>> could be checked by any deployer.
> > >>>
> > >>> Jean-frederic Clere wrote:
> > >>>
> > >>>> On Thu, 2006-09-21 at 09:36 +0200, Sacha Labourey wrote:
> > >>>>
> > >>>>
> > >>>>> What about having the MainDeployer set a thread
> context variable
> > >>>>> indicating whether we are inside a "Redeploy" scenario?
> > >>>>>
> > >>>>>
> > >>>> MainDeployer knows that it is doing a redeploy(), the
> problem is
> > >>>> just that the redeploy() should also be in the
> TomcatDeployer or
> > >>>> that MainDeployer should tell to the TomcatDeployer that the
> > >>>> undeploy() is called for a redeploy() (like
> undeploy(false) for a
> > >>>> redeployement and
> > >>>> undeploy(true) for an undeployement).
> > >>>>
> > >>>> Cheers
> > >>>>
> > >>>> Jean-Frederic
> > >>>>
> > >>>>
> > >> _______________________________________________
> > >> jboss-development mailing list
> > >> jboss-development(a)lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/jboss-development
> > >>
> > >
> > > _______________________________________________
> > > jboss-development mailing list
> > > jboss-development(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/jboss-development
> > >
> > >
> >
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
17 years, 7 months
