HI,
Have a look at the memory settings in the run.conf file and also monitor the Garbage collections. This will give you some starting point as to what needs to be tuned.
Search the forum for Performance tunning or heap settings and you will find some tips on how to tune the server properly.
I am currently also in a process of tunning a Jboss server running in a clustered mode with 24G RAM.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235868#4235868
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235868
Im not sure whether the signalling of tasks ie task.signal has the save behaviour as the direct signalling on the token object. Also, is the token object uniquely identified by something other than its name? ie its path parent/child? I am trying to work out thru junits what the constraints are, but it doesnt seem to be limited to fully nested f/j's.
It is all rather bizarre. Since, I have managed to see that all child tokens of a parent token are at the join, yet the parent is still at the fork. I didnt think that this should happed.
Finally, I have seen instances where the child tokens go past the join, yet the parent token is still at the fork...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235854#4235854
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235854