Two crashes today so far.

The first version of the system was written in Tango2k, then when new releases were available the system was migrated upwards and now resides on tango 5.5. The problems started with 5.0.

Objects, shouldnt they be cached in "application cache"? Include cache is for include files, like html, right?

Looking at the processes I see no process "eating memory". SQL server eats almost 800 megs, though, but I guess that is normal. Witango stays under 30 megs.

Today I have increased the worker threads from 5 to 40, and cachesize from 10 to 20 Megs, to see if the problem goes away. (Tango process jumped up to 110 Megs of memory rightaway)

Thanks for all help!

Peter







----- Original Message ----- From: "Bill Conlon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 02, 2004 2:35 AM
Subject: Re: Witango-Talk: Quoting of method call parameters




Random thoughts:

Did the same code run on v5, and this problem only started with 5.5?

Are you monitoring the processes to see whether memory use is growing
excessively?  Maybe some memory leak got introduced with object
instantiation?

Wasn't there a change in how include files were handled in v5.5?  Can
you allocate more memory for includes, and see if the problem is the
same or better?


On Wednesday, December 1, 2004, at 04:44 PM, Peter Ternstr�m wrote:

i havent used the search builders since 1996 :-), but still find the search action very convenient. Its only when I have to do more custom searches (like user row sorting) that I use the DBMS action instead.

At this moment our production server hosts about 140 community systems for clients. Among these you find Customer clubs, Trade union member systems, Youth project communities, Government e-democracy solutions etc. All communities share the exact same code.

Its hard to give you any good measure of load, as in "hits". Looking at todays report gives me about 2000 user logins during this afternoon, and a peak of about 200 simultaneus users sessions. This made our server crash 5 times. All crashes seem to be related to method calls. Also, after the crash witango fails to restart which is very annoying.

The crashes seem to follow a pattern.

1. A random action causes an Exception_access_violation:

Event log: The "/dok_thread.taf" application file, action "Get_Dok", caused an unrecoverable OS exception. (Get_Dok is a search action that also contains a call method. Object resides in a custom scope shared between all users)

2. Immediately after the first OS exception (same second), another 5-10 actions cause exceptions:

Event log: "/start.taf" application file, action "Users_Online", caused an unrecoverable OS exception.
...
...
And the server "takes the red pill"



I have now updated nearly all call methods to be quoted correctly, as stated in this thread. Well se if the crashing continues tomorrow. Im holding my breath. (Ive been trying to fix this since august)


Thanks again for all advice

Peter




----- Original Message ----- From: "Alan Wolfe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 02, 2004 12:50 AM Subject: Re: Witango-Talk: Quoting of method call parameters


we use only DBMS so we just fixed those up, the search builders use correct
sql syntax so they probably are not the problem.


I cant recall what the errors were in the logs, it was about 2 years ago we
dealed with it. we had to bang our head against the wall quite a while until
we found the fix.


We still have a crash ocasionaly but have something setup to  automaticly
restart witango if it goes down so it's not so bad.

How much load are you under and how many crashes are you getting?

----- Original Message ----- From: "Peter Ternstr�m" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 01, 2004 3:38 PM
Subject: Re: Witango-Talk: Quoting of method call parameters



Thanks for the advice.

I get EXCEPTION_ACCESS_VIOLATION in the event log and the witango service
stops abruptly. The SQL server is rock solid.


Did you get these kind of errors, too?

How did you change to more correct SQL syntax - did you use DBMS actions
instead of standard "Search"?


Peter



----- Original Message ----- From: "Alan Wolfe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 02, 2004 12:36 AM
Subject: Re: Witango-Talk: Quoting of method call parameters


