FreeTDS Development Group

[PMoore AT axa.com.au]

brent,
     are you using UNIONs in your query ? or is it just an AND/OR type of
WHERE clause your gui builds?
regards
peter

Peter Moore
Contractor,
ITeG, Axa Australia






"Brent L Johnson" <brent AT bjohnson.net>@franklin.oit.unc.edu on 31/07/2001
03:53:50 AM

Please respond to "TDS Development Group" <freetds AT franklin.oit.unc.edu>

Sent by:  bounce-freetds-132908 AT franklin.oit.unc.edu


To:   "TDS Development Group" <freetds AT franklin.oit.unc.edu>
cc:
Subject:  [freetds] Connection Reset by Peer


I've searched the newsgroups and found other people with similar problems
(especially when connecting to SQL Server).  I'm not sure if this is
driver related, SQL Server related, or JDBC related (which is why I'm
sending this to the list).

I have a search page which searches on a very large database.  One of the
search inputs is a multi select where the person can pick from quite a few
choices.  The report runs just fine, until (it seems) the SQL statement
gets "too large".

It's really strange, it runs fine with (I'm, of course, using FreeTDS
connecting to a SQL Server database) just a a few criteria selected.  But
if I go down and start clicking lots of selects all I get is this:

java.sql.SQLException: Network error- Connection reset by peer: Connection
reset by peer

I uncheck a few of the criteria and it works fine.  Is there a max to the
length of a sql statement sent?  If so, can I increase that, and why would
I get a connection reset by peer rather than some other error?

Any help would be appreciated, thanks,

- Brent

---
You are currently subscribed to freetds as: [PMoore AT axa.com.au]
To unsubscribe, forward this message to
$subst('Email.Unsub')










**********************************************************************
Important Note
This email (including any attachments) contains information which is 
confidential and may be subject to legal privilege.  If you are not 
the intended recipient you must not use, distribute or copy this 
email.  If you have received this email in error please notify the 
sender immediately and delete this email. Any views expressed in this 
email are not necessarily the views of AXA.   Thank you.
**********************************************************************