Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Roland Dumas
I'm serious here. Had interminable problems with odbc and now with jdbc. Experiencing crashes either way. Odbc crashed on one machine, jdbc crashes 2 machines. (identical machines). Jdbc crashes don't have any build-ups like odbc. No CPU pegging, etc. just when there is a hit, it goes boom crash.

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Dale Graham
We're running two servers (one production, one development) at OS X 10.3.8. Our database is Oracle 9. We're running JDBC connections for the J2EE version of the Witango servlet and that's been very, very stable. On our laptops for development, we're using JDBC to connect to the Oracle db wi

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Roland Dumas
Since my case(s) are connecting to mysql, I've got different moving parts. Nevertheless, when I ask folk who use the same connectors to mysql if they have experienced application server crashes, they say "Nope". I'm sure there are bugs, but how come other folks say their app servers throw errors a

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Dale E Graham
We use JDBC to MySQL as well, again with no crash problems. It does seem pretty mysterious. I haven't experienced the "crash boom" thing. On the other hand, I think we've always been in 10.3+ since we started using JDBC to connect... Maybe 10.2.8 wasn't *quite* ready for prime time in this reg

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Roland Dumas
Yes, it is possible that witango was not fully stable on 10.2.8 On 2/25/05 12:11 PM, "Dale E Graham" <[EMAIL PROTECTED]> wrote: > We use JDBC to MySQL as well, again with no crash problems. It does > seem pretty mysterious. I haven't experienced the "crash boom" thing. > On the other hand, I thi

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Jon van der Raadt
We are running 5.0.9 on osx server 10.3.8 -- not a hickup. 10.2.8 has a number of issues and I would highly recommend an upgrade. Jon On 25-Feb-05, at 1:17 PM, Roland Dumas wrote: Yes, it is possible that witango was not fully stable on 10.2.8 On 2/25/05 12:11 PM, "Dale E Graham" <[EMAIL PROTEC

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Roland Dumas
With what database and connection? On 2/25/05 12:32 PM, "Jon van der Raadt" <[EMAIL PROTECTED]> wrote: > We are running 5.0.9 on osx server 10.3.8 -- not a hickup. 10.2.8 has > a number of issues and I would highly recommend an upgrade. > > Jon > On 25-Feb-05, at 1:17 PM, Roland Dumas wrote: >

Re: Witango-Talk: Can anyone read a crash log for jdbc crash?

2005-02-25 Thread Roland Dumas
Where'd you get witango 5.0.9? Latest I see is 5.0.1.65 On 2/25/05 12:32 PM, "Jon van der Raadt" <[EMAIL PROTECTED]> wrote: > We are running 5.0.9 on osx server 10.3.8 -- not a hickup. 10.2.8 has > a number of issues and I would highly recommend an upgrade. >

Witango-Talk: Problem with @URL post

2005-02-25 Thread Stefan Gonick
I'm trying to use @URL to POST arguments to a program that is expecting to get a form post on a non-Witango system. I tested my @URL on my own program that was expecting a form posting, and it worked fine. When I sent the same information to the ColdFusion based program, it did not think that it

RE: Witango-Talk: Problem with @URL post

2005-02-25 Thread Scott Cadillac
Hi Stefan, Did you pass your form arguments via POSTARGARRAY or POSTARGS? Also, use the FROM attribute of <@URL>, and add the following to it FROM='[EMAIL PROTECTED]<@CRLF>Content-Type: application/x-www-form-urlencoded' Hope that helps. Scott Cadillac - Business Extranet Freedom IExtr

RE: Witango-Talk: Problem with @URL post

2005-02-25 Thread Stefan Gonick
I tried both using postargarray and postargs with the same lack of result. I'll try your suggestion next. Thanks! Stefan At 06:39 PM 2/25/2005, you wrote: Hi Stefan, Did you pass your form arguments via POSTARGARRAY or POSTARGS? Also, use the FROM attribute of <@URL>, and add the following to it FR