Isode Events (Facility Detail)

Summary: Isode components write to logging streams when events occur.

Facility Tsap

Messages relating to the transport layer

NameSeverityIDDescriptionAction
AddressUnknownfatal103 The transport address presented is unknown.
BadITOTlengthfatal402The packet length in the ITOT packet header is incorrect. The connection is broken.
BadITOTversionfatal400The version number at the start of an ITOT TPKT was incorrect. The connection is broken.
BadMaxTPDUsizefatal302 The requested maximum TPDU size was invalid.
BadOperationwarning53 A transport layer parameter was incorrect.
BadParametererror52 A transport layer parameter was incorrect.
BadProviderfatal314There is some problem with the capabilities of the transport provider.
Congestionerror101 Lack of resources or some other transient problem caused a transport layer disconnection.
Duplicateerror231 An attempt to reuse the source reference for the same NSAPs was detected.
Errorerror12 OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event. See log entry for details
ErrorSerror28 OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event. See log entry for details
Fatalfatal13 OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event See Log entry for details. Please send information on the occurrence of this event to support@isode.com
FatalSfatal29 OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event. See Log entry for details. Please send information on the occurrence of this event to support@isode.com
Interruptinfo31 An operation was interrupted
InvalidLengtherror238 A length field in the transport PDU was found to be invalid.
ListenFailurefatal352There was a failure listening on the given address. The associated error gives more details.
Mismatcherror232 There was a problem with transport connection references.
ModuleMismatchfatal350When initializing a transport layer module, a mismatch was found between the name the loader thought was the module's name, and the actual name.
NConnectFailedwarning401When the NSAP address gives multiple actual addresses, the transport layer will attempt each address in turn. This message logs the failure of the initial addresses.
Negotiationfatal230 The transport providers failed to negotiate. Normally a result of a failure to agree a transport class.
NetDisconnecterror51 The network connection was lost.
NetRefusederror236 Failed to create the network connection over which the transport connection is made.
NoEndPointerror309 The transport provider does not use an end point which can be used with poll() or select().
NoFactoryfatal310The transport stack implementation lacks a factory method for the type of object required.
NoNSAPAddresserror301 There was no network address in the transport called address.
NoProvidererror308 The operation could not be performed as there was no transport service provider.
NormalDisconnectsuccess228 A normal transport layer disconnection.
NoSessionfatal102 The session entity is not attached to a TSAP.
NoStackfatal311There was no transport stack configured for the given network address.
Noticenotice6 General notice level event: See log entry for details No Operator Action
NoticeSnotice22 General notice level event: See log entry for details No Operator Action
NoTsapfatal312There was no transport stack configured for the given network address.
NotSpecifiederror100 A transport level disconnect was sent with no specific reason.
NoUserfatal300 There was no TS User object available for the transport layer. This is a programming error.
Overflowerror235 It was not possible to assign a connection reference as there were too many assigned.
Protocolerror233 A protocol error was detected.
RejectBadParamerror304 A received TPDU has an unknown parameter field.
RejectBadTypeerror305 A received TPDU has an unknown TPDU type field.
RejectBadValueerror306 A received TPDU has an invalid value for the given field
RejectReceivederror307The peer system rejected a TPDU for the reason given.
RejectUnspecifiederror303 A received TPDU was rejected for no specific overall reason, more detail is given in the context.
RemoteCongestionerror229 Lack of resources or some other transient problem caused a transport layer disconnection.
RestoreFailurefatal351 There was a failure when rebuilding the information for a transport endpoint following transfer of the endpoint to another process.
Tailoringfatal313There is a value error in the loading the tailoring for the transport provider module. If the value is <missing> then a mandatory value is missing from the tailoring file.
Timerinfo30 A timeout was encountered.
TPDUpdu2Transport PDUNo Operator Action
UserDatainfo54
Waitingwarning32 There are indications waiting

Fatal

Message Text
  • %1
Parameters
  1. Text describing error
Description
OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event
Action
See Log entry for details. Please send information on the occurrence of this event to support@isode.com

Error

Message Text
  • %1
Parameters
  1. Text describing error
Description
OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event.
Action
See log entry for details

Notice

Message Text
  • %1
Parameters
  1. Text describing condition
Description
General notice level event: See log entry for details
Action
No Operator Action

TPDU

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Transport PDU
Action
No Operator Action

FatalS

Message Text
  • %1 %2
Parameters
  1. Text describing error
  2. Additional text field
Description
OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event.
Action
See Log entry for details. Please send information on the occurrence of this event to support@isode.com

ErrorS

Message Text
  • %1 %2
Parameters
  1. Text describing error
  2. Additional text field
Description
OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event.
Action
See log entry for details

NoticeS

Message Text
  • %1 %2
Parameters
  1. Text describing condition
  2. Additional text field
Description
General notice level event: See log entry for details
Action
No Operator Action

Timer

Message Text
  • Timeout waiting for operation (%1)
Parameters
  1. Bit mask of network level events which are awaited
Description
A timeout was encountered.
Action

Interrupt

Message Text
  • Operation interrupted
Description
An operation was interrupted
Action

Waiting

Message Text
  • Indications waiting
Description
There are indications waiting
Action

NetDisconnect

Message Text
  • Network disconnect
Description
The network connection was lost.
Action

BadParameter

Message Text
  • Bad Parameter
Description
A transport layer parameter was incorrect.
Action

BadOperation

Message Text
  • Invalid operation
Description
A transport layer parameter was incorrect.
Action

UserData

Message Text
  • [%1]
Parameters
  1. Data from transport peer
Description
Action

