You could just remember when you started it, rearrange your whole concept of
space and time around m.  Thus you'd say, I ate lunch at x cycles since I
started JBoss.  Then you could politely ask the world to adopt this new form
of time.  Thus you'd know every m on the m you best not deploy but it would
be fine to deploy slightly after the m.

Though perhaps the other solutions or chance and retry is more pragmatic ;-)

> From: Lee Haslup <[EMAIL PROTECTED]>
> Reply-To: "Research Triangle Java User's Group mailing
> list."<[EMAIL PROTECTED]>
> Date: Wed, 19 May 2004 12:23:13 -0400
> To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]>
> Subject: Re: [Juglist] Remote deployment to Websphere Application Server?
> 
> Of course that just improves your odds since it can still scan during
> your FTP upload.  If the upload takes n seconds and it scans every m
> seconds then your chance of getting whacked are n/m.  Increasing m helps
> but it can't drive the chance to zero.
> 
> [EMAIL PROTECTED] wrote:
> 
>> Well you could also just increase the time between scans.  (default is 5
>> seconds, its the last entry in server/xxx/conf/jboss-service.xml)
>> 
>>  
>> 
>>> From: Phillip Rhodes <[EMAIL PROTECTED]>
>>> Reply-To: [EMAIL PROTECTED], "Research Triangle Java User's Group
>>> mailing list."<[EMAIL PROTECTED]>
>>> Date: Wed, 19 May 2004 00:42:57 -0400
>>> To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]>
>>> Subject: Re: [Juglist] Remote deployment to Websphere Application Server?
>>> 
>>>    
>>> 
>>>> Im following the thread bec im using Jboss. if im
>>>> going to automate this, ill use the FTP ant task, but
>>>> im not sure if you can do a "move" after the FTP (can
>>>> you)?. 
>>>>      
>>>> 
>>> Not having an easy way to automate the move on the
>>> other end is the main reason I don't even worry about
>>> it.  Deployments are infrequent enough, and FTP
>>> direct to the deploy dir works well enough most of the time,
>>> that I find it to be a non-issue in practice.
>>> 
>>> Yeah, occassionally I'll get an IOException complaining
>>> about "unexpected end of zlib input stream." So I re-FTP
>>> the file, and 99 times out of 100 it deploys fine the
>>> second time...
>>> 
>>> possibly in the future as the ear files get bigger
>>> and bigger, it will become an issue... if so I'll
>>> deal with it then. :-)
>>> 
>>> Just my $00.02 worth...
>>> 
>>> TTYL,
>>> 
>>> Phil
>>> 
>>> _______________________________________________
>>> Juglist mailing list
>>> [EMAIL PROTECTED]
>>> http://trijug.org/mailman/listinfo/juglist_trijug.org
>>>    
>>> 
>> 
>> 
>> _______________________________________________
>> Juglist mailing list
>> [EMAIL PROTECTED]
>> http://trijug.org/mailman/listinfo/juglist_trijug.org
>> 
>> 
>> 
>>  
>> 
> 
> 
> 
> _______________________________________________
> Juglist mailing list
> [EMAIL PROTECTED]
> http://trijug.org/mailman/listinfo/juglist_trijug.org


_______________________________________________
Juglist mailing list
[EMAIL PROTECTED]
http://trijug.org/mailman/listinfo/juglist_trijug.org

Reply via email to