[jira] Issue Comment Edited: (JS2-893) cluster synchronization feature

    [ 
https://issues.apache.org/jira/browse/JS2-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737490#action_12737490
 ] 

hongkunan edited comment on JS2-893 at 7/31/09 3:56 AM:
--------------------------------------------------------

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


      was (Author: jones_ahk):
    thanks your answer!

I follow your step,but login is error.

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

  
> cluster synchronization feature
> -------------------------------
>
>                 Key: JS2-893
>                 URL: https://issues.apache.org/jira/browse/JS2-893
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Other
>    Affects Versions: 2.1.2, 2.1.3, 2.2.0
>            Reporter: Joachim MÃller
>            Assignee: Randy Watler
>             Fix For: 2.1.4, 2.2.0
>
>         Attachments: JS2-893_patch.zip
>
>
> We developed a cluster synchronization feature that is able to synchronize 
> the execution of an objects method cluster-wide. The approach is similar to 
> the spring transaction proxy, so we are able to AOP-inject the cluster 
> synchronization via spring configuration. The component is highly 
> customizable. A new database table is used for synchonization, but any other 
> data container (i.e. broadcast-distributed-hashmap) could be used.
> One main application for this functionality is the start of many jetspeed 
> cluster nodes and synchronize the deployment of the PAs to the database. 
> (Even with the VersionedApplicationManager we experienced DB constraints 
> failures on startup with fresh database, preventing the some PAs from 
> registration.)
> Patch follows (exists only for the 2.1.2-POSTRELEASE branch yet).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: jetspeed-dev-help@xxxxxxxxxxxxxxxxxx