I
Irfan
Guest
Has any one done any independent tests comparing the classic Appserver the OEPAS for 11.6. I have noticed a few things from a simple test on a windows PC running PAS and on Linux: - No application metrics available (logged with support) Were you looking for a metrics like localhost:16680/.../metrics - For PAS development mode 5 sessions are always started even if setting "max abl sessions per agent" to 1. What then happens is that only 1 of these sessions will be used If you want to start only 1 session, then you have to set two properties maxABLSessionsPerAgent=1 numInitialSessions=1 - Intermittent error with the progress.cfg file being locked thus stopping creation of new pas instance in OE Explorer with Java sevlet error. This occurs if creating/deleting PAS instances through OE explorer multiple times (logged with support). Stopping & starting adminserver sorts this. Should be a bug - The same agent session is always used if available is this expected behaviour. The classic appserver jumped about between agents but PAS will always use the same session if available from any number of different sessions. So in effect the one session could be used 90% of the time and the others very rarely.If this sessions fails due to a DB connection lost or for any other reason this would I suspect stop the appserver from working. If there are any memory leaks or the like then the one session will suffer from a build-up of problems rather than being shared out. I n PASOE, if a session is started and used while executing any client request then the same session will continue to be used if only 1 client request is sent overall. The behaviour is different to Classic Appserver as in Classic it tends to use all the started agents. In PASOE, a new session is used if it is only required to . - Performance appears to be less than the classic appserver: 63 vs 24 seconds on a test I ran with an empty test.p file ETIME(YES). DO i = 1 TO 100000: RUN test.p ON hServer. END. MESSAGE ETIME / 1000 VIEW-AS ALERT-BOX INFO BUTTONS OK. Performance gains on using PASOE can be observed based on load(concurrent clients & payloads). This way, you should be able to see the benefits of running a Multi-Session Agent. - Finally a simple question about how do we trim sessions for the agent. . The classic appserver jumped about between agents but PAS will always use the same session if available from any number of different sessions. So in effect the one session could be used 90% of the time and the others very rarely. As mentioned to you earlier, PASOE uses sessions based on number of client requests. If only 1 client request is executed, then there is no need for running a different session everytime. Considering this fact, there might be below reasons why a session has to be killed 1. Know if there is hung Client requests and terminate them - /oemanager/applications/ /clients?timeoutms=100000 2. Terminating any client session - /oemanager/applications/ /sessions?sessionID=&terminateOpt=1 3. Deleting free ABL Sessions in the Agent – in JMX SessionManager -> terminateFreeABLSessions 4. Terminate a given ABL session – We are working on this one, should be available soon
Continue reading...
Continue reading...