Shannon,
There are know issues with xODBC and Filemaker 7-9 I am not sure if
they extend to JDBC but there are related to the FMP plug in in not
Witango as I can reproduce them with any ODBC connection to FMP.
I have been working for 1 year with FMI to resolve these.
We are close.
They are
Out of memory errors which cause the plug in stop responding at all
( these seems resolved with 9)
Failure to close connections properly when shutting down the DB
Dan
--
Dan Stein
FileMaker 7 Certified Developer
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 215-799-0192 (call 1st)
FMP, WiTango, EDI,SQL 2000, MySQL, PHP
[EMAIL PROTECTED]
"The mind is its own place and in itself can make heaven of hell or a
hell of a heaven." John Milton
On Oct 1, 2007, at 6:35 PM, Shannon Henderson wrote:
We use JDBC with Filemaker and OCI with Oracle. We're not having
trouble with anything but Witango connections now. I'm finding it
harder to believe that all of the driver creators got it wrong and
Witango got it right...
On Oct 1, 2007, at 2:43 PM, Robert Garcia wrote:
The old database I used to use, would require this when for some
reason witango would burp or lost connection. It was very
frustrating, but I never found a way to just stop that one thread
from the witango side. It should be noted, that other dbs don't
require this. Both MS SQL 2000 and MySQL don't have this problem.
I can reboot mysql, and leave witango alone, and it will
reconnect. This led me to realize, it is more of an issue with the
ODBC driver/db from the vendor. I experimented with other code and
found this to be the case, outside of witango.
What database do you use?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Oct 1, 2007, at 1:20 PM, Shannon Henderson wrote:
Does anyone know if it is possible to kill open database
connections without restarting the witango server process? We've
had some cases lately where a connection will fail somewhere
between the witango server and the database server. Everything
but witango recognizes that the session is dead and ditches it.
Rather than starting a new session, witango just keeps returning
"113 Unable to communicate with the specified data source. The
existing connection was lost." on the old session until the
datasource timeout kicks in.
The problem is that the some other sessions are often fine, so I
hate to kill off everything if I can tell that there are specific
dead sessions.
--------------------------------------------------------------------
Shannon Henderson
Web Support Services
Reed College
Portland, OR 97202-8199
[EMAIL PROTECTED]
--------------------------------------------------------------------
____________________________________________________________________
____
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
