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

[Roland Dumas]

On Dec 1, 2005, at 3:02 PM, Robert Shubert wrote: I suppose since these options aren’t possible at the moment, and it does seem that Witango is failing internally, I would turn my attention back to the search itself.   Can you not do a join? In other words, search for just the data in orders, then do a second search for the records that are joined in the second table? Yes, I undid the join. Just a simple query on one table causes the crash.   Can you revert back to a standard search action and remove all the absolutely necessary columns? yes. crashes happen   Have you tried moving the search to another TAF (and use braches) or to a TCF (and use a callmethod)? have rewritten the actions completely from scratch. Examination of the XML doesn't reveal anything that looks like it went bad, but then something might be bad that looks right to me...   Are any of the columns holding unusual data? High-bit characters, INTs that might be null or contain spaces, anything that might return data that Witango doesn’t expect? nope. and the records associated with crashes have nothing out of the ordinary in them at all. some are the simplest of orders and some more complex. In fact, the order table doesn't contain the contents of the order, so records are amazingly similar.    Is there anyway to test your site on another server or configuration? I would even be willing to setup the site in my Windows environment if we through it might help. I pulled everything to my testing server and can't reproduce. The production machine is OS X 10.3.9 and the testing is 10.2.8. The difference being that the production machine was crashing with ODBC issues and customer support said that the OS was the culprit and I needed to upgrade to 10.3.9 to get a better flavor of ODBC. That did work and the current issue isn't ODBC related nor did it start when the OS was upgraded. It started when I added one field to the table (VARCHAR 5) that contains Y or N values and also made the search a left outer join to pull in a field from  another table. I got rid of the left outer join and it's just a simple select all the fields query now (either a query action or a directDBMS with SELECT * where order_number = x  That's the action that crashes witango server.  ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf