How to Allow More Transactions Per Session On a Per-Channel Basis
(Doc ID 1933283.1)
Last updated on SEPTEMBER 30, 2019
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
We have a tcp_local_option file with some settings in it including:
We want to have different / greater limitation on a different channel.
We created an identical tcp_newchannel_option file but, excluded the ALLOW_TRANSACTIONS_PER_SESSION expecting this channel to use the default value (no limit).
Traffic is coming to port 25, tcp_local and then it switches to tcp_newchannel and the different limitation value in tcp_newchannel_option.
It seems to use the limitation of the first channel used, the channel associated with the port where the connection is made, in this case tcp_local and the tcp_local_option values.
We also tried setting transactionlimit 15 on the tcp_newchannel, but there is still an error after 10 transactions.
Set transactionlimit to 5 on the newchannel, we get the error after 5.
So, it seems it can restrict up to the maximum set in the option file, but not allow more transactions.
How can we allow more transactions on this new channel?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document