Before you move to nine you need to make sure that you are not using
the "show" DB technique for ODBC.
If you have DB A with data in it and DB B with no data but references
to the A tables and you connect through B then you are better off
sticking with 8 until the update to the ODBC plug in. They fixed the
issue you are having trouble with but now there is an open connection
to A and B and they never close the connection to A so even with
Witango you can end up opening many connections and get over your 100
connections on a busy server.
I have a version of the XODBC plug in that we have been using for
about 8 months with 8 that they never released that solves the major
issues you are having.
If you need that contact me off list and let me know where to FTP it
to its 25 megs.
Dan
--
Dan Stein
FileMaker 7 Certified Developer
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
FMP, WiTango, EDI,SQL 2000, MySQL, PHP
[EMAIL PROTECTED]
www.dss-db.com
'We create the world in which we live: if that world becomes unfit
for human life, it is because we tire of our responsibility.'
Cyril Connolly 1938
On Oct 5, 2007, at 1:36 PM, Kent Swisher wrote:
Dan
I am using remote FMSA8 as data source via ODBC for 6 months. Have
had problems, not with Witango hanging, but that the FMSA does not
re-establish ODBC upon a reboot of the FMSA server hardware. FMSA
says ODBC is enabled but no connections can be made from any ODBC
enabled PC or app. Usually takes a second boot of FMSA application
to re-establish ODBC. Witango apps come back online after FMSA
reboot without having to reboot the local IIS server.
Moving to FMSA9 this week.
-> Kent
On 10/5/2007 6:55 AM, Dan Stein wrote:
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] <mailto:[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] <mailto:[EMAIL PROTECTED]> -
[EMAIL PROTECTED] <mailto:[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] <mailto:[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
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
