The latest production app server on OS X crashes every so often, when traffic is
fairly high. The app server's FATAL signal is either a bus error or segmentation
violation, usually the latter. If anyone has any ideas as to why this might happen,
or things to try to prevent it, I would be happ
What are the:
CACHE=
CACHEINCLUDEFILES=
variables set to in the witango.ini file?
Robert Garcia
On Tuesday, January 28, 2003, at 08:49 AM, Jeffrey Bohmer wrote:
The latest production app server on OS X crashes every so often, when
traffic is fairly high. The app server's FATAL signal is
TRUE for both. (The CACHESIZE is about 20MB.)
- Jeff
>What are the:
>
>CACHE=
>CACHEINCLUDEFILES=
>
>variables set to in the witango.ini file?
>
>Robert Garcia
>
>On Tuesday, January 28, 2003, at 08:49 AM, Jeffrey Bohmer wrote:
>
>>
>>The latest production app server on OS X crashes every so
How heavy a load? I have tested it under heavy loads, and It did well,
where it used to crash. There is still a point where it crashes when
absolutely hammered, but it seems to be beyond the point of reasonable
expectation. If the cache is off, it will crash under a lighter load.
Looking at
For a few minutes before the crashes, the app server gets about 35-45 requests per
minute. Other hardware/config info:
Dual 1.25GHz G4
1.75 GB memory
PostgreSQL has it's own drives for data & logs.
THREADPOOLSIZE=25
LOGGINGLEVEL=3
All caches/buf
Hi,
What would be the best solution to block a user from entering a site twice.
Or, in other words prevent other users to use a same login. Any Ideas?
Thanks!
Marc Leblanc
_
The new MSN 8: advanced junk mail protection and 2
The threadpoolsize acts different than you think it would. I have done
alot of testing, and the more you add, the slower, and more buggy the
server gets. It is worse on the mac than windows, but occurs on both.
Try setting the threadpoolsize to 10. Also, before you test, open the
terminal,
I've been monitoring the system with top -u for a while. witangod's threads are
always 3 above THREADPOOLSIZE. CPU usage for witangod is usually 90 - 110% when the
site is getting hits. When no hits are coming in, it drops out of the list. (I
assume CPU usage can go above 100% because this
Title: What am I doing wrong? <@URL> w/ postargarray
I created a taf to test the connection to a secure server using the <@URL> tag and I keep getting an error message. Can anyone tell me what I am doing wrong? I have tried placing the taf on both a secure and non-secure server and still get the
Title: Problems with <@URL>/Mac OS X/HTTPS
I created a taf to test the connection to a secure server using the <@URL> tag and I keep getting an error message. Can anyone tell me what I am doing wrong? I have tried placing the taf on both a secure and non-secure server and still get the same mess
Did you talk about the same physical user?
if yes you should verify that a specific variable/object in the user scope
has not a specific value/state.
if you talk about protecting a session to be opened twice or more from many
differents users, you should need some checking on the domain scope by
What are using to simulate the load? Are you hitting the same taf over
and over? Are you monitoring real traffic? If you are monitoring
realtraffic, does the witangoevents.log tell you which taf the app
server crashed on? When it crashes, is it actually crashing, producing
a crash log, or j
You may visit http://www.theradmac.com/ and download the latest witango installers:
AS 5.01.054 for Windows.
AS 5.01.054a for OS X.
DS 5.0.2 for OS X.
--
Robert Garcia
BigHead Technology
2781 N Carlmont Pl
Simi Valley, CA 93065
Phone 805.522.8577
http://www.bighead.net/
http://www.theradmac.com
I think I"m getting that disease that doesnt let you remember things...
like well formed english or how to install Tango...
Just did a 2tk SP1 install, and the .taf that I have called is spitting
out the XML code for the taf (the taf itself only has a html page in it -
no xml)
Therefore, somethin
The load is real traffic. The witangoevents.log does not specify a taf,
rather it says things like:
[20794] 2003-01-28 10:23:02 RUNTIMEINFO Started accepting user
requests
[20794] 2003-01-28 10:50:08 RUNTIMEFATALCaught fatal signal
SIGSEGV; thread id = 3801008
[21067] 2003-01-28
Stacey,
It looks like the web server isn't recognizing the plugin. What OS and
web server are you using?
Jason
On Tuesday, January 28, 2003, at 09:09 PM, Stacey Schoffer wrote:
I think I"m getting that disease that doesnt let you remember things...
like well formed english or how to install T
Hi Stacey,
This might sound basic but are you actually calling
the file via the web server. From what you have below
it looks like you could be dragging the file onto your
web browser or opening the file in the browser.
What I mean is you'll need to open the file in the
form:
http://localhost\hel
Before you troubleshoot further, you have to determine if you have a
specific method/taf that is causing the problem. Unfortunately the OS X
logging doesn't work as well as on the windows version.
Robert
On Tuesday, January 28, 2003, at 06:17 PM, Jeffrey Bohmer wrote:
The load is real traff
Well the comments posted to the list pretty much confirm what I had heard
before, that the present encrypt/decrypt tags offered with Witango are
either not tight enough or not practical in a production environment.
I really am looking for tags using blowfish or MD5 technology. You can tell
I am by
I've started to look at the GnuPG package - it looks like there are
scriptable versions for Windows, Mac and Linux. If I can get a simple
example working, it should be workable to incorporate into a TCF/Custom
tag. The dilemma you still have with that though is key creation and
storage. To
Jeff,
You might get a clue on the last TAF served by corresponding the web
server log file with the Witango log file. That will always keep
logging, even when the daemon dies. If you can look at a few instances
you might build a case for common culprits to find specific files that
could be
Witango -r option does not work correctly.
Console says... Another instance is running. Seems to be that the restart is
to quick before old witangod has quit.
Christian
Btw... Will there be a config.taf as before?
TO UNSU
Title: Re: Witango-Talk: Problems with <@URL>/Mac OS X/HTTPS
When T2K SP1 was release it only had support for SSL on Win32 and Mac OS 8.6/9. The unix versions of the server did not support ssl with the @URL tag. On OS X the server is now using the Unix code base so the Windows server is the o
Try using:
sudo /Applications/Witango/Server/witangod -r
We do not have any issues on the servers in the lab here with this option
restarting the server.
On 29/1/03 4:01 PM, "Christian Platt" <[EMAIL PROTECTED]> wrote:
> Witango -r option does not work correctly.
>
> Console says... Another i
Hi Phil,
i guess the time it takes witangod to shut down is to long and your
script does not wait long enogh to have first instance shut down.
if i use witangod -k it takes some time for the process to quit
if i then restart witango it works, but if i do not wait long enough, i
get the same
Try binding your server to a single IP address by setting the
LISTENERADDRESS in the witango.ini file and see if this speeds up the
shutdown of the server. LISTENERADDRESS instructs the server to use the
specified IP address instead of binding to all addresses available to the
machine. Binding to
Christian,
What is the configuration of the HW you are running the server on? Is it OS
X Workstation or Server? 10.2.3?
On 29/1/03 5:09 PM, "Christian Platt" <[EMAIL PROTECTED]> wrote:
> Hi Phil,
>
> i guess the time it takes witangod to shut down is to long and your
> script does not wait l
27 matches
Mail list logo
