test

Sun Java System Messaging Server 6.3 Administration Guide

C.5.8.3 Miscellaneous

These are miscellaneous options:

DEBUG

(integer, bitmask) Enable debug output. The default value is 6 which selects warning and error messages.

Table C–21 defines the bit values of the DEBUG bitmask.

Table C–21 DEBUG Bitmask

Bit  

Value  

Description  

0-31 

-1

Extremely verbose output 

0 

1

Informational messages 

1 

2

Warning messages 

3 

4

Error messages 

3 

8

Subroutine call tracing 

4 

16

Hash table diagnostics 

5 

32

I/O diagnostics, receive 

6 

64

I/O diagnostics, transmit 

7 

128

SMS to email conversion diagnostics (mobile originate and SMS notification) 

8 

256

PDU diagnostics, header data 

9 

512

PDU diagnostics, body data 

10 

1024

PDU diagnostics, type-length-value data 

11 

2048 

Option processing; sends all option settings to the log file. 

LISTEN_CONNECTION_MAX

(integer, >= 0) The maximum number of concurrent, inbound TCP connections to allow across all SMPP relay and server instantiations. A value of 0 (zero) indicates that there is no global limit on the number of connections. There may, however, be per relay or server limits imposed by a given relay or server instantiation. Default: 10,000

LOG_PAGE_COUNT

(0, 1, 2) The LOG_PAGE_CONT SMS channel option only takes effect when logging is enabled for the channel with the logging channel keyword. When logging is enabled, this option controls the value recorded in the mail.log file's message size field. Normally that field gives the block size of the underlying message file. When LOG_PAGE_COUNT has a non-zero value, the number of transmitted pages will instead be recorded in that field of the log file.

0 - Log the block size of the underlying message file. This is the default behavior when LOG_PAGE_COUNT is not specified.

1 - Log the count of pages sent when the entire message is successfully transmitted to the recipient. Otherwise, log a page count of zero even if some pages were sent to the recipient.

2 - Log the count of pages sent to the recipient regardless of whether or not the entire message was sent.

The distinction between LOG_PAGE_COUNT=1 and LOG_PAGE_COUNT=2 is only relevant when a message is sufficiently large that it will be transmitted as several pages. In that case, it is possible that before transmitting all the pages an error might occur. For example, the network between the MTA and the remote SMPP server goes down. In that case, a later retransmission attempt will be made for the message. For each attempt, the previously sent pages are sent again along with the pages which were not sent. Sites may choose whether or not they want to record the count of pages successfully sent during these failed delivery attempts.