When I do message monitoring in RWB for a longer duration(say 3hrs or more) , it times out. Of course the system resource and volume of data have impact on this but cant change either at this point. So as a work around, can we increase the time out value somewhere (may be in the Visual admin) ?
My only worry is, if it is the actual servlet(which is responsible for the action) which is timing out due to long running SQL query then we may not be able to do much, as its timeout value comes from a container wide(global) parameter for all servlets, which I would imagine is going to be not advisable to change ?
Thanks in advance