>From what I have seen you are having issues with a single _javascript_ action not the entire server's stability. The _javascript_ action is in fact an interface to the _javascript_ engine (dll/dylib) written by Netscape. T2K and Witango 5.0.x use the version 1.x engine which is not completely thread safe and it also suffers from a lot of exceptions like divide by zero errors. If the _javascript_ library crashes, it will also drag down the witangod process as it gets loaded into the witangod processes memory space. All development on the version 1.4 library ceased several years ago (back in 1999) and the version 1.5 library was never finished.
Now I am not saying that every script action will crash the _javascript_ library so you do not need to rewrite all you script actions if they are not crashing. The main point is that functionality and load do strange things to software especially when written and tested on HW that was typically a PII350 and especially when run on todays faster machines with a server that is now preemptively threaded.
The _javascript_ 1.4 library was written before Redhat 7, Windows 2000 and Mac OS X, G4/G5/P4 processors and GCC3 compiler. We are currently investigating updating the _javascript_ functionality to use SpiderMonkey for inclusion in a future release of the Witango Server - http://www.mozilla.org/js/spidermonkey/ . SpiderMonkey is the _javascript_ engine used in the Mozilla browsers and although it still has some issues it is technology that has active development and has been developed for a "modern" OS, HW and compiler.
If using the 1.x _javascript_ library is crashing the witangod process the only work around currently is to not use it for the particular functionality that crashes it and use the meta language to provide the same functionality. The main use of the _javascript_ engine that I have seen is for verifying data is a particular type or format. Much of this functionality can now be replaced by metatags like @ISNUM, @ISALPHA, @ISDATE, etc and @REGEX. The Regex engine has been updated in the 5.0.1.065 build and should be able to be used to verify data like email addresses, phone numbers, etc, quickly and easily. For example you can do a simple check that an email address is correctly formatted ([EMAIL PROTECTED]) with the following metatag combination.
<@IF "<@NUMROWS array='<@REGEX EXPR="[EMAIL PROTECTED]" STR="<@arg email>" TYPE=E>'>">
If needed you could use @REGEX to strip out the 2nd or top level domain and check it is part of a list or particular length as well.
Also when you find a reproducible issue email a test case to us of the functionality that crashes the server along with a procedure to crash the server with the test case. The same holds for memory leaks. If you can identify the functionality that is causing the memory leak send us a test case and procedure so that it can be fixed in a future release. Most of the crashes we fix are from test cases that are sent to us and are normally from a real world solution.
Phil
On 12/2/04 12:18 PM, "Customer Support" <[EMAIL PROTECTED]> wrote:
>
>
> Begin forwarded message:
>
>> From: John McGowan <[EMAIL PROTECTED]>
>> Date: 12 February 2004 1:21:50 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: Witango-Talk: Tango Memory Leaks
>> Reply-To: [EMAIL PROTECTED]
>>
>> If you've never heard of the "watchdog" you're behind.
>>
>> If you're still running the "watchdog" you're also behind.
>>
>> It was a service running with T2K that would give the "illusion of
>> stability" by restarting the T2K process if it ever stopped.
>>
>> Kinda like the "procautostart" process I'm using to give the illusion
>> of stability on my Linux Witango 065 Server. Which crashes several
>> times a day due to the use of the Script action.
>>
>> /John
>>
>> Steve Campbell wrote:
>>
>>> Maybe I am so behind with versions, but "watchdog", can someone
>>> educate
>>> me? IF need be then yes, do it off list.
>>>
>>> Thanks
>>> Steve
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Fogelson, Steve [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, February 10, 2004 4:11 PM
>>> To: '[EMAIL PROTECTED]'
>>> Subject: RE: Witango-Talk: Tango Memory Leaks
>>>
>>> I tried the following on Tango 2000
>>>
>>> Net stop "Tango 2000 Server"
>>> Net start "Tango 2000 Server"
>>>
>>> Worked fine except the watchdog restarted the Tango server before I
>>> could do
>>> my maintenance.
>>>
>>> Any way to prevent this?
>>>
>>> Thanks
>>>
>>> Steve Fogelson
>>> Internet Commerce Solutions
>>>
>>> -----Original Message-----
>>> From: Bengt Bredin [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, February 10, 2004 10:08 AM
>>> To: [EMAIL PROTECTED]
>>> Subject: SV: Witango-Talk: Tango Memory Leaks
>>>
>>>
>>>
>>> Hi !
>>>
>>> I just created a bat file with two lines:
>>> Net stop "witango server 5"
>>> Net start "witango server 5"
>>> Then use the W2K Scheduler to set up a routine that calls the bat
>>> file. Seems to work fine.
>>>
>>> Bengt
>>>
>>>
>>>
>>> -----Ursprungligt meddelande-----
>>> Från: Steve Campbell [mailto:[EMAIL PROTECTED] Skickat: den 10
>>> februari 2004 16:36
>>> Till: [EMAIL PROTECTED]
>>> Ämne: RE: Witango-Talk: Tango Memory Leaks
>>>
>>> I am interested in this as well. Thanks
>>>
>>> Steve
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Peter Ternström [mailto:[EMAIL PROTECTED] Sent: Tuesday,
>>> February 10, 2004 6:45 AM
>>> To: [EMAIL PROTECTED]
>>> Subject: Re: Witango-Talk: Tango Memory Leaks
>>>
>>> Cool!
>>>
>>> could you tell me how to do this? I would like to restart tango server
>>> every
>>> night, due to memory leak problems.
>>>
>>> Kind regards
>>> Peter
>>>
>>>
>>> ----- Original Message ----- From: "RJ Hendrickson"
>>> <[EMAIL PROTECTED]>
>>> To: "Multiple recipients of list witango-talk"
>>> <[EMAIL PROTECTED]>
>>> Sent: Saturday, April 06, 2002 9:10 PM
>>> Subject: Re: Witango-Talk: Tango Memory Leaks
>>>
>>>
>>> You can use the W2K Scheduler to set up a routine to reset Tango
>>> automatically on a daily basis, or as often as you like if you don't
>>> want
>>> to have to worry about doing it manually.
>>>
>>> RJ
>>>
>>> At 04:33 PM 4/1/2002, you wrote:
>>>
>>>> Unfortunately, I have found to have similar memory leaks in tango
>>>>
>>> 4.05.047.
>>>
>>>> with apache. The leak occurs on windows 2000 and linux and mac. On my
>>>> win2000/apache or linux apache systems, I can slowly watch the memory
>>>>
>>> usage
>>>
>>>> creap up, and my windows 2000 servers will crash occasionally due to
>>>>
>>> it. I
>>>
>>>> am sure it is tango, because if I just restart the tango service, the
>>>>
>>> memory
>>>
>>>> goes back to normal. As long as I restart the tango server every
>>>> couple
>>>>
>>> of
>>>
>>>> days, no problems. The linux machines will restart the tango daemon
>>>> by
>>>> itself when the memory gets out of hand.
>>>>
>>>> I use a lot of binary library applications with tango, which means I
>>>> am
>>>> pulling large amounts of binary data from PrimeBase SQL, and I think
>>>>
>>> that
>>> is
>>>
>>>> why I see this problem more pronounced than others.
>>>>
>>>> --
>>>>
>>>> Robert Garcia
>>>> BigHead Technology
>>>> 21053 Devonshire Suite 206
>>>> Chatsworth, Ca 91311
>>>> Phone 818.773.8162
>>>> Fax 818.773.8164
>>>> http://www.bighead.net/
>>>> [EMAIL PROTECTED]
>>>>
>>>>
>>>>
>>>>> From: Jose Kuhn <[EMAIL PROTECTED]>
>>>>> Reply-To: [EMAIL PROTECTED]
>>>>> Date: Wed, 20 Mar 2002 14:03:57 -0500
>>>>> To: Multiple recipients of list witango-talk
>>>>>
>>> <[EMAIL PROTECTED]>
>>>
>>>>> Subject: Re: Witango-Talk: Trying to make plans - Mac, Web*, Tango
>>>>> projections
>>>>>
>>>>> Hello!
>>>>>
>>>>> Both, Robert Garcia and myself are huge Mac heads but we have both
>>>>> temporarily moved to WiTango 2k Windows 2K running with Apache(Due
>>>>>
>>> to
>>> the
>>>
>>>>> memory leak in the Tango Webstar Plug in). We also use PrimeBase as
>>>>>
>>> our
>>> SQL
>>>
>>>>> Database. There is a memory leak in the Webstar Plug in Witango 2k.
>>>>>
>>> I
>>>
>>>> would
>>>>
>>>>> wait until this summer when Witango 5 comes out. Witango 5 will not
>>>>>
>>> run
>>> on
>>>
>>>>> Mac OS 9. According to Phil, there will be a Webstar 5 plug-in as
>>>>>
>>> well
>>> as
>>>
>>>>> the usual Apache Plug-in for Mac OS X. It runs fabulously with
>>>>>
>>> Apache.
>>>
>>>>> Primebase flies on Mac OS X (IT's slow on Mac OS 9.) You can
>>>>>
>>> download a
>>>
>>>> free
>>>>
>>>>> developer's version from http://www.Primebase.com.
>>>>>
>>>>> BTW Robert's http://www.bighead.net company is a Primebase
>>>>>
>>> Distributor.
>>> You
>>>
>>>>> can Run Primebase from everything from Mac OS 9/X to Solaris/AIX
>>>>>
>>>>> Jose
>>>>>
>>>>> on 3/20/02 11:51 AM, Joe Terrasi at [EMAIL PROTECTED]
>>>>>
>>> wrote:
>>>
>>>>>> I currently use WebSTAR/Tango2k/Filemaker on a classic Mac
>>>>>>
>>> (actually,
>>>
>>>>>> the FileMaker is on a different box).
>>>>>>
>>>>>> What are anybody's thoughts on how I should upgrade?
>>>>>>
>>>>>>
>>>>>> I wouldn't mind moving to an OSX box if necessary.
>>>>>>
>>>>>> I would love to scrap FileMaker all together (unless performance
>>>>>>
>>> can
>>>
>>>>>> be improved).
>>>>>>
>>>>>> I REALLY want to stay with Tango.
>>>>>>
>>>>>> I would like to stay with WebSTAR if possible, but I could possibly
>>>>>>
>>>> switch.
>>>>
>>>>>> What will be my best solution in the next 6 months-1 year? What
>>>>>> database will serve me well? I also have a lot of forms/labels to
>>>>>> print from the data - do I need a separate reports package?
>>>>>>
>>>>>> Sorry if these are basic questions, but I'd love your collective
>>>>>>
>>> input.
>>>
>>>>>> Thanks!!
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
