Thanks for confirming that. What you're trying to do is valid; it's just that it requires real caution when used in an actual cluster with production data, so it's not the default.
That technique won't work if the JBC config has "useRegionBasedMarshalling" set to true. Which in AS 5.1 is only the case for the field-granularity-session-cache, but will probably be the default everywhere in 5.2.
I bring that up because there's some hard-coded logic that detects useRegionBasedMarshalling=true and deletes the sessions off the disk at webapp undeploy. But thinking about your question has me thinking the "purgeOnStartup" flag could handle that useRegionBasedMarshalling=true use case fine as well, removing the need to have the cleanup be hard coded, and letting people like yourself control the behavior.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259965#4259965
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259965
Hey,
I've searched around but been unable to find how to do this. I currently have multiple JBoss instances on a WinServer2008 x64 machine (bound to separate IP address) I can get one to start up as a service but not more than one. I've tried editing the service.bat to start up multiples but that didn't work. It never gets to the second one. I also tried copying the service file and changing all the stuff inside to make another service but when I try to start that it starts and stops right away. What is the proper way to have multiple JBoss services. Or if this is not possible what I really want is to have these instances start up at startup and not have a bunch (like 10) open command prompt windows.
thanks!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259961#4259961
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259961
Hey,
I'm working with on an ant script that can be used to start/stop a JBoss instance on a remote machine on my local intranet. the stopping part works fine. Starting causes me issues.
Basically what I am doing is calling the a bat file that runs the run.bat (remote server is WinServ2008) with specific parameters. this file contains the fillowing:
\\[servername]\[jboss home]bin\run.bat -c [instanceName] -b [ip address to bind instance to] -Djboss.messaging.ServerPeerID=2
when it runs it acts like it's trying to start jboss on my local machine. So how do I get JBoss to start from an external machine? Starting it locally works with out problem.
Thanks for any help you can give.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259960#4259960
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259960
A tip for those who come this way after us: we found a large part of the problem was that the cluster nodes rely on being in constant communication.
If one of them is under high load (say, running some reports or something) its CPU usage may be so high it does not respond to the cluster ping quickly enough (within 3 seconds). The cluster then treats it as dead and removes it from the cluster, even though it is not dead it is just busy.
We increased the org.jgroups.protocols.pbcast.GMS timeout and it helped a great deal.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259958#4259958
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259958
OK, it sounds like this may be ok in a single server dev environment, but doesn't make much sense in an actual/production cluster. What you said makes sense. In theory not all servers are suppose to go down at the same time anyway ;). I had played with the purgeOnStartup but it seemed to lead to other inconsistencies in replication / startup, which is what you hinted at. Thanks, I'll try to use it locally, but will skip it in production.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259956#4259956
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259956
Good question. Complicated answer.
First, if you want to try to get this to work, you can disable buddy replication in your JBC config and also update the JBC config's cacheLoaderConfig section:
<property name="purgeOnStartup">false</property>
That's "true" by default.
The issue with reading sessions off the disk at startup is that the persistent-across-server-restart storage for a session is meant to be the other nodes in the cluster, not the disk. If you also start reading sessions off the disk, you run into the potential of having using out-of-date data from the disk in preference to the data transferred from the cluster. This is particularly the case with buddy replictation.
See https://jira.jboss.org/jira/browse/JBAS-5627, particularly the subtasks under it, for a more in-depth discussion.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259953#4259953
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259953