Revision: 15687
Author: [email protected]
Date: Thu Dec 9 08:58:48 2010
Log: Update Issue 1872
Fixing NPE and adding non regression test
http://code.google.com/p/mobicents/source/detail?r=15687
Added:
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-1.xml
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-2.xml
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-3.xml
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/start-jboss-5-server-node3.sh
Modified:
/trunk/servers/sip-servlets/sip-servlets-jboss5/src/main/java/org/jboss/web/tomcat/service/session/ClusteredSipApplicationSession.java
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/prepare-jboss-5-server-for-clustering-failover.sh
=======================================
--- /dev/null
+++
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-1.xml
Thu Dec 9 08:58:48 2010
@@ -0,0 +1,184 @@
+<Server>
+
+ <!-- Optional listener which ensures correct init and shutdown of APR,
+ and provides information if it is not installed -->
+ <Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
+ <!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
+ <Listener className="org.apache.catalina.core.JasperListener" />
+
+ <Service name="jboss.web"
+ className="org.mobicents.servlet.sip.startup.SipStandardService"
+ balancers="127.0.0.1"
+ sipPathName="org.mobicents.ha"
+
sipApplicationDispatcherClassName="org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl"
+ concurrencyControlMode="SipApplicationSession"
+ congestionControlCheckingInterval="-1"
+
darConfigurationFileLocation="conf/dars/distributable-dar.properties"
+ sipStackPropertiesFile="conf/mss-sip-stack.properties">
+
+ <!-- A HTTP/1.1 Connector on port 8080 -->
+ <Connector protocol="HTTP/1.1" port="8080"
address="${jboss.bind.address}"
+ connectionTimeout="20000" redirectPort="8443" />
+
+ <!-- Add this option to the connector to avoid problems with
+ .NET clients that don't implement HTTP/1.1 correctly
+ restrictedUserAgents="^.*MS Web Services Client Protocol
1.1.4322.*$"
+ -->
+
+ <!-- A AJP 1.3 Connector on port 8009 -->
+ <Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
+ redirectPort="8443" />
+
+ <!-- SSL/TLS Connector configuration using the admin devl guide
keystore
+ <Connector protocol="HTTP/1.1" SSLEnabled="true"
+ port="8443" address="${jboss.bind.address}"
+ scheme="https" secure="true" clientAuth="false"
+ keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
+ keystorePass="rmi+ssl" sslProtocol = "TLS" />
+ -->
+
+ <!-- Define a SIP Connector -->
+ <Connector port="5080"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="udp"/>
+
+<!-- Define the default TCP SIP Connector -->
+ <Connector port="5080"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="tcp"/>
+
+
+ <Engine name="jboss.web" defaultHost="localhost"
className="org.mobicents.servlet.sip.startup.SipStandardEngine"
jvmRoute="node1">
+
+ <!-- The JAAS based authentication and authorization realm
implementation
+ that is compatible with the jboss 3.2.x realm implementation.
+ - certificatePrincipal : the class name of the
+ org.jboss.security.auth.certs.CertificatePrincipal impl
+ used for mapping X509[] cert chains to a Princpal.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ -->
+ <Realm className="org.jboss.web.tomcat.security.JBossWebRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ <!-- A subclass of JBossSecurityMgrRealm that uses the
authentication
+ behavior of JBossSecurityMgrRealm, but overrides the authorization
+ checks to use JACC permissions with the current
java.security.Policy
+ to determine authorized access.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ <Realm
className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ -->
+
+ <Host name="localhost"
hostConfigClass="org.mobicents.servlet.sip.startup.SipHostConfig"
+
configClass="org.mobicents.servlet.sip.startup.jboss.SipJBossContextConfig"
+ xmlNamespaceAware="true">
+
+ <!-- Uncomment to enable request dumper. This Valve "logs
interesting
+ contents from the specified Request (before processing)
and the
+ corresponding Response (after processing). It is
especially useful
+ in debugging problems related to headers and cookies."
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.valves.RequestDumperValve" />
+ -->
+
+ <!-- Access logger -->
+ <!--
+ <Valve className="org.apache.catalina.valves.AccessLogValve"
+ prefix="localhost_access_log." suffix=".log"
+ pattern="common" directory="${jboss.server.log.dir}"
+ resolveHosts="false" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host. Does not provide SSO across a
cluster.
+
+ If this valve is used, do not use the JBoss
ClusteredSingleSignOn
+ valve shown below.
+
+ A new configuration attribute is available beginning with
+ release 4.0.4:
+
+ cookieDomain configures the domain to which the SSO cookie
+ will be scoped (i.e. the set of hosts to
+ which the cookie will be presented). By
default
+ the cookie is scoped to "/", meaning the host
+ that presented it. Set cookieDomain to a
+ wider domain (e.g. "xyz.com") to allow an SSO
+ to span more than one hostname.
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.authenticator.SingleSignOn" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host AND to all other hosts in the cluster.
+
+ If this valve is used, do not use the standard Tomcat
SingleSignOn
+ valve shown above.
+
+ Valve uses a JBossCache instance to support SSO credential
+ caching and replication across the cluster. The JBossCache
+ instance must be configured separately. See the
+ "jboss-web-clusteredsso-beans.xml" file in the
+ server/all/deploy directory for cache configuration details.
+
+ Besides the attributes supported by the standard Tomcat
+ SingleSignOn valve (see the Tomcat docs), this version also
+ supports the following attributes:
+
+ cookieDomain see above
+
+ treeCacheName JMX ObjectName of the JBossCache MBean used
to
+ support credential caching and replication
across
+ the cluster. If not set, the default value is
+ "jboss.cache:service=ClusteredSSOCache"
+
+ maxEmptyLife The maximum number of seconds an SSO with no
+ active sessions will be usable by a request
+
+ processExpiresInterval The minimum number of seconds between
+ efforts by the valve to find and invalidate
+ SSO's that have exceeded
their 'maxEmptyLife'.
+ Does not imply effort will be spent on such
+ cleanup every 'processExpiresInterval'.
+ -->
+ <!--
+ <Valve
className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+ -->
+
+ <!-- Check for unclosed connections and transaction terminated
checks
+ in servlets/jsps.
+
+ Important: The dependency on the CachedConnectionManager
+ in META-INF/jboss-service.xml must be uncommented, too
+ -->
+
+ <Valve
className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
+
cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
+
transactionManagerObjectName="jboss:service=TransactionManager" />
+
+ </Host>
+
+ </Engine>
+
+ </Service>
+
+</Server>
=======================================
--- /dev/null
+++
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-2.xml
Thu Dec 9 08:58:48 2010
@@ -0,0 +1,184 @@
+<Server>
+
+ <!-- Optional listener which ensures correct init and shutdown of APR,
+ and provides information if it is not installed -->
+ <Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
+ <!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
+ <Listener className="org.apache.catalina.core.JasperListener" />
+
+ <Service name="jboss.web"
+ className="org.mobicents.servlet.sip.startup.SipStandardService"
+ balancers="127.0.0.1"
+ sipPathName="org.mobicents.ha"
+
sipApplicationDispatcherClassName="org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl"
+ concurrencyControlMode="SipApplicationSession"
+ congestionControlCheckingInterval="-1"
+
darConfigurationFileLocation="conf/dars/distributable-dar.properties"
+ sipStackPropertiesFile="conf/mss-sip-stack.properties">
+
+ <!-- A HTTP/1.1 Connector on port 8080 -->
+ <Connector protocol="HTTP/1.1" port="8080"
address="${jboss.bind.address}"
+ connectionTimeout="20000" redirectPort="8443" />
+
+ <!-- Add this option to the connector to avoid problems with
+ .NET clients that don't implement HTTP/1.1 correctly
+ restrictedUserAgents="^.*MS Web Services Client Protocol
1.1.4322.*$"
+ -->
+
+ <!-- A AJP 1.3 Connector on port 8009 -->
+ <Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
+ redirectPort="8443" />
+
+ <!-- SSL/TLS Connector configuration using the admin devl guide
keystore
+ <Connector protocol="HTTP/1.1" SSLEnabled="true"
+ port="8443" address="${jboss.bind.address}"
+ scheme="https" secure="true" clientAuth="false"
+ keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
+ keystorePass="rmi+ssl" sslProtocol = "TLS" />
+ -->
+
+ <!-- Define a SIP Connector -->
+ <Connector port="5081"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="udp" />
+
+ <!-- Define the default TCP SIP Connector -->
+ <Connector port="5081"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="tcp" />
+
+
+ <Engine name="jboss.web" defaultHost="localhost"
className="org.mobicents.servlet.sip.startup.SipStandardEngine"
jvmRoute="node2">
+
+ <!-- The JAAS based authentication and authorization realm
implementation
+ that is compatible with the jboss 3.2.x realm implementation.
+ - certificatePrincipal : the class name of the
+ org.jboss.security.auth.certs.CertificatePrincipal impl
+ used for mapping X509[] cert chains to a Princpal.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ -->
+ <Realm className="org.jboss.web.tomcat.security.JBossWebRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ <!-- A subclass of JBossSecurityMgrRealm that uses the
authentication
+ behavior of JBossSecurityMgrRealm, but overrides the authorization
+ checks to use JACC permissions with the current
java.security.Policy
+ to determine authorized access.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ <Realm
className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ -->
+
+ <Host name="localhost"
hostConfigClass="org.mobicents.servlet.sip.startup.SipHostConfig"
+
configClass="org.mobicents.servlet.sip.startup.jboss.SipJBossContextConfig"
+ xmlNamespaceAware="true">
+
+ <!-- Uncomment to enable request dumper. This Valve "logs
interesting
+ contents from the specified Request (before processing)
and the
+ corresponding Response (after processing). It is
especially useful
+ in debugging problems related to headers and cookies."
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.valves.RequestDumperValve" />
+ -->
+
+ <!-- Access logger -->
+ <!--
+ <Valve className="org.apache.catalina.valves.AccessLogValve"
+ prefix="localhost_access_log." suffix=".log"
+ pattern="common" directory="${jboss.server.log.dir}"
+ resolveHosts="false" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host. Does not provide SSO across a
cluster.
+
+ If this valve is used, do not use the JBoss
ClusteredSingleSignOn
+ valve shown below.
+
+ A new configuration attribute is available beginning with
+ release 4.0.4:
+
+ cookieDomain configures the domain to which the SSO cookie
+ will be scoped (i.e. the set of hosts to
+ which the cookie will be presented). By
default
+ the cookie is scoped to "/", meaning the host
+ that presented it. Set cookieDomain to a
+ wider domain (e.g. "xyz.com") to allow an SSO
+ to span more than one hostname.
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.authenticator.SingleSignOn" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host AND to all other hosts in the cluster.
+
+ If this valve is used, do not use the standard Tomcat
SingleSignOn
+ valve shown above.
+
+ Valve uses a JBossCache instance to support SSO credential
+ caching and replication across the cluster. The JBossCache
+ instance must be configured separately. See the
+ "jboss-web-clusteredsso-beans.xml" file in the
+ server/all/deploy directory for cache configuration details.
+
+ Besides the attributes supported by the standard Tomcat
+ SingleSignOn valve (see the Tomcat docs), this version also
+ supports the following attributes:
+
+ cookieDomain see above
+
+ treeCacheName JMX ObjectName of the JBossCache MBean used
to
+ support credential caching and replication
across
+ the cluster. If not set, the default value is
+ "jboss.cache:service=ClusteredSSOCache"
+
+ maxEmptyLife The maximum number of seconds an SSO with no
+ active sessions will be usable by a request
+
+ processExpiresInterval The minimum number of seconds between
+ efforts by the valve to find and invalidate
+ SSO's that have exceeded
their 'maxEmptyLife'.
+ Does not imply effort will be spent on such
+ cleanup every 'processExpiresInterval'.
+ -->
+ <!--
+ <Valve
className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+ -->
+
+ <!-- Check for unclosed connections and transaction terminated
checks
+ in servlets/jsps.
+
+ Important: The dependency on the CachedConnectionManager
+ in META-INF/jboss-service.xml must be uncommented, too
+ -->
+
+ <Valve
className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
+
cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
+
transactionManagerObjectName="jboss:service=TransactionManager" />
+
+ </Host>
+
+ </Engine>
+
+ </Service>
+
+</Server>
=======================================
--- /dev/null
+++
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/setup/jboss-5/server-jboss-5-failover-cc-sas-port-3.xml
Thu Dec 9 08:58:48 2010
@@ -0,0 +1,184 @@
+<Server>
+
+ <!-- Optional listener which ensures correct init and shutdown of APR,
+ and provides information if it is not installed -->
+ <Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
+ <!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
+ <Listener className="org.apache.catalina.core.JasperListener" />
+
+ <Service name="jboss.web"
+
className="org.mobicents.servlet.sip.startup.failover.SipStandardBalancerNodeService"
+ balancers="127.0.0.1"
+ sipPathName="org.mobicents.ha"
+
sipApplicationDispatcherClassName="org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl"
+ concurrencyControlMode="SipApplicationSession"
+ congestionControlCheckingInterval="-1"
+
darConfigurationFileLocation="conf/dars/distributable-dar.properties"
+ sipStackPropertiesFile="conf/mss-sip-stack.properties">
+
+ <!-- A HTTP/1.1 Connector on port 8080 -->
+ <Connector protocol="HTTP/1.1" port="8080"
address="${jboss.bind.address}"
+ connectionTimeout="20000" redirectPort="8443" />
+
+ <!-- Add this option to the connector to avoid problems with
+ .NET clients that don't implement HTTP/1.1 correctly
+ restrictedUserAgents="^.*MS Web Services Client Protocol
1.1.4322.*$"
+ -->
+
+ <!-- A AJP 1.3 Connector on port 8009 -->
+ <Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
+ redirectPort="8443" />
+
+ <!-- SSL/TLS Connector configuration using the admin devl guide
keystore
+ <Connector protocol="HTTP/1.1" SSLEnabled="true"
+ port="8443" address="${jboss.bind.address}"
+ scheme="https" secure="true" clientAuth="false"
+ keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
+ keystorePass="rmi+ssl" sslProtocol = "TLS" />
+ -->
+
+ <!-- Define a SIP Connector -->
+ <Connector port="5082"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="udp"/>
+
+ <!-- Define the default TCP SIP Connector -->
+ <Connector port="5082"
+ ipAddress = "${jboss.bind.address}"
+ protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler"
+ signalingTransport="tcp"/>
+
+
+ <Engine name="jboss.web" defaultHost="localhost"
className="org.mobicents.servlet.sip.startup.SipStandardEngine"
jvmRoute="node2">
+
+ <!-- The JAAS based authentication and authorization realm
implementation
+ that is compatible with the jboss 3.2.x realm implementation.
+ - certificatePrincipal : the class name of the
+ org.jboss.security.auth.certs.CertificatePrincipal impl
+ used for mapping X509[] cert chains to a Princpal.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ -->
+ <Realm className="org.jboss.web.tomcat.security.JBossWebRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ <!-- A subclass of JBossSecurityMgrRealm that uses the
authentication
+ behavior of JBossSecurityMgrRealm, but overrides the authorization
+ checks to use JACC permissions with the current
java.security.Policy
+ to determine authorized access.
+ - allRolesMode : how to handle an auth-constraint with a
role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which
requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there
are no
+ web-app/security-roles
+ <Realm
className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"
+
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ -->
+
+ <Host name="localhost"
hostConfigClass="org.mobicents.servlet.sip.startup.SipHostConfig"
+
configClass="org.mobicents.servlet.sip.startup.jboss.SipJBossContextConfig"
+ xmlNamespaceAware="true">
+
+ <!-- Uncomment to enable request dumper. This Valve "logs
interesting
+ contents from the specified Request (before processing)
and the
+ corresponding Response (after processing). It is
especially useful
+ in debugging problems related to headers and cookies."
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.valves.RequestDumperValve" />
+ -->
+
+ <!-- Access logger -->
+ <!--
+ <Valve className="org.apache.catalina.valves.AccessLogValve"
+ prefix="localhost_access_log." suffix=".log"
+ pattern="common" directory="${jboss.server.log.dir}"
+ resolveHosts="false" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host. Does not provide SSO across a
cluster.
+
+ If this valve is used, do not use the JBoss
ClusteredSingleSignOn
+ valve shown below.
+
+ A new configuration attribute is available beginning with
+ release 4.0.4:
+
+ cookieDomain configures the domain to which the SSO cookie
+ will be scoped (i.e. the set of hosts to
+ which the cookie will be presented). By
default
+ the cookie is scoped to "/", meaning the host
+ that presented it. Set cookieDomain to a
+ wider domain (e.g. "xyz.com") to allow an SSO
+ to span more than one hostname.
+ -->
+ <!--
+ <Valve
className="org.apache.catalina.authenticator.SingleSignOn" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host AND to all other hosts in the cluster.
+
+ If this valve is used, do not use the standard Tomcat
SingleSignOn
+ valve shown above.
+
+ Valve uses a JBossCache instance to support SSO credential
+ caching and replication across the cluster. The JBossCache
+ instance must be configured separately. See the
+ "jboss-web-clusteredsso-beans.xml" file in the
+ server/all/deploy directory for cache configuration details.
+
+ Besides the attributes supported by the standard Tomcat
+ SingleSignOn valve (see the Tomcat docs), this version also
+ supports the following attributes:
+
+ cookieDomain see above
+
+ treeCacheName JMX ObjectName of the JBossCache MBean used
to
+ support credential caching and replication
across
+ the cluster. If not set, the default value is
+ "jboss.cache:service=ClusteredSSOCache"
+
+ maxEmptyLife The maximum number of seconds an SSO with no
+ active sessions will be usable by a request
+
+ processExpiresInterval The minimum number of seconds between
+ efforts by the valve to find and invalidate
+ SSO's that have exceeded
their 'maxEmptyLife'.
+ Does not imply effort will be spent on such
+ cleanup every 'processExpiresInterval'.
+ -->
+ <!--
+ <Valve
className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+ -->
+
+ <!-- Check for unclosed connections and transaction terminated
checks
+ in servlets/jsps.
+
+ Important: The dependency on the CachedConnectionManager
+ in META-INF/jboss-service.xml must be uncommented, too
+ -->
+
+ <Valve
className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
+
cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
+
transactionManagerObjectName="jboss:service=TransactionManager" />
+
+ </Host>
+
+ </Engine>
+
+ </Service>
+
+</Server>
=======================================
--- /dev/null
+++
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/start-jboss-5-server-node3.sh
Thu Dec 9 08:58:48 2010
@@ -0,0 +1,4 @@
+#export JBOSS_HOME=/home/deruelle/servers/jboss-5.1.0.CR1
+export JAVA_OPTS="-Xms1024m -Xmx1024m -XX:PermSize=128M
-XX:MaxPermSize=256M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode"
+sh $JBOSS_HOME/bin/run.sh -c port-3 -Djboss.service.binding.set=ports-03
-Djboss.messaging.ServerPeerID=2 -Dsession.serialization.jboss=false
+
=======================================
---
/trunk/servers/sip-servlets/sip-servlets-jboss5/src/main/java/org/jboss/web/tomcat/service/session/ClusteredSipApplicationSession.java
Thu Dec 9 08:01:47 2010
+++
/trunk/servers/sip-servlets/sip-servlets-jboss5/src/main/java/org/jboss/web/tomcat/service/session/ClusteredSipApplicationSession.java
Thu Dec 9 08:58:48 2010
@@ -1448,11 +1448,13 @@
public void rescheduleTimersLocally() {
((ClusteredSipApplicationSessionTimerService)sipContext.getSipApplicationSessionTimerService()).rescheduleTimerLocally(this);
- if(logger.isInfoEnabled()) {
- logger.info("SipApplicationSession " + key + " number of servletTimers
to reschedule locally " + servletTimers.size());
- }
- for(String key : servletTimers.keySet()) {
-
((ClusteredSipServletTimerService)sipContext.getTimerService()).rescheduleTimerLocally(this,
key);
+ if(servletTimers != null) {
+ if(logger.isInfoEnabled()) {
+ logger.info("SipApplicationSession " + key + " number of servletTimers
to reschedule locally " + servletTimers.size());
+ }
+ for(String key : servletTimers.keySet()) {
+
((ClusteredSipServletTimerService)sipContext.getTimerService()).rescheduleTimerLocally(this,
key);
+ }
}
}
}
=======================================
---
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/prepare-jboss-5-server-for-clustering-failover.sh
Mon Dec 6 10:10:16 2010
+++
/trunk/servers/sip-servlets/sip-servlets-test-suite/sipp-scenarios/clustering/prepare-jboss-5-server-for-clustering-failover.sh
Thu Dec 9 08:58:48 2010
@@ -8,7 +8,7 @@
rm -rf $JBOSS_HOME/server/port-1
rm -rf $JBOSS_HOME/server/port-2
-#rm -rf $JBOSS_HOME/server/port-3
+rm -rf $JBOSS_HOME/server/port-3
mvn clean install -f ../../../pom.xml -P jboss-5 -Dnode=all
@@ -23,16 +23,12 @@
cp -rf $JBOSS_HOME/server/all $JBOSS_HOME/server/port-1
cp -rf $JBOSS_HOME/server/all $JBOSS_HOME/server/port-2
-#cp -rf $JBOSS_HOME/server/all $JBOSS_HOME/server/port-3
cp setup/jboss-5/server-jboss-5-failover-port-1.xml
$JBOSS_HOME/server/port-1/deploy/jbossweb.sar/server.xml
cp setup/jboss-5/server-jboss-5-failover-port-2.xml
$JBOSS_HOME/server/port-2/deploy/jbossweb.sar/server.xml
-#cp setup/jboss-5/server-jboss-5-failover-port-3.xml
$JBOSS_HOME/server/port-3/deploy/jbossweb.sar/server.xml
-
mkdir $JBOSS_HOME/server/port-1/conf/dars
mkdir $JBOSS_HOME/server/port-2/conf/dars
-#mkdir $JBOSS_HOME/server/port-3/conf/dars
if [ $# -ne 0 ]; then
case $1 in
@@ -121,6 +117,20 @@
cp setup/jboss-5/war-deployers-jboss-beans-passivation-enabled.xml
$JBOSS_HOME/server/port-1/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
cp setup/jboss-5/war-deployers-jboss-beans-passivation-enabled.xml
$JBOSS_HOME/server/port-2/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
;;
+ uas-timer-colocation)
+ echo "Distributed example used is uas timer colocation"
+ cp -rf $JBOSS_HOME/server/all $JBOSS_HOME/server/port-3
+ cp setup/jboss-5/server-jboss-5-failover-cc-sas-port-1.xml
$JBOSS_HOME/server/port-1/deploy/jbossweb.sar/server.xml
+ cp setup/jboss-5/server-jboss-5-failover-cc-sas-port-2.xml
$JBOSS_HOME/server/port-2/deploy/jbossweb.sar/server.xml
+ cp setup/jboss-5/server-jboss-5-failover-cc-sas-port-3.xml
$JBOSS_HOME/server/port-3/deploy/jbossweb.sar/server.xml
+ mvn clean install
-f ../../../sip-servlets-examples/simple-sip-servlet-distributable/pom.xml
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/target/simple-sip-servlet-distributable-*.war
$JBOSS_HOME/server/port-1/deploy
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/target/simple-sip-servlet-distributable-*.war
$JBOSS_HOME/server/port-2/deploy
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/target/simple-sip-servlet-distributable-*.war
$JBOSS_HOME/server/port-3/deploy
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/distributable-simple-dar.properties
$JBOSS_HOME/server/port-1/conf/dars/distributable-dar.properties
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/distributable-simple-dar.properties
$JBOSS_HOME/server/port-2/conf/dars/distributable-dar.properties
+
cp ../../../sip-servlets-examples/simple-sip-servlet-distributable/distributable-simple-dar.properties
$JBOSS_HOME/server/port-3/conf/dars/distributable-dar.properties
+ ;;
*)
echo "Distributed example used is uas"
mvn clean install
-f ../../../sip-servlets-examples/simple-sip-servlet-distributable/pom.xml