Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Error 1608 A Client Process exited abnormally

2 posts in Internet Last posting was on 2000-09-02 07:32:34.0Z
David Milller Posted on 2000-09-01 22:44:55.0Z
From: "David Milller" <dmill@bellsouth.net>
Subject: Error 1608 A Client Process exited abnormally
Date: Fri, 1 Sep 2000 18:44:55 -0400
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Message-ID: <cyEXAiGFAHA.130@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.internet
NNTP-Posting-Host: 63.67.185.181
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.internet:307
Article PK: 1067364

I am in an environment that is using Perl/PHP/CGI with the Perl DBI as the
means of communicating with the database. I am beginning to see the the
Error 1608, Severity:18, State: 4 more and more. The book says it is
nothing to worry about but I am seeing it sometimes 40 or so times a day an
growing.

We are a VERY HIGH volume web shop so we are dealing with 500,000 unique
connections per day. I am looking for any insight into what is causing this
error. Can the Perl/PHP scripts end in some way that casuses this error.
Can I have the Perl programmers fix the ending of the transactions in their
code?

Please any help greatly appreciated?????

We have Sybase ASE 12.0 64 Bit on Sun Solaris 2.6. We use Zeus web server.
DB Server has 4G RAM and 4 Processors.

Thanks in advance,
Miller


Anthony Mandic <amandic Posted on 2000-09-02 07:32:34.0Z
Date: Sat, 02 Sep 2000 17:32:34 +1000
From: Anthony Mandic <amandic@*t.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Error 1608 A Client Process exited abnormally
References: <cyEXAiGFAHA.130@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <d5NlPHLFAHA.268@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.internet
Lines: 55
NNTP-Posting-Host: pix208a.magna.com.au 203.111.111.208
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.internet:306
Article PK: 1067362


David Milller wrote:
>
> I am in an environment that is using Perl/PHP/CGI with the Perl DBI as the
> means of communicating with the database. I am beginning to see the the
> Error 1608, Severity:18, State: 4 more and more. The book says it is
> nothing to worry about but I am seeing it sometimes 40 or so times a day an
> growing.
>
> We are a VERY HIGH volume web shop so we are dealing with 500,000 unique
> connections per day. I am looking for any insight into what is causing this
> error. Can the Perl/PHP scripts end in some way that casuses this error.
> Can I have the Perl programmers fix the ending of the transactions in their
> code?
>
> Please any help greatly appreciated?????

40 messages is nothing for your number of connections per day. Message
1608 is quite common. It happens when a client connection terminates
abruptly. You'd see it quite frequently at sites that have PC users
as clients. These are users who kill their client process or shutdown
their system with the client process running (probably because they
think their client has died since its hung on a badly performing query
or they are blocked. Basically naive users who are impatient).

Given that you have a web interface the problem can easily be exacerbated.
Its too easy to close a connection when a query process takes too long to
return. This is most likely what is happening at your site. About the best
thing you can do is code the middle tier so that it can detect if the
client end is gone to cancel the query and close the connection to the
server. Unfortunately, I don't know enough about the web mechanism here
to say if its even possible. You'd have to have your perl programmers
test the feasibility of this. But they should know what to check now.
Alternately you can just continue to ignore it and put it down to
something that happens and will continue to happen.

> We have Sybase ASE 12.0 64 Bit on Sun Solaris 2.6. We use Zeus web server.

??? This isn't possible. Solaris 2.6 is a 32 bit OS. It can't run
64 bit apps. You have to either be using ASE 12 32 bit or be on
Solaris 7 or 8 in 64 bit mode.

-am