× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mike E wrote:

> But seriously, how do you get around that?  If I'm running
> just a single appserver instance, I'm pretty much screwed.
> I have to take down all of my apps to fix one.  If I'm
> running clustered appservers, can I take each one
> down individually and deploy the fix while the others
> are handling incoming requests?

Yes.  I ran multiple server instances and could shut one down without the
others noticing.
I have deployed individual fixes to WAS 3.5 and 4 without ever having to
shut down the server instance.  If you chose to do it manually by copying
JSP/servlets into the WAS file system it can be a chore, but you can readily
write a script to do it, even in CL.

There are those who say that requiring a manual deploy is the sign of a
'standard in progress' and I might just agree with that assessment.  But I
just wanted to let you know that it is possible to deploy a bug fix without
disrupting  the folks on the other side of the glass.  My guess is that
vendors will fill in the gap that the J2EE folks left in the process.
  --buck




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.