Entering content frame

Background documentation JMS Provider Service Locate the document in its SAP Library structure

The JMS Provider Service enables you to manage the JMS destinations and connection factories on SAP J2EE Engine.

This service runs on both the server and dispatcher.

Caution

Each working destination (the one with at least one producer/consumer) may take up to sizeLimitInMasterQueue bytes, which means that you should ensure that N * sizeLimitInMasterQueue (where N is the number of expected working destinations) does not exceed the virtual machine heap size.

Server

Property

Description

Default Value

agentThreadCount

The maximum number of threads that can work simultaneously to deliver messages to the destinations.

10

cleanUpServiceSleepInterval

The time interval in milliseconds after which the Clean Up service is called.

600000

messageExpirationDelta

Removes all expired messages before (currentTime – messageExpirationDelta). The time interval is in milliseconds.

600000

clientMemorySize

The total amount of memory the client can distribute in the buffer.

10485760

clientConsumerBuffer

The size of the buffer the client can use.

102400

countLimitInMasterQueue

The limit of the number of messages in the master queue.

32000

sizeLimitInMasterQueue

The total size of the messages in the master queue.

1048576

fetchSizeOnStartupInMasterQueue

The number of messages that are loaded at startup of a destination.

4096

maxFetchSizeInMasterQueue

The maximum size of the loaded messages at startup of a destination.

1024

transactionStorePath

Defines the directory with enough free space where the transactions are to be written.

 

 

Dispatcher

Property

Description

Default Value

/tcp

The port on which the JMS Provider opens a socket.

1139

 

See also:

 

JMS Administration in the Administration Manual

 

Leaving content frame