RE: Witango-Talk: crashing witango 5 on OS X

Thu, 01 Dec 2005 11:57:50 -0800

This still sounds like a datasource management issue. Witango is either trying to make a new ds connection, or in the process of tearing one down, or needing to set options on a connection that aren’t working. This is largely a guess, I admit.

 

These are things I would try (next – I know you’ve been dealing with this for a while):

 

1)       run with datasourcelife = 1

2)       run with datasourcelife = 120

3)       Try inserting a very simple and static database search at the top of the taf on the same table(s) involved in the crash. In other words ‘touch’ it before you use it.

4)       Make sure the “Number of rows to retrieve” is set to “No Maximum” and the Start retrieval at match number is 1 on the Results pane of the DirectDBMS action

 

Robert

 

From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 01, 2005 2:26 PM
To: [email protected]
Subject: Re: Witango-Talk: crashing witango 5 on OS X

 

15

how might that be related to crashes in one action of one taf only on first hits of a record, some of the time?

 

 

On Dec 1, 2005, at 11:21 AM, Robert Shubert wrote:



What is your data source timeout setting?

 

-----Original Message-----

From: Roland Dumas [mailto:[EMAIL PROTECTED]]

Sent: Thursday, December 01, 2005 12:24 PM

Subject: Re: Witango-Talk: crashing witango 5 on OS X

 

Still trying to figure out what crashes witango server 5 on OS X

(10.3.9)

 

previously, I'd isolated crashes to a single action in a taf that is

an order processing function. The order processing person looks at

each order before submitting them to a back end system, so the taf is

doing a SELECT and pulling up one order. Initially a search action

item, I changed to direct dbms so I could write the select as simply

as possible.

 

The failure occurs in this situation: about 10% of the time, the

first hit of a specific record crashes witango server. subsequent

queries of the record do not. No pattern at all to the content of the

record being grabbed. No odd characters or anything.

 

To further simplify, I duplicated the offending action and removed

all results processing. Still crashed.

 

Since the query is a left outer join, I thought maybe there was

something about the results of that causing witango to choke, so I

created simple select all actions for each of the two tables.

Actually a witango query action returning all fields of the specific

two tables.

 

Crash.

 

The 'orders' table - when a record is queried for the first time, it

sometimes crashes witango, about 10% of the time.

 

So I think maybe something is wrong with the table. I get my mysql

admin application, Navicat, and launch the various maintenance

functions, and they all come back saying the table is just fine. I

repair, optimise, etc, but I still have this crashing problem.

 

Customer support says to upgrade to witango 5.5 and OS X 10.4

 

That's a big deal to do, especially when the ecommerce site is taking

many large sales during the holiday season. (we'll set aside the

issue of upgrading when the paid for version has been anything but

trouble-free)

 

ok, that's my story. witango crashes on the first query of a record

in a specific table summa the time. How to I go about fixing this?

________________________________________________________________________

 

________________________________________________________________________

 

 

Roland A. Dumas

310 W. Bellevue Ave.

San Mateo, CA 94402

650-347-1373

415-412-9300 (cell)

AIM: radumas

 



 

________________________________________________________________________
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