Just a follow up to this old thread:

By looking at the sources of ERXConfigurationManager I found the following info 
in the javadoc comment of the method configureRapidTurnAround():

"[…] Rapid turnaround mode will only be enabled if […] system has WOCaching 
disabled."

I can't remember why but I used to uncheck "Caching enabled" on my deployed 
instances so perhaps it's time to get rid of some ol' habbits. After changing 
that setting I still get the rapid turnaround error in the logs. The only way 
to get rid of these log entries was to explicitly set '-WOAllowRapidTurnaround 
NO' as an additional argument. Shouldn't WO automatically detect that it is not 
in development mode, how does WO determine that it is in deployment mode?

I deploy using JavaMonitor (the Apple stock version), WO 5.4.3, OS X Server 
10.5.8, apps all fully embedded using Wonder and apparently all apps are 
started in development mode as I get a line 'WODisplayExceptionPages=true' in 
my log file where the official Application Properties doc 
(http://developer.apple.com/legacy/mac/library/documentation/WebObjects/WOAppProperties/WOAppProperties.pdf)
 states that "[…]  The default value is true in development mode and false in 
deployment mode."

jw


Am 14.08.2009 um 09:16 schrieb Johann Werner:

> Hi Frank,
> 
> Am 22.04.2009 um 21:51 schrieb Mr. Frank Cobia:
> 
>> Never mind. My mind is not working today. I am working in a deployment 
>> environment and I saw that error on the command line and assumed that was my 
>> problem. I looked in the log file and found an error that made more sense. I 
>> did not realize that error was not actually something that would stop the 
>> app from running.
>> 
>> What tells WebObjects that it is in a rapid turnaround environment so that I 
>> can get rid of this?
> 
> did you find an answer on that matter? I have a new Xserve and everytime I 
> start an app I get an e-mail with that error (I use log4j's SMTP appender). 
> Sort of annoying.
> 
> jw
> 
>> 
>> Thanks,
>> Frank
>> 
>> 
>> On Apr 22, 2009, at 3:46 PM, Mike Schrag wrote:
>> 
>>> wait, what are you talking about production? rapid turnaround isn't used in 
>>> production ... this is only for development mode.  that is also not a 
>>> crashing exception, it's just a log error, though i don't know how you 
>>> managed to get it talking about rapid turnaround in a deployment scenario
>>> 
>>> On Apr 22, 2009, at 3:43 PM, Mr. Frank Cobia wrote:
>>> 
>>>> So I need pb.proj files to deploy for production on an XServe?
>>>> 
>>>> I tried this and it does not seem to help.
>>>> 
>>>> Thanks,
>>>> Frank
>>>> 
>>>> 
>>>> On Apr 22, 2009, at 3:35 PM, Mike Schrag wrote:
>>>> 
>>>>> you either have to have eclipse generate pb.proj/xcodeproj files (it's in 
>>>>> the wolips build settings) or you need to use the _WOLipsProject stuff 
>>>>> (that isn't quite officially a public thing) ..
>>>>> 
>>>>> ms
>>>>> 
>>>>> On Apr 22, 2009, at 3:30 PM, Mr. Frank Cobia wrote:
>>>>> 
>>>>>> I have several applications that I just rebuilt and installed where they 
>>>>>> were already working but now they die with the message:
>>>>>> 
>>>>>> Apr 22 15:24:34 Bids[2002] (_PBXProjectWatcher.java:532) ERROR 
>>>>>> com.webobjects._ideservices._PBXProjectWatcher  - Cannot use rapid 
>>>>>> turnaround.  Please start Project Builder and open the project for this 
>>>>>> application.
>>>>>> 
>>>>>> 
>>>>>> I saw that some people had said to check the host name and "changeip 
>>>>>> -checkhostname" says everything is okay and I tried adding -WOHost to 
>>>>>> the command line for th app, but I am still getting the same error.
>>>>>> 
>>>>>> Does anyone know what causes this?
>>>>>> 
>>>>>> Thanks,
>>>>>> Frank

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to