Sybase ASE max network packet size

This is a server wide configuration setting. The
benefit of using larger packet sizes is that you can
get better efficiency and throughput from the network
by sending data in larger packets, i.e. the same
amount of data is transmitted in a smaller number of
large packets and thus incur less overhead.

On the client side, it is also possible to set the
packet size for the connection explicitly, which is
apparently what your application is doing. However,
the client can only set the packet size to a maximum
of the server "max network packet size", assuming that
sufficient "additional network memory" exists. If the
client packet size exceeds "max network packet size",
you get an error and the connection fails.

regards,

David

--- Alexander Foken <alexander@xxxxxxxx> wrote:

What does "sp_configure max network packet size"
affect? The current
connection or the entire server?

If it's the connection, it simply can't work: The
commercial app is
forked, and has no relation to DBI's connection, so
it creates and uses
its own connection (though it seems to fail to set
the desired size by
itself).

It it's the entire server, does the client library
assume a certain size
or does it asks the server for the current max.
packet size?


(And why would you want to change that setting?)

Alexander

On 23.06.2006 14:36, Matthew Persico wrote:

I have a commercial program that accesses a Sybase
12.5 server. It has
an option to change the packet size of the
communucation frame with
the server, but you have to know what size you
want.

Sooo, in my perl program, I connect to the
database with DBD::Sybase,
execute a
sp_configure 'max network packet size' and then I
system() the
commercial program with the argument
-zpkt=whatever I got back.

Occasionally, the program responds with

DB-Lib ERROR: 20201: Packet size of 16384 not
supported -- size of
13824 used instead. severity is 1

The program then dies, but that is their problem -
it should
disconnect and reconnect properly and I will
register te bug with them

My question is this what causes this? One minute
16384 is ok and the
next its not. DBD::Sybase is CT-LIb based and
their program is DB-Lib
based. Is that a problem?
--
Matthew O. Persico



--
Alexander Foken
mailto:alexander@xxxxxxxx
http://www.foken.de/alexander/



.

Relevant Pages

  • Re: Socket weirdness
    ... client) before you will notice a shutdown receive at server. ... Then eventually a packet comes from the peer, and that will contain data, so the server responds RST: ... way back across the network. ...
    (microsoft.public.dotnet.framework)
  • Re: At a loss figuring out if an IP is on LAN or INET
    ... What the server probably wants to check here is whether the IP in the ... packet header matched the IP in the packet data. ... multiple desktop machines behind "true NAT" firewalls. ... computer that just accepted the connection). ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Removing T/TCP and replacing it with something simpler
    ... > globally enabled on the machine and the server supports it too. ... The setsockoptoptimizes packet sending on the server ... >> established TCP connection, but blocks sending data until the ... > will go in one packet on the wire. ...
    (freebsd-arch)
  • Re: asynchronous socket problem when connecting to localhost
    ... You server starts sending right after accepting connection. ... also ensure the packet goes to a correct client. ... it's the last packet I sent. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Nmap questions concering my router
    ... Once a connection is established, ... > it may differ from other applications - we just send data to a network ... > local wire, you may relay the packet from 'Nicky' to the router, but I ... > all addresses (and may listen using just one interface to receive all ...
    (comp.security.firewalls)