D
dbeavon
Guest
When I need to make changes to the oepas1 configuration (eg. AVM parameters, propath, etc), I need to restart the entire pacific appserver (it isn't enough for the multi-session agent to restart). I can live with that, but what bothers me is that stopping and restarting the pacific appserver takes a ton of time - like a whole minute or two. I did a minimal amount of investigation; enough to see that adminserver (java) is launching numerous, consecutive powershell scripts, each of which is quite CPU-intensive. This unusual adminserver activity consists of the vast majority of the bottleneck in the stop/restart operations. I'd guess that the time that the TomCat java process itself takes to stop or start is only a minimal (5-10%) of the overall time, and the majority of the time is related to these wierd adminserver-spawned powershell scripts. I was wondering if this performance issue is typical in Windows or if there is something misconfigured on our Windows server (a 3.2 Ghz box, SSD, lots of ram). I though I'd ask the question since I'm sitting here waiting for PAS to restart and I have a few minutes to spare (and don't need a coffee refill yet). (Powershell scripts aren't good at doing tiny operations because the startup overhead is substantial. Is there any reason why OE PAS in Windows relies so heavily on powershell? Could this work - whatever it is - be rolled back into the adminserver java process itself? Or assuming that .Net is required, couldn't there be a separate "adminserverhelper" service that would perform the various small operations that are otherwise being done in powershell?)
Continue reading...
Continue reading...