Thanks everyone,
Ive decided to reprogram my application into using custom scoped vars and objects. If it works (i really hope it does) ill buy you guys a drink.
Peter
----- Original Message ----- From: "Scott Cadillac" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 11, 2004 4:45 PM
Subject: RE: Witango-Talk: application vars timing out
Hi Peter,
Ben is write, this works for Custom Scope too, to prevent timeout and used to work for Application Scope as well (it might still).
<@ASSIGN NAME=variableTimeout SCOPE=myCustom VALUE=0>
I've used Custom Scope for years, and never found a problem with it.
Cheers....
Scott Cadillac, XML-Extranet ~ 403-254-5002 ~ [EMAIL PROTECTED] ------------ Well-formed Programming in C# ASP.NET, Witango and XML For Hire ~ http://xmlx.ca/forhire ------------ IExtranet ~ http://IExtranet.net ------------ Weblog ~ http://xmlx.ca Forums ~ http://forums.xmlx.ca Knowledge Base ~ http://kb.xmlx.ca ------------ P.O. Box 69006 RPO Bridlewood SW Calgary, Alberta Canada T2Y 4T9
-----Original Message----- From: Peter Ternstr�m [mailto:[EMAIL PROTECTED] Sent: Thursday, November 11, 2004 8:28 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: application vars timing out
That is very interesting! Thanks.
Peter
----- Original Message ----- From: Ben Johansen <mailto:[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 4:22 PM
Subject: RE: Witango-Talk: application vars timing out
Have you tried this?
To change the expiry timeout period for domain variables only, assign the desired value to variableTimeout in domain scope. For example, to specify that domain scope variables never expire, make the following assignment:
<@ASSIGN NAME=variableTimeout SCOPE=application VALUE=0>
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-----Original Message----- From: Peter Ternstr�m [mailto:[EMAIL PROTECTED] Sent: Thursday, November 11, 2004 7:59 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: application vars timing out
Hello again,
Im on windows, both server and development. As custom scopes timeout(?),
this is not an option. I need the app vars and objects to be available all
the time, from server startup to infinity. Ive sent a request to
[EMAIL PROTECTED] I cant wait for a clarification in this matter.
I dont mean to be rude puking application vars all over this list. Im quite
frustrated over this since server uptime is vital for our companys
reputation.
Peter
----- Original Message -----
From: "Dan Stein" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 11, 2004 3:10 PM
Subject: Re: Witango-Talk: application vars timing out
Peter understood.
I was just suggesting something very painless since you can just do a find a
replace on the whole project to change application scopes to whatever you
name the custom scope to be.
I agree it should not be happening and the server should not be crashing and
failing to restart.
I missed the beginning of this are you on Mac or windows?
I have not found a problem with custom scopes timing out.
on 11/11/04 2:23, Peter Ternstr�m at [EMAIL PROTECTED] wrote:
>
> I upgraded from 5.065 to 5.5 hoping to solve this issue. So, the problem
> exists in both versions. Im not going to re-program our entire application
> to use custom scope vars instead of application vars, just because to find
> another bug or undocumented feature in witango application server. Im
> hoping
> with can solve this issue as soon as possible so we can start using their
> software as stated in the manual. Until then - it is server watch for us.
> Guess what? Server crashed this night, too! For no apparent reason. Im so
> tired of this.
>
> Peter
>
> ----- Original Message -----
> From: "Dory" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, November 11, 2004 1:01 AM
> Subject: Re: Witango-Talk: application vars timing out
>
>
> I don't know about Peter, but my situation is occurring with 5.065, so
> it wouldn't appear to be a problem exclusive to 5.5. Witango support
> is currently researching the issue with me, so if I find out anymore
> I'd be happy to share.
>
> On Wed, 10 Nov 2004 18:57:36 -0500, Dan Stein <[EMAIL PROTECTED]> wrote:
>> Peter,
>>
>> Did this problem happen with with 5.065. Can you roll back to that to see
>> if
>> it is a 5.5 problem?
>>
>> Could there be memory issues are you running out of memory to store the
>> variables from all the different scopes.
>>
>> As a work around have you tried just loading these as a custom scope. If
>> I
>> remember right these will function just like and application scope.
>>
>> I use these when I need them and my ISP does not allow application scope.
>>
>> Dan
>>
>>
>>
>> on 11/10/04 2:18, Peter Ternstr�m at [EMAIL PROTECTED] wrote:
>>
>>> Hello all,
>>>
>>> we're having the exact same problem - application vars and objects
>>> stored in
>>> application scope time out and our application seizes to work properly.
>>> This
>>> is a major issue for us, since we are hosting about 140 communities on
>>> the
>>> web and noone can log in. We have tried to solve this by checking if app
>>> vars are existant upon login, but this ultimately (after a number of
>>> logins,
>>> usually once every couple of days) causes a server crash caused by
>>> reloading
>>> application vars and objects stored in application scope discussed in
>>> other
>>> threads of witango talk.
>>>
>>> In fact, this is such a big problem for us, that we are looking for
>>> other
>>> program languages for our application. The program language and
>>> application
>>> server HAS TO WORK ACCORDING TO THE MANUAL. Otherwise our developers
>>> have
>>> guess what functionality witango really supports, and all time to try to
>>> build an app "by the book" is lost.
>>>
>>> We would really like some input from you guys and with on this issue. We
>>> are
>>> strung in a situation where at least one of us has to keep an eye on the
>>> server and reload app vars if necessary- 24/7. Maybe it is a
>>> configuration
>>> problem on our side? We only run one application, thus have not
>>> configured
>>> other applications in applications.ini than "default". (Yes, we have
>>> tried
>>> to configure another application, but still same result - loss of app
>>> vars).
>>>
>>> Is anyone out there using application vars at all? Do you have the same
>>> problem? Is there a solution?
>>>
>>> We are running Win 2003, Apache 2.049, SQL 7 (on separate server), and
>>> Witango 5.5.
>>>
>>> Grateful for all input!
>>> Peter
>>>
>>> ----- Original Message -----
>>> From: "Dory" <[EMAIL PROTECTED]>
>>> To: <[EMAIL PROTECTED]>
>>> Sent: Tuesday, October 26, 2004 12:41 AM
>>> Subject: Witango-Talk: application vars timing out
>>>
>>>
>>>> We are experiencing 2 problems:
>>>>
>>>> 1. It appears that our application variables are timing out after the
>>>> system variabletimeout period. On page 349 of the Witango 5
>>>> Programmer's Guide.pdf, it says that application variables NEVER time
>>>> out, yet ours do. I tried to resolve this by setting the
>>>> variabletimeout trigger which on page 485 of the same document says
>>>> that we can set that var in the application scope. When I try this I
>>>> get this error, "You may not set the configuration variable
>>>> (variabletimeouttrigger) in the (application) scope".
>>>>
>>>> The document says I am able to set this, yet I am not able to. Is
>>>> there a way I can set this var in the application scope? How do I stop
>>>> my application vars from timing out rather than just setting the
>>>> system variabletimeout to a really huge number?
>>>>
>>>>
>>>> 2. The timeformat and timestampformat specified in our
>>>> applications.ini file is being ignored. The system settings are used
>>>> for these values instead of our application specific ones. I am not
>>>> sure if this is related to problem 1 or not. How do I make Witango pay
>>>> attention to the timeformat and timestamp format in the
>>>> applications.ini file? (yes the Witango server has been restarted)
>>>>
>>>> We are running Witango Application Server (Standard Edition Upgrade)
>>>> 5.0.1.065
>>>>
>>>> Thanks for any tips or information you can provide.
>>>> ______________________________________________________________ __________
>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>>
>>> ______________________________________________________________ __________
>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>>
>>
>> --
>> Dan Stein
>> Digital Software Solutions
>> 799 Evergreen Circle
>> Telford PA 18969
>> Land: 215-799-0192
>> Cell: 610-256-2843
>> Fax 413-410-9682
>> FMP, WiTango, EDI,SQL 2000
>> [EMAIL PROTECTED]
>> www.dss-db.com
>>
>> "When you are born, you cry and those who love you rejoice. And if
>> you
>> live your life as you should, when you die, you rejoice and those who
>> love you cry."
>>
>>
>>
>> ______________________________________________________________ __________
>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>
> ______________________________________________________________ __________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
> ______________________________________________________________ __________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
--
Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com
"When you are born, you cry and those who love you rejoice. And if you
live your life as you should, when you die, you rejoice and those who
love you cry."
______________________________________________________________ __________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________ __________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________ __________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________ __________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
