[JBoss-user] [Clustering/JBoss] - Re: Load balancing and Failover
Gunjan - did you ever resolve this? I am seeing something similar happening w/ 4.0.2. At least in my case, jvmRoute is not being set ( I think on the Tomcat side ). I have 3.2.2 servers defined in my LB as well, and everything works perfect when I map to those. As soon as I map back to 4.0.2 servers, no workie. Without the jvmRoute being passed, the browser - LB cannot determine proper node to send the request to, so it goes to the 'next' node, (in my case) causing a second login page. Look in the returned HTTP headers and see if the jvmRoute is being returned. Also, I don't see the domain attribute being set in your workers.properties, which sets the jvmRoute name that is associated with a LB node. I saw a reference in 4.0.3 RC release notes about a fix in the jvmRoute stuff, so am going to try 4.0.3RC2. Mike View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3898489#3898489 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3898489 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Load balancing and Failover
Hi, I think this problem is due to JAAS related configurations on node 2 because this problem occurs when the request goes on node2 then the login page is displayed correctly but when i login the request goes to node 1. My login-config.xml on node 2 is ?xml version='1.0'? !DOCTYPE policy PUBLIC -//JBoss//DTD JBOSS Security Config 3.0//EN http://www.jboss.org/j2ee/dtd/security_config.dtd; !-- The XML based JAAS login configuration read by the org.jboss.security.auth.login.XMLLoginConfig mbean. Add an application-policy element for each security domain. The outline of the application-policy is: application-policy name=security-domain-name login-module code=login.module1.class.name flag=control_flag module-option name = option1-nameoption1-value/module-option module-option name = option2-nameoption2-value/module-option ... /login-module login-module code=login.module2.class.name flag=control_flag ... /login-module ... /application-policy $Revision: 1.12.2.2 $ -- !-- Used by clients within the application server VM such as mbeans and servlets that access EJBs. -- application-policy name = client-login login-module code = org.jboss.security.ClientLoginModule flag = required /login-module /application-policy !-- Security domain for JBossMQ -- application-policy name = jbossmq login-module code = org.jboss.security.auth.spi.DatabaseServerLoginModule flag = required module-option name = unauthenticatedIdentityguest/module-option module-option name = dsJndiNamejava:/DefaultDS/module-option module-option name = principalsQuerySELECT PASSWD FROM JMS_USERS WHERE USERID=?/module-option module-option name = rolesQuerySELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?/module-option /login-module /application-policy !-- Security domain for JBossMQ when using file-state-service.xml application-policy name = jbossmq login-module code = org.jboss.mq.sm.file.DynamicLoginModule flag = required module-option name = unauthenticatedIdentityguest/module-option module-option name = sm.objectnamejboss.mq:service=StateManager/module-option /login-module /application-policy -- !-- Security domains for testing new jca framework -- application-policy name = HsqlDbRealm login-module code = org.jboss.resource.security.ConfiguredIdentityLoginModule flag = required module-option name = principalsa/module-option module-option name = userNamesa/module-option module-option name = password/module-option module-option name = managedConnectionFactoryNamejboss.jca:service=LocalTxCM,name=DefaultDS/module-option /login-module /application-policy application-policy name = JmsXARealm login-module code = org.jboss.resource.security.ConfiguredIdentityLoginModule flag = required module-option name = principalguest/module-option module-option name = userNameguest/module-option module-option name = passwordguest/module-option module-option name = managedConnectionFactoryNamejboss.jca:service=TxCM,name=JmsXA/module-option /login-module /application-policy !-- A template configuration for the jmx-console web application. This defaults to the UsersRolesLoginModule the same as other and should be changed to a stronger authentication mechanism as required. -- application-policy name = jmx-console login-module code=org.jboss.security.auth.spi.UsersRolesLoginModule flag = required module-option name=usersPropertiesprops/jmx-console-users.properties/module-option module-option name=rolesPropertiesprops/jmx-console-roles.properties/module-option /login-module /application-policy !-- A template configuration for the web-console web application. This defaults to the UsersRolesLoginModule the same as other and should be changed to a stronger authentication mechanism as required. -- application-policy name = web-console login-module code=org.jboss.security.auth.spi.UsersRolesLoginModule flag = required module-option name=usersPropertiesweb-console-users.properties/module-option module-option name=rolesPropertiesweb-console-roles.properties/module-option /login-module /application-policy !-- A template configuration for the JBossWS web application (and transport layer!). This defaults to the UsersRolesLoginModule the same as other and should be changed to a stronger
[JBoss-user] [Clustering/JBoss] - Re: Load balancing and Failover
Please post you tc5-cluster-service.xml file. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3892085#3892085 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892085 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: Load balancing and Failover
Hi David, Thanks for your reply. My tc5-cluster-service.xml is ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- Customized TreeCache Service Configuration for Tomcat 5 Clustering -- !-- -- !-- = -- !-- -- !-- Defines TreeCache configuration -- !-- -- jboss:service=Naming jboss:service=TransactionManager !-- Configure the TransactionManager -- org.jboss.cache.JBossTransactionManagerLookup !-- Isolation level : SERIALIZABLE REPEATABLE_READ (default) READ_COMMITTED READ_UNCOMMITTED NONE -- REPEATABLE_READ !-- Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC -- REPL_ASYNC !-- Name of cluster. Needs to be the same for all clusters, in order to find each other -- Tomcat-Cluster !-- JGroups protocol stack properties. Can also be a URL, e.g. file:/home/bela/default.xml -- !-- The default UDP stack: - If you have a multihomed machine, set the UDP protocol's bind_addr attribute to the appropriate NIC IP address, e.g bind_addr=192.168.0.2. - On Windows machines, because of the media sense feature being broken with multicast (even after disabling media sense) set the UDP protocol's loopback attribute to true -- UDP mcast_addr=230.1.2.7 mcast_port=45577 ip_ttl=8 ip_mcast=true mcast_send_buf_size=15 mcast_recv_buf_size=8 ucast_send_buf_size=15 ucast_recv_buf_size=8 loopback=true bind_addr=10.1.1.131/ PING timeout=2000 num_initial_members=3 up_thread=false down_thread=false/ MERGE2 min_interval=1 max_interval=2/ FD_SOCK/ VERIFY_SUSPECT timeout=1500 up_thread=false down_thread=false/ pbcast.NAKACK gc_lag=50 retransmit_timeout=600,1200,2400,4800 max_xmit_size=8192 up_thread=false down_thread=false/ UNICAST timeout=600,1200,2400 window_size=100 min_threshold=10 down_thread=false/ pbcast.STABLE desired_avg_gossip=2 up_thread=false down_thread=false/ FRAG frag_size=8192 down_thread=false up_thread=false/ pbcast.GMS join_timeout=5000 join_retry_timeout=2000 shun=true print_local_addr=true/ pbcast.STATE_TRANSFER up_thread=true down_thread=true/ !-- Alternate TCP stack: customize it for your environment, change bind_addr and initial_hosts -- !-- TCP bind_addr=thishost start_port=7810 loopback=true/ TCPPING initial_hosts=thishost[7810],otherhost[7810] port_range=3 timeout=3500 num_initial_members=3 up_thread=true down_thread=true/ MERGE2 min_interval=5000 max_interval=1/ FD shun=true timeout=2500 max_tries=5 up_thread=true down_thread=true / VERIFY_SUSPECT timeout=1500 down_thread=false up_thread=false / pbcast.NAKACK down_thread=true up_thread=true gc_lag=100 retransmit_timeout=3000/ pbcast.STABLE desired_avg_gossip=2 down_thread=false up_thread=false / pbcast.GMS join_timeout=5000 join_retry_timeout=2000 shun=false print_local_addr=true down_thread=true up_thread=true/ pbcast.STATE_TRANSFER up_thread=true down_thread=true/ -- !-- Max number of milliseconds to wait for a lock acquisition -- 15000 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3892087#3892087 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892087 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf
