Home > Archive > SQL Anywhere Mobile > May 2005 > Why is -x tcpip{keep_alive=1} invalid?









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Why is -x tcpip{keep_alive=1} invalid?
Breck Carter

2005-05-30, 7:24 am

Why is -x tcpip& #123;keep_alive=3d1}
invalid? This contradicts
the Help which says it is ignored.

Breck

I. 05/30 04:29:09. Adaptive Server Anywhere MobiLink Version
9.0.2.3124
I. 05/30 04:29:09.
I. 05/30 04:29:09. Copyright =a9 1989-2004 Sybase, Inc.
Portions Copyright =a9 2002-2004,
iAnywhere Solutions, Inc.
I. 05/30 04:29:09. All rights reserved. All unpublished
rights reserved.
I. 05/30 04:29:09.
I. 05/30 04:29:09. This software contains confidential and
trade secret information of
I. 05/30 04:29:09. iAnywhere Solutions, Inc.
Use, duplication or disclosure of the
software and documentation
I. 05/30 04:29:09. by the U.S. Government is subject to
restrictions set forth in a license
I. 05/30 04:29:09. agreement between the Government and
iAnywhere Solutions, Inc. or
I. 05/30 04:29:09. other written agreement specifying the
Government's rights to use the
I. 05/30 04:29:09. software and any applicable FAR
provisions, for example, FAR 52.227-19.
I. 05/30 04:29:09.
I. 05/30 04:29:09. iAnywhere Solutions, Inc., One Sybase
Drive, Dublin, CA 94568, USA
I. 05/30 04:29:09.
I. 05/30 04:29:09. Networked Seat (per-seat) model. Access
to the server is limited to 1 seat(s).
This server is licensed to:
I. 05/30 04:29:09. Developer Edition
I. 05/30 04:29:09. Restricted Use
I. 05/30 04:29:10. <Main>: MobiLink server started
I. 05/30 04:29:10. <Main>: Option 1: -c
I. 05/30 04:29:10. <Main>: Option 2: DSN=3dUno
Remittance9;UID=3dMo
bilink1;pwd=3d******
**
I. 05/30 04:29:10. <Main>: Option 3: -fr
I. 05/30 04:29:10. <Main>: Option 4: -r
I. 05/30 04:29:10. <Main>: Option 5: 3
I. 05/30 04:29:10. <Main>: Option 6: -vs
I. 05/30 04:29:10. <Main>: Option 7: -x
I. 05/30 04:29:10. <Main>: Option 8: tcpip& #123;keep_alive=3d1}

I. 05/30 04:29:10. <Main>: Option 9: -w
I. 05/30 04:29:10. <Main>: Option 10: 20
I. 05/30 04:29:10. <Main>: Option 11: -s
I. 05/30 04:29:10. <Main>: Option 12: 200
I. 05/30 04:29:10. <Main>: Option 13: -zu+
I. 05/30 04:29:10. <Main>: Option 14: -d
I. 05/30 04:29:10. <Main>: Option 15: 128m
I. 05/30 04:29:10. <Main>: Option 16: -u
I. 05/30 04:29:10. <Main>: Option 17: 32m
I. 05/30 04:29:10. <Main>: Option 18: -e
I. 05/30 04:29:10. <Main>: Option 19:
E:\MobilinkServer\re
mote_errors.txt
I. 05/30 04:29:10. <Main>: Option 20: -f
I. 05/30 04:29:10. <Main>: Verbose logging: show script
names when invoked
I. 05/30 04:29:10. <Main>: Individual database connections
will be closed after synchronization errors.
I. 05/30 04:29:10. <Main>: BLOB cache size: 524288
I. 05/30 04:29:10. <Main>: Maximum number of BLOB bytes to
compare: 4294967295
I. 05/30 04:29:10. <Main>: Maximum number of database
connections: 21
I. 05/30 04:29:10. <Main>: Maximum number of deadlock
retries: 3
I. 05/30 04:29:10. <Main>: Timeout for inactive database
connections: 60 minutes
I. 05/30 04:29:10. <Main>: Maximum delay between retries
after deadlock: 30 seconds
I. 05/30 04:29:10. <Main>: Rowset size: 200
I. 05/30 04:29:10. <Main>: Upload cache size: 33554432 bytes
I. 05/30 04:29:10. <Main>: Download cache memory size:
134217728 bytes
I. 05/30 04:29:10. <Main>: Download cache directory size:
10485760 bytes
I. 05/30 04:29:10. <Main>: Number of worker threads: 20
I. 05/30 04:29:10. <Main>: Maximum number of threads
uploading concurrently: 20
W. 05/30 04:29:10. <Main>: Warning: Unknown users will be
added automatically (when there is no authenticate_user
script).
I. 05/30 04:29:10. <Main>: Example scripts will not be
automatically generated for unknown versions.
I. 05/30 04:29:10. <Main>: Local file for remote
synchronization logs: 'E:\MobilinkServer\r
emote_errors.txt'
I. 05/30 04:29:10. <Main>: Stream specifier 1:
tcpip& #123;keep_alive=3d1}

I. 05/30 04:29:10. <Main>: ODBC DBMS Name: Adaptive Server
Anywhere
I. 05/30 04:29:10. <Main>: ODBC DBMS Version: 09.00.0002
I. 05/30 04:29:10. <Main>: ODBC DBMS Driver Version:
09.00.0002
I. 05/30 04:29:10. <Main>: ODBC Version supported by the
driver: 3.52
I. 05/30 04:29:10. <Main>: Collation sequence of the
consolidated database is 'cp1252'
I. 05/30 04:29:10. <Main>: ODBC isolation set to: Read
Committed
I. 05/30 04:29:10. <Main>: Connected
E. 05/30 04:29:10. <Main>: Error: Invalid stream parameter
keep_alive for stream 1: tcpip& #123;keep_alive=3d1}

I. 05/30 04:29:10. <Main>: MobiLink server shutting down
I. 05/30 04:29:10. <Main>: MobiLink server undergoing hard
shutdown.
I. 05/30 04:29:10. <Main>: All connections and
synchronizations being terminated.
I. 05/30 04:29:12. <Main>: Disconnected
I. 05/30 04:29:12. <Main>: MobiLink server finished
Graham Hurst

2005-05-31, 11:24 am

Breck Carter wrote:
> Why is -x tcpip{keep_alive=1} invalid? This contradicts
> the Help which says it is ignored.


The documentation wasn't changed when we changed the stream layer to
report unused parameters as errors. It used to be that all unrecognized
stream parameters were quietly ignored. Now they cause errors.

We'll change the docs to say that parameter is no longer valid.

Cheers,

Graham
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com