yoshi66
asked on
BES question
Hi
We are running BES 4.1.5
We have a couple of servers and about 2000 devices.
I have a query regarding the way the BES servers speak to the devices, via the RIM server. Is a seperate connection opened up on port 3101 between the BES and the RIM server, or is it just one connection?
The reason I ask is that I am receiving the following error messages on my BES;
[SERVICE_RELAY_SESSION:xxx :xxx] Service transaction not found. SERVICESESSION_TAG=xx
This only happens after reboots for about an hour or so, apparently they are due to dropped packets after a device has authenticated, but I was curious.
Cheers
We are running BES 4.1.5
We have a couple of servers and about 2000 devices.
I have a query regarding the way the BES servers speak to the devices, via the RIM server. Is a seperate connection opened up on port 3101 between the BES and the RIM server, or is it just one connection?
The reason I ask is that I am receiving the following error messages on my BES;
[SERVICE_RELAY_SESSION:xxx
This only happens after reboots for about an hour or so, apparently they are due to dropped packets after a device has authenticated, but I was curious.
Cheers
ASKER
Hi there
Thanks...just one clarification question; When you say that the data packets were in transmission before the server was rebooted, do you mean from the BES server to RIM, or RIM to the BES server? And what sort of data would this be?
Thanks...just one clarification question; When you say that the data packets were in transmission before the server was rebooted, do you mean from the BES server to RIM, or RIM to the BES server? And what sort of data would this be?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So, that may not have made a lot of sense, but the end result is this... dont worry about it. Any data that didnt get there during the reboot would be requeued and transmitted shortly afterward anyway. I let all of my techs know to expect these errors and ignore them if they appear after a reboot.