J
Jon Brock
Guest
I've got a web interface and some web services written in Java that communicate back to PASOE. After a few days, the heap is filling up with instances of com.progress.ubroker.client.HttpClientProtocol. Manually triggering garbage collection does not help. We are using a session-free connection and the dynamic API. I am calling _release() and releaseConnection() appropriately. I'm pretty sure all of that code is correct because this memory leak does not occur when using the traditional/legacy appserver, only PASOE. This occurs in 11.6 and 11.7. This is roughly the code path: // connection setup, this object is saved and used across multiple threads Connection connection = new Connection(url, "", "", ""); connection.setSessionModel(Connection.SM_SESSION_FREE); // individual call connection.setClientContextID(context); app = new OpenAppObject(connection, ""); ParamArray params = new ParamArray(...); app.runProc("something.p", params); app._release(); connection.releaseConnection(); One extra note, the connection object is recreated after a few hundred reuses (this was a workaround to deal with another memory leak with the legacy appserver). Has anybody run into this? Am I doing it wrong?
Continue reading...
Continue reading...