M
mroberts@rev.com.au
Guest
We do this a lot, and do not have issues with running multiple PAS instances In our case, we have scripted the deploy so the webapps and config (except for ports) are the same, and each PAS instance works independently Places to look are Colliding JSESSIONID's ... both PAS instances are configures in $PAS/conf/context.xml to use sessionCookieName JSESSIONID ... the default I believe. As soon as we created a second instance, we had session issues where the same session cookie was used for both instances, and we logged into pas1 but hit issues when we hit pas2, logged in, then pas1 stopped working. We had to amend our context.xml to have a different sessionCookieName for each instance or The browser then maintains a different session cookie for each instance, and they recognize their respective sessionid's. $PAS/logs/app.agent.log ... verify that the agent on the second pas instance is running as expected, and not spitting out runtime errors (db not connected, insufficient resource on db etc) $pas/logs/catalina.out ... look for any errors here .. we occasionally didn't properly "separate" the pas instances, and there was a conflict on port assignments. Errors any any of the above can cause a PAS instance top look like it is running, but not be "completely there" Mark
Continue reading...
Continue reading...