Hi. ###### Again, your request/comments are not supposed to be written in a jira issue, because this is the place for the developers. Support-requests should be sent always to the jetspeed-user list. PLEASE do NOT comment the JIRA issue JS2-893 anymore for this regard. ######
I was mistaken, there IS a documentation regarding the cluster setup of Jetspeed: http://portals.apache.org/jetspeed-2/deployguide/config-cluster.html Can you confirm that the exception has something to do with the cluster configuration? I would recommend the following steps: With one Jetspeed installation: - install the Jetspeed distribution Check if the portal runs OK. - set up a second Jetspeed instance Check if both portals run OK. - make the changes to the distributed cache - change the Portlet Application Manager to use the VersionedPortletApplicationManager Check if both portals run OK. Regards, Joachim > thanks your answer! > > I follow your step,but login is error. > javax.security.auth.login.LoginException:The user null dose not exist > > > my env: > OS: windows xp > jdk:1.5 > server:tomcat6(jetspeed self install) > http: apache2.2 > database:oracle92 > > jetspeed.properties > > # Cache page manager override properties, (these override above legacy > properties if set) > # database page manager cache size: > org.apache.jetspeed.ehcache.pagemanager.maxelements=128 > # database page manager cache element expiration in seconds, (infinite = 0): > org.apache.jetspeed.ehcache.pagemanager.element.ttl=150 > # PSML page manager file cache size: > org.apache.jetspeed.ehcache.pagemanager.maxfiles=1000 > > #------------------------------------------------------------------------- > # C A C H E > #------------------------------------------------------------------------- > # cache configuration resource, ('ehcache.xml' or 'distributed-ehcache.xml' > supported by default): > org.apache.jetspeed.ehcache.config.resource=ehcache.xml > # distributed cache peer discovery multicast address: > org.apache.jetspeed.ehcache.group.address=230.0.0.1 > # distributed cache peer discovery multicast port: > org.apache.jetspeed.ehcache.group.port=4446 > # distributed cache peer discovery multicast TTL, (0=host, 1=subnet, ... see > ehcache.xml): > org.apache.jetspeed.ehcache.group.ttl=1 > # distributed cache peer hostname, (set to listen on specific interface): > org.apache.jetspeed.ehcache.hostname=localhost > # distributed cache peer port: > org.apache.jetspeed.ehcache.port=40001 Joachim Müller schrieb: > Hi Jones Ahk, > > Can you please post your requests in the mailing lists rather than > commenting an issue that is already resolved? Thx. > >> where have jetspeed2.2 cluster detail's document?? >> >> who can give me a document? thanks! > > There is no special cluster documentation as far as I know but > Jetspeed2.2 is cluster-ready. A few points to mention: > > - You have to use the database page manager (PSML, prefererences, > security constraints) > > - You can set up distributed caching (see ehcache configuration in > jetspeed.properties) > > - consider to use the VersionedPortletApplicationManager to avoid > conflicts during PA synchronization to the database from different nodes > > Regards, > Joachim > > -- . frankfurt am main, 21°c, zur zeit keine wolken unter 1500 m und keine kumulunimbus oder gewitterwolken. die sichtweite reicht weiter als 10 km. < joachim müller joac...@wemove.com t +49 69 759003 11 wemove digital solutions gmbh eschersheimer landstr. 5-7 60322 frankfurt am main amtsgericht frankfurt am main, hrb 53992 geschäftsführer joachim müller, stefan hartmann wemove digital solutions www.wemove.com --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
