-dain
On Friday, December 6, 2002, at 07:01 PM, Peter Fagerlund wrote:
If You aspire to run 24/7/365 it would become a problem in a "real" situation ... Yes - The idee is to be able to change any part of the running system with the "new" desired deploy configuration, at any time also the microkernel when phase'sing a tree phase restart JbossMC:ContainerComponents:Deployments. -- Now in a production scenario striving for 90+ % uptime ... You would typically use a hardware separate box to FW/LB in front to help today ... tomorrow You might just hot-swap any part for another at any time ... "Container wise" ... is/was a goal ... That could theoretically happen today in a clustered scenario ... --- We have just not tested it ...
/peter_f
l�rdagen den 7 december 2002 kl 00.25 skrev Hunter Hillegas:
I'm happy to file a bug report if y'all actually see this as a bug...
Should the deployment mechanism be able to sort out this kind of tampering
and redeploy everything correctly? I mean, it would be quite nice but it
seems like the case I presented isn't often to occur in any real
situation...
Hunter
From: Peter Fagerlund <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Sat, 7 Dec 2002 00:03:44 +0100 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Interesting Deployment Ordering "Issue"Please file a bug report ! or else i have to ,-) ... yes i found some things not working when it comes to "internal components" redeploying since We tend to mostly focus on application (re)deploy ... a simple ex. run jb -> do a db/ds test -> redeploy db/ds - do a db test : will fail in my tests ... /peter_f fredagen den 6 december 2002 kl 19.47 skrev Hunter Hillegas:Not sure if this is really even an issue, since it sprang up from a
very
unnatural case...
We're testing to find a problem with our app and Jetty... I'm
hypothesizing
that a script is "touch-ing" all the files under the JBoss tree...
When I do a "touch *" under the deploy directory, total chaos ensues. I
assume the wildcard orders by name, alpha... Well, this totally fscks
everything as things undeploy and redeploy in that order. When the dust
settles, basically nothing works.
I'm not filing this as a bug since it probably is what you should
expect if
you are silly enough to do something like "touch *" in deploy... Kind
of
interesting though...
Gotta go kick the guy that wrote the backup script that was doing that.
hunter
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
