[Clustering/JBoss] - Re: How to make field-granularity-session-cache the default
by bstansberry@jboss.com
The default clustering behavior in AS 5 can be controlled via the server/XXX/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml file.
| <bean name="WebAppClusteringDefaultsDeployer"
| class="org.jboss.web.tomcat.service.deployers.ClusteringDefaultsDeployer">
|
| <!-- Default session cache config used by distributable webapps -->
| <property name="cacheName">standard-session-cache</property>
| <!-- Default session cache config used by FIELD granularity distributable webapps -->
| <property name="fieldGranularityCacheName">field-granularity-session-cache</property>
|
| ....
|
| <property name="replicationGranularity">SESSION</property>
|
| ....
|
| </bean>
|
Change replicationGranularity to FIELD and you'll get FIELD by default, unless you configure something else in the app's jboss-web.xml.
If you want field-granularity-session-cache to be used by default even if you use SESSION or ATTRIBUTE granularity, change the value of the "cacheName" property. Although I'd recommend adding your own cache config or tweaking standard-session-cache to match what you want. Solely because using a config named "field-granularity-..." for non-field-granularity will confuse someone some day. :)
I haven't revamped the FIELD granularity section of the guide yet. :(
The AS now uses the standard POJO Cache annotation instead of @AopMarker. It is @org.jboss.cache.pojo.annotation.Replicable.
Re: using aopc, you can also use load time weaving. See http://www.jboss.org/jbossaop/docs/2.0.0.GA/docs/aspect-framework/referen... for some discussion of weaving options. There are a couple details in there that are a bit off from AS 5.1 but it's useful.
Here's a quick summary of what I did to get load-time weaving for a FIELD granularity web app:
1) Edit server/all/conf/bootstrap/aop.xml's AspectManager bean:
| <property name="enableLoadtimeWeaving">true</property>
| <property name="include">com.bar., com.bar.</property>
| <property name="exclude">org.</property>
The first is self-evident. :) The second is where you list the packages you for sure want AOP to look at for load-time weaving. The third is packages for sure *not* to look at. By default that was "org.jboss." but when I experimented I got complaints about some stuff in org.richfaces in the admin-console.war, so I changed it to just "org."
2) Copy the pluggable-instrumentor.jar to the bin/ dir from server/all/deployers/jboss-aop-jboss5.deployer
3) Edit run.conf and add
JAVA_OPTS="$JAVA_OPTS -javaagent:pluggable-instrumentor.jar"
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237765#4237765
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237765
17 years, 1 month
[Installation, Configuration & DEPLOYMENT] - JBoss Node takes too much time in startup
by akshay_johari
Hi All,
I have just installed JBoss 4.2.2 GA with jdk 1.6.0. I have put the EAR in deploy/ directory at the newly created node and start the node. It starts in maximum 3 mins. but as I mount the content from NAS and restart the node, it took too much time and up in 45 mins. I don't know the reason of it. Can you please help. I see in nohup that Jboss is waiting for something at the following point :
19:36:00,096 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
19:36:00,998 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
19:36:00,998 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
19:36:01,340 INFO [TransactionManagerService] Starting recovery manager
19:36:01,773 INFO [TransactionManagerService] Recovery manager started
19:36:01,773 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
Please suggest what should I do to resolve this problem. Sorry for my bad English
Thanks in advance
Regards,
Akshay
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237762#4237762
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237762
17 years, 1 month
[Tomcat, HTTPD, Servlets & JSP] - SSO session destroyed using a4j:poll
by pablo.fraga1975
Hi,
I am using JBoss 4.2.0, all conf, ClusterdSSOValve with cookiedomain, ajax4jsf, richfaces 3.3.0 GA and a4j:poll component in some jsp pages, the whole thing in a production environment that receives more than 400.000 tx per day.
We are experiencing an unexpected behaviour, where we login properly, hit some pages in one of the web apps. then go to another web app. where we have rich graphics in a jsp using a4j:poll component. This page works fine even for hours, refreshing data correctly, our session timeout is 30 minutes (default value), in each request fired by the a4j:poll component the session is accessed, but, after some hours (not always the same time) the whole sessions are destroyed and we can see it because we have implemented HttpSessionListener in each web app and the page freezes.
Don't know what is happening and this doesn't happens in our test environment, the difference we could see is the sustained overload.
Any more information that you need, just ask me about it.
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237754#4237754
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237754
17 years, 1 month