D
dbeavon
Guest
Currently I'm forced to bounce PASOE a few times a day. This is the instance of PASOE that is installed on my local workstation with PDSOE. What happens is that after a while of using it, the connections or sessions seem to be "leaked". I'm not sure what connections or sessions I'm dealing with because all the screens that I have access to show 1 or less. Below is the exception I get from .Net: Progress.Open4GL.Exceptions.RunTime4GLErrorException HResult=0x80131500 Message=ERROR condition: No connections available to process request. (7211) Source=Progress.o4glrt StackTrace: at Progress.Open4GL.Proxy.Procedure.RunPersistentProcedure(String requestID, String procName, ParameterSet params_Renamed, MetaSchema schema, Int32 stateModel) at Progress.Open4GL.Proxy.Procedure.RunPersistentProcedure(String procName, ParameterSet params_Renamed) ==== log (nothing in abl ms-agent log, only in the session mgr log): 14:07:21.067/4003832 [catalina-exec-5] ERROR com.progress.appserv.Session - LocalSession(97AEA49D755BD74E1BC5A0D28A5D4E76284608D618A7.oepas1) : timeout error occurred while reserving a connection = com.progress.appserv.broker.exception.BrokerException$NoAvailableConnectionsException: Agent:No Available Connections[cannot reserve connection]:Agent. (18298) It would be really nice to understand what exactly is being leaked. In OEE, there is often nothing shown under the "connections", "sessions", or "agents" for the abl application. On rare occasion I will see only one connection, but in the normal case I do not. In the tomcat manager there is also almost nothing of interest (screenshot). In the current scenario, it was "dev_lumbertrack_dkb" that was refusing connections. My hope is to understand what is going wrong so that if this ever happens in production we will know how to handle it. We will have a number of different abl apps and web apps running in the same tomcat instance so it will be extremely disruptive to just stop and restart the entire instance. I've tried reading thru the available docs but cannot find any clues about how to begin to troubleshoot whatever component has leaked connections (eg. https://knowledgebase.progress.com/servlet/fileField?id=0BEa0000000TisZ ) Here are some things I've tried, none of which will free up the APSV connections for use by my .Net openclient clients. *** Kill all ms-agents using oemanager: $OUT = Invoke-RestMethod -Method Delete -Uri (' http://localhost:' + $portnumber.ToString() + '/oemanager/applications/' + $ablapp + '/agents/' + $agent.agentId) -Credential $cred -ContentType "application/vnd.progress+json" *** stop/restart individual webapps *** use the tomcat manager (screenshot above) to expire tomcat sessions NONE of these operations will free up the imaginary connections which are supposedly unavailable . I was hoping to see something in the logs but they aren't all that helpful, beyond the message you see above. I will see what I can do to increase logging in the "session manager". But I had thought that stopping and restarting the webapp would essentially clear out the session manager. Does the session manager have a mechanism for resetting only *one* abl application at a time? Or would that require bouncing all of tomcat, as is my last resort? If anyone has suggestions about how to troubleshoot, I would greatly appreciate it. I think my current theory is that the session manager has been corrupted in some way, possibly over-counting my active connections and restricting me because it thinks I've surpassed the limit of 5. There hasn't been anything I can do to reset the session manager aside from bouncing the tomcat instance. I'd like a way to "reset" whatever portion of the session manager is responsible for this and see if I can get my tomcat to become responsive again. Any help would be much appreciated. Hopefully most of this question makes sense. I have only a few weeks of experience with OEPAS thus far, and only with the dev license.
Continue reading...
Continue reading...