G
Gareth Vincent
Guest
We eventually found out the root cause of this issue. There was a code change that was caching all printing templates back to the user's machine. In some instances the size of these templates amounted to around 80Mb. What was happening was if there was a slight drop in network while caching these templates it would cause the user's Session to remain in a READING state which then left the Agent session in an ACTIVE state. This problem was highlighted by some of our customers running on WAN connections running on PASOE. We were only able to reproduce this by physically unplugging the network cable when caching was taking place at the time of printing. I would like to think that PASOE would handle this better and simply timeout the connection at some point but this was not the case. Our DEV has now changed the code to only cache what is needed for the user. A part of me is glad that it was crashing as I’m not sure that we would have picked up the amount of data that was getting transferred to the end-user.
Continue reading...
Continue reading...