NotSpecified

Message Text
  • Reason not specified
Description
A transport level disconnect was sent with no specific reason.
Action

Congestion

Message Text
  • Congestion at TSAP
Description
Lack of resources or some other transient problem caused a transport layer disconnection.
Action

NoSession

Message Text
  • Session entity not attached to TSAP
Description
The session entity is not attached to a TSAP.
Action

AddressUnknown

Message Text
  • TSAP Address unknown
Description
The transport address presented is unknown.
Action

NormalDisconnect

Message Text
  • Normal disconnect initiated by session entity
Description
A normal transport layer disconnection.
Action

RemoteCongestion

Message Text
  • Remote transport entity congestion at connect request time
Description
Lack of resources or some other transient problem caused a transport layer disconnection.
Action

Negotiation

Message Text
  • Connection negotiation failed
Description
The transport providers failed to negotiate. Normally a result of a failure to agree a transport class.
Action

Duplicate

Message Text
  • Duplicate source reference for same pair of NSAPs
Description
An attempt to reuse the source reference for the same NSAPs was detected.
Action

Mismatch

Message Text
  • Mismatched references
Description
There was a problem with transport connection references.
Action

Protocol

Message Text
  • Protocol Error
Description
A protocol error was detected.
Action

Overflow

Message Text
  • Reference overflow
Description
It was not possible to assign a connection reference as there were too many assigned.
Action

NetRefused

Message Text
  • Connection request refused on this network connection
Description
Failed to create the network connection over which the transport connection is made.
Action

InvalidLength

Message Text
  • Head or parameter length invalid
Description
A length field in the transport PDU was found to be invalid.
Action

NoUser

Message Text
  • No TS User for operation %1
Parameters
  1. Operation in progress when error found
Description
There was no TS User object available for the transport layer. This is a programming error.
Action

NoNSAPAddress

Message Text
  • Missing network address
Description
There was no network address in the transport called address.
Action

BadMaxTPDUsize

Message Text
  • Invalid Maximum TPDU size %1
Parameters
  1. Requested maximum TPDU size
Description
The requested maximum TPDU size was invalid.
Action

RejectUnspecified

Message Text
  • TPDU rejected %1
Parameters
  1. Context for rejection
Description
A received TPDU was rejected for no specific overall reason, more detail is given in the context.
Action

RejectBadParam

Message Text
  • TPDU has unknown parameter type %1
Parameters
  1. parameter type value
Description
A received TPDU has an unknown parameter field.
Action

RejectBadType

Message Text
  • TPDU has unknown TPDU type %1
Parameters
  1. type value
Description
A received TPDU has an unknown TPDU type field.
Action

RejectBadValue

Message Text
  • TPDU has bad value for %1
Parameters
  1. value type
Description
A received TPDU has an invalid value for the given field
Action

RejectReceived

Message Text
  • Peer rejected TPDU, reason %1
Parameters
  1. The reject reason
Description
The peer system rejected a TPDU for the reason given.
Action

NoProvider

Message Text
  • No Transport Provider
Description
The operation could not be performed as there was no transport service provider.
Action

NoEndPoint

Message Text
  • No pollable end point
Description
The transport provider does not use an end point which can be used with poll() or select().
Action

NoFactory

Message Text
  • No factory method to make Transport %1
Parameters
  1. The type of factory required
Description
The transport stack implementation lacks a factory method for the type of object required.
Action

NoStack

Message Text
  • No Transport Stack for address %1
Parameters
  1. The network address which failed
Description
There was no transport stack configured for the given network address.
Action

NoTsap

Message Text
  • No Transport Listener for TSEL '%1'H
Parameters
  1. The selector which was not found (in hex)
Description
There was no transport stack configured for the given network address.
Action

Tailoring

Message Text
  • Tailoring error for %1, %2: %3
Parameters
  1. The name of the module
  2. The name of the item
  3. The value for the item
Description
There is a value error in the loading the tailoring for the transport provider module. If the value is <missing> then a mandatory value is missing from the tailoring file.
Action

BadProvider

Message Text
  • Problem with transport provider %1, %2
Parameters
  1. The name of the module
  2. Information about the problem with the provider
Description
There is some problem with the capabilities of the transport provider.
Action

ModuleMismatch

Message Text
  • Transport module name mismatch proposed=%1 actual=%2
Parameters
  1. The provided module name
  2. The name of the module being loaded
Description
When initializing a transport layer module, a mismatch was found between the name the loader thought was the module's name, and the actual name.
Action

RestoreFailure

Message Text
  • Failed to restore using %1 in module %2
Parameters
  1. The provided save information
  2. The name of the module doing the restoration
Description
There was a failure when rebuilding the information for a transport endpoint following transfer of the endpoint to another process.
Action

ListenFailure

Message Text
  • Failure listening on %1
Parameters
  1. The address being attempted
Description
There was a failure listening on the given address. The associated error gives more details.
Action

BadITOTversion

Message Text
  • Bad ITOT version number %1
Parameters
  1. The provided version number
Description
The version number at the start of an ITOT TPKT was incorrect. The connection is broken.
Action

NConnectFailed

Message Text
  • Failed to connect to address %1
Parameters
  1. Failed network address
Description
When the NSAP address gives multiple actual addresses, the transport layer will attempt each address in turn. This message logs the failure of the initial addresses.
Action

BadITOTlength

Message Text
  • Bad ITOT packet length %1
Parameters
  1. The presented packet length
Description
The packet length in the ITOT packet header is incorrect. The connection is broken.
Action

All rights reserved © 2002 - 2024 Isode Ltd.