> They were related to the database, Oterro would accept a whole lot of > variations of sql syntax (like sel instead of select, and you can omit > commas from column lists and such), but it turned out, some variations > worked better than others, and some would cause crashes. > > Changing to more correct SQL syntax made most of our problems disapear. > We > still have a couple crashes every handful of days but its much more > acceptable than it was. > > At one point in time we had a complicated while loop that under certain > circumstances would loop infinitely and cause witango to crash too, you > might look into that if you are using a loop that might not be > terminating. > > Another thing you might do to find the place it's crashing would be to
put
> some file append actions in your code to write out to a log file >
certain
> information like "user ref <userref> is at <filename> in position
2".
SO
> when it crashes you can look at the log and see the last couple
entries
to
> see if theres a pattern.
>
> ----- Original Message ----- > From: "Peter Ternstr�m"
<[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 01, 2004 3:22 PM
> Subject: Re: Witango-Talk: Quoting of method call parameters
>
>
>> What kind of issues were those? Please tell us more, we're kind of
> fumbling
>> in the dark for a solution
>>
>> Peter
>>
>>
>> ----- Original Message ----- >> From: "Alan Wolfe"
<[EMAIL PROTECTED]>
>> To: <[EMAIL PROTECTED]>
>> Sent: Thursday, December 02, 2004 12:15 AM
>> Subject: Re: Witango-Talk: Quoting of method call parameters
>>
>>
>> > Nope sorry we have:
>> >
>> > R:Base for database
>> >
>> > IIS6
>> >
>> > Windows 2003 server
>> >
>> > Witango 5.0.1.065
>> >
>> > there were some issues we worked through so thought id ask.
>> >
>> > ----- Original Message ----- >> > From: "Peter Ternstr�m"
<[EMAIL PROTECTED]>
>> > To: <[EMAIL PROTECTED]>
>> > Sent: Wednesday, December 01, 2004 3:08 PM
>> > Subject: Re: Witango-Talk: Quoting of method call parameters
>> >
>> >
>> >> Im using MS SQL server 2000 with SP3
>> >>
>> >> IIS6
>> >>
>> >> Win 2003 server
>> >>
>> >> Witango 5.5
>> >>
>> >>
>> >> Any similar experiences with this setup?
>> >>
>> >>
>> >> Peter
>> >>
>> >> ----- Original Message ----- >> >> From: "Alan Wolfe"
<[EMAIL PROTECTED]>
>> >> To: <[EMAIL PROTECTED]>
>> >> Sent: Thursday, December 02, 2004 12:09 AM
>> >> Subject: Re: Witango-Talk: Quoting of method call parameters
>> >>
>> >>
>> >> > Hey Peter,
>> >> >
>> >> > Just curious, what database are you using?
>> >> >
>> >> > ----- Original Message ----- >> >> > From: "Peter Ternstr�m"
<[EMAIL PROTECTED]>
>> >> > To: <[EMAIL PROTECTED]>
>> >> > Sent: Wednesday, December 01, 2004 3:03 PM
>> >> > Subject: Re: Witango-Talk: Quoting of method call parameters
>> >> >
>> >> >
>> >> >> It works great on our development server, but on the
production
>> >> >> servers
>> >> >> it
>> >> >> crashes under load.
>> >> >>
>> >> >> Today we had 4 crashes, and severe load.
>> >> >>
>> >> >> Yesterday we only had 1 crash, but moderate load.
>> >> >>
>> >> >> Crashlog doesnt point me out to one tcf or taf file, so it
must
be
>> >> > something
>> >> >> in the app server...or our code ;-)
>> >> >>
>> >> >> Peter
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> ----- Original Message ----- >> >> >> From: "Ben Johansen"
<[EMAIL PROTECTED]>
>> >> >> To: <[EMAIL PROTECTED]>
>> >> >> Sent: Wednesday, December 01, 2004 11:43 PM
>> >> >> Subject: RE: Witango-Talk: Quoting of method call parameters
>> >> >>
>> >> >>
>> >> >> The easiest way to tell is to create a stub method that
take in
the
>> >> >> parameters and records/displays them somewhere without any
other
> code
>> > in
>> >> > the
>> >> >> method
>> >> >> This should tell you if the variables are to blame or it is
you
> code.
>> >> >>
>> >> >> Since most of us think that our code (mine included) is >>
>> >> brilliant
> and
>> >> >> correct the first time out of chute, then it must be the
software.
> LOL
>> >> >> ;-)
>> >> >>
>> >> >>
>> >> >> Ben Johansen - http://www.pcforge.com
>> >> >> Authorized Witango & MDaemon Reseller
>> >> >> Available for Witango Developement
>> >> >>
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: Peter Ternstr�m [mailto:[EMAIL PROTECTED]
>> >> >> Sent: Wednesday, December 01, 2004 3:31 PM
>> >> >> To: [EMAIL PROTECTED]
>> >> >> Subject: Re: Witango-Talk: Quoting of method call parameters
>> >> >>
>> >> >> Thanks Ben,
>> >> >>
>> >> >> Im experiencing server crashes under heavy load and I am
trying
to
>> > figure
>> >> >> out the problem. Its always a TCF that causes the crash. In
the
>> >> >> current
>> >> >> method calls, values that are integers or will evaluate to
integers
>> > (from
>> >> >> vars, column refs etc) are NOT quoted.
>> >> >>
>> >> >> Could not quoting values in method calls cause the server to
crash?
>> >> >> (on
>> >> >> heavy load)
>> >> >>
>> >> >> ?
>> >> >>
>> >> >> Peter
>> >> >>
>> >> >>
>> >> >> ----- Original Message ----- >> >> >> From: "Ben Johansen"
<[EMAIL PROTECTED]>
>> >> >> To: <[EMAIL PROTECTED]>
>> >> >> Sent: Wednesday, December 01, 2004 9:41 PM
>> >> >> Subject: RE: Witango-Talk: Quoting of method call parameters
>> >> >>
>> >> >>
>> >> >> Either quote is fine '""' or "''"
>> >> >> The issue with this quote is not the type of the column but
the
>> >> >> name
>> >> > itself,
>> >> >> since column names can contain spaces, I consider it a most >> >> >> habit
>> >> >> to
>> >> >> quote
>> >> >> these
>> >> >>
>> >> >> Ben Johansen - http://www.pcforge.com
>> >> >> Authorized Witango & MDaemon Reseller
>> >> >> Available for Witango Developement
>> >> >>
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: Peter Ternstr�m [mailto:[EMAIL PROTECTED]
>> >> >> Sent: Wednesday, December 01, 2004 1:30 PM
>> >> >> To: [EMAIL PROTECTED]
>> >> >> Subject: Re: Witango-Talk: Quoting of method call parameters
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> so how about column references?
>> >> >>
>> >> >> <@CALLMETHOD OBJECT="object" SCOPE="d2"
>> >> >> METHOD="show_messenger_voting_form(<@COLUMN
'messenger.auid'>)"
>> >> >> ENCODING=META>
>> >> >>
>> >> >> The auid can only contain integers, but should I quote it >> >> >> anyway?
>> >> >>
>> >> >> And if I quote it, should, how should I quote it?
>> >> >>
>> >> >> <@CALLMETHOD OBJECT="object" SCOPE="d2"
>> >> >> METHOD="show_messenger_voting_form('<@COLUMN >> >> >>
"messenger.auid">')"
>> >> >> ENCODING=META>
>> >> >>
>> >> >> ?
>> >> >>
>> >> >> Peter
>> >> >>
>> >> >>
>> >> >>
>> >> >> ----- Original Message ----- >> >> >> From: "Alan Wolfe"
<[EMAIL PROTECTED]>
>> >> >> To: <[EMAIL PROTECTED]>
>> >> >> Sent: Wednesday, December 01, 2004 6:51 PM
>> >> >> Subject: Re: Witango-Talk: Quoting of method call parameters
>> >> >>
>> >> >>
>> >> >> > And if you want to be "fully xml compliant" (witango is >> >> >> > getting
>> >> >> > stricter
>> >> >> > on
>> >> >> > that sometime in the future isnt it? I recall something
about
>> >> >> > that
>> >> >> > at
>> >> > the
>> >> >> > last conference), you will want to quote just about
EVERYTHING
so
>> >> >> > better
>> >> >> > safe now then sorry later on i think (:
>> >> >> >
>> >> >> > for the xml compliance it's only for attributes of tags
though
if
> i
>> >> >> > understand correctly, so instead of this which works now:
>> >> >> > <@RANDOM HIGH=100 LOW=1>
>> >> >> >
>> >> >> > you'd want this:
>> >> >> > <@RANDOM HIGH="100" LOW="1">
>> >> >> >
>> >> >> > ----- Original Message ----- >> >> >> > From: "Ben
Johansen" <[EMAIL PROTECTED]>
>> >> >> > To: <[EMAIL PROTECTED]>
>> >> >> > Sent: Wednesday, December 01, 2004 9:41 AM
>> >> >> > Subject: RE: Witango-Talk: Quoting of method call
parameters
>> >> >> >
>> >> >> >
>> >> >> > Here is a couple of quick rules that I use in Witango
>> >> >> >
>> >> >> > If it is contains a space "Quote It"
>> >> >> > If it is a String/Text "Quote it even if it doesn't have a
space"
>> >> >> > If it is a number "Quoting Optional" if the number is in a
>> >> >> > Witango
>> >> >> > Variable
>> >> >> > "Quote It"
>> >> >> >
>> >> >> > You can pretty much quote all because Witango doesn't use
> explicitly
>> >> > typed
>> >> >> > vars they pretty much are all strings
>> >> >> >
>> >> >> > <@CALC EXP="1 + 1"> = <@CALC EXP="'1' + '1'">
>> >> >> >
>> >> >> >
>> >> >> > Ben Johansen - http://www.pcforge.com
>> >> >> > Authorized Witango & MDaemon Reseller
>> >> >> > Available for Witango Developement
>> >> >> >
>> >> >> >
>> >> >> > -----Original Message-----
>> >> >> > From: Peter Ternstr�m [mailto:[EMAIL PROTECTED]
>> >> >> > Sent: Wednesday, December 01, 2004 10:11 AM
>> >> >> > To: [EMAIL PROTECTED]
>> >> >> > Subject: Witango-Talk: Quoting of method call parameters
>> >> >> >
>> >> >> > Hello everyone,
>> >> >> >
>> >> >> > sorry for this maybe stupid question;
>> >> >> >
>> >> >> > what is correct quoting in a method call?
>> >> >> >
>> >> >> > if the parameters are integer values, should they be
quoted
> anyway?
>> >> >> >
>> >> >> > Thanks for all help
>> >> >> >
>> >> >> > Peter
>> >> >> >
>> >
______________________________________________________________________ __
>> >> >> > 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
>> >> >>
>> >> >>
>> >> >>
>> >
______________________________________________________________________ __
>> >> >> 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
>
>
_____________________________________________________________________ ___
> 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

Reply via email to