Are you saying that you want to save changes made to mbeans via Web Console? If so, that is not possible. If you want the change to be permanent, you must modify the original xml configuration file.
If what you want to do is have several possible 'states' for an mbean and switch from one to another, one way is to set up scripts using twiddle to make the changes, and then run the appropriate script(s).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001833#4001833
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001833
Here's an example:
------------
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
<Proxy balancer://myCluster>
Order deny,allow
Allow from all
#jboss cluster members
BalancerMember ajp://192.168.1.98:8009/myWebApp keepalive=On
#ImmPort application
ProxyPass /myWebApp balancer://myCluster stickysession=jsessionid lbmethod=bytraffic nofailover=Off
ProxyPassReverse /myWebApp balancer://myCluster
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001832#4001832
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001832
HI -
I'm not sure if this is totally related to your problem, but I have similar issues. If there's a firewall in between your apache and application server, then the solution that worked for me was keepalive On.
The default Linux keepalive settings will need to be modified to match those of the allowable idle connection time out on the firewall.
LINUX DEFAULTS:
# cat /proc/sys/net/ipv4/tcp_keepalive_time
7200
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
75
# cat /proc/sys/net/ipv4/tcp_keepalive_probes
9
Apache settings:
ProxyPass .... keepalive=On
For additional info, see http://libkeepalive.sourceforge.net/docs/TCP-Keepalive-HOWTO
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001829#4001829
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001829
Hi,
I've got an action in one node of my process that if it fails I want it to halt the jBPM execution.
What I did was create a new custom exception and throw it. As it is said in the jBPM documentation (9.7. Exception handling) if there are uncaught exceptions they will be thrown to the client that is calling the signal() method. However my exception in the client is always null, although he realizes that an exception happens.
I've already tried to not even use a custom exception, and just let the default be thrown but the same happens.
Did I missunderstood the documentation or could it be some problem?
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001827#4001827
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001827
A small correction for other users ....
'Test' page is defined/deleted from
jboss-portal.sar/portal-samples.war/WEB-INF/default-object.xml.
'News' page is defined/deleted at jboss-portal.sar/conf/data/default-object.xml.
'My Page' I couldn't find anywhere.
Yes you are right. I remember I installed the test portlets found in portletswap.com for tutorials. It could be one of them...hmmm...
Could any xml files have been installed in JBOSS_AS itself ?... as I remember deleting/re-creating the whole default/deploy/jboss-portal.sar
Does JBOSS_AS keep some portal related configs upon restart.. ?
I will check again later today and update the post.
10x
SJX
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001825#4001825
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001825