Thanks for replying.
Yeah everything is fine.I am not using any form authentication.
Actually I am accessing Resource Adapter through a web application.
In the previous versions what I used to do is just changed some port settings
to make the things working.
Infact I am not getting any logs also for session replication.
Just getting the messages for
New Member
Dead member etc.
As you know I am using Apache .
When I fire the 1st request its going on any server either on all or on node2.
When I shutdown the server which is currently handling the request & start
tring to access the application it shows me session expired. Login again.
I was not doing specific for session replication for Jboss-3.2.5 also but the
application was running fine.
Let me elaborate it.
For Jboss-3.2.5
1. Copy the all folder from <JBoss_Home>\server and paste into the same
directory for 2 times.
Note: - all is the name of the folder.
Now rename them to node2 & node3.
2. Move to node2 folder -> open
<JBoss_Home>\server\node2\deploy\http-invoker.sar\META-INF\ jboss-service.xml
file.
Do the following changes into it.
Change 8080 everywhere in the file to 18080.
3. Move to <JBoss_Home>\server\node2\deploy\jbossweb-tomcat41.sar\META-INF\
jboss-service.xml
Search for
<Engine name="MainEngine" defaultHost="localhost"
Add jvmRoute=?node2? to the tag.
Similarly do it into the all folder also like
<Engine name="MainEngine" defaultHost="localhost" jvmRoute=?node1?>
Search for
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
Change the port of this from 8080 to 18080
Similarly
Again Search for
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
Change the port from 8009 to 18009.
4) move to <JBoss_Home>\server\node2\deploy\jms\oil2-service.xml
Search for ServerBindPort change from 8092 to 18092
5) move to <JBoss_Home>\server\node2\deploy\jms\oil-service.xml
Search for ServerBindPort change from 8090 to 18090
5) <JBoss_Home>\server\node2\deploy\jms\uil2-service.xml
Search for ServerBindPort change from 8093 to 18093
6) <JBoss_Home>\server\node2\deploy\cluster-service.xml
<mbean code="org.jboss.ha.jndi.HANamingService"
Port :- from 1100 to 11100
Find the loopback and set it true.
7) D:\jboss-3.2.3\server\node2\deploy\snmp-adaptor.sar\managers.xml
Change the port from 1162 to 11162
8)
D:\jboss-3.2.3\server\node2\deploy\snmp-adaptor.sar\META-INF\jboss-service.xml
Change the port from 1162 to 11162
7) <JBoss_Home>\server\node2\conf\jboss-minimal.xml
Search for
Change the port from 1099 to 11099
8) <JBoss_Home>\server\node2\conf\jboss-service.xml
Change the port from 8083 to 18083
Change the port from 1099 to 11099
Change the RmiPort from 1098 to 11098
Change the RMIObjectPort from 4444 to 14444
Change the ServerBindPort from 4445 to 14445
Can you send me the whole configuration required , from making the second
instance till the deployment. Because I have tried many scenarios
As now I have added jboss-web.xml with the following code
<jboss-web>
<replication-config>
<replication-trigger>SET_AND_GET</replication-trigger>
<replication-type>SYNC</replication-type>
<replication-granularity>ATTRIBUTE</replication-granularity>
</replication-config>
</jboss-web>
but still I am not getting the session replication.
The behaviour is same.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934584#3934584
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934584
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
