[JBossCache] - Help need in delplying JBoss Cache as a distributed cache
by dsualeh
Hi guys.
I am having troubling in deploying JBoss as a distributed cache.
Can someone please have a look at my property configuration
Your help will be very much appreciated
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- Sample TreeCache Service Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ==================================================================== -->
<!-- Defines TreeCache configuration -->
<!-- ==================================================================== -->
jboss:service=Naming
jboss:service=TransactionManager
<!--
Configure the TransactionManager
-->
<!--
org.jboss.cache.DummyTransactionManagerLookup
-->
<!--
Isolation level : SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
-->
NONE
<!--
Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC
-->
REPL_ASYNC
<!--
Just used for async repl: use a replication queue
-->
false
<!--
Replication interval for replication queue (in ms)
-->
0
<!--
Max number of elements which trigger replication
-->
0
<!-- Name of cluster. Needs to be the same for all clusters, in order
to find each other
-->
GlueCache-GD
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
-->
<!-- UDP: if you have a multihomed machine,
set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
-->
<!-- UDP: On Windows machines, because of the media sense feature
being broken with multicast (even after disabling media sense)
set the loopback attribute to true -->
<UDP mcast_addr="228.1.2.3" mcast_port="48866"
ip_ttl="64" ip_mcast="true"
mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
loopback="true"/>
<PING timeout="2000" num_initial_members="3"
up_thread="false" down_thread="false"/>
<MERGE2 min_interval="10000" max_interval="20000"/>
<!-- <FD shun="true" up_thread="true" down_thread="true" />-->
<FD_SOCK/>
<VERIFY_SUSPECT timeout="1500"
up_thread="false" down_thread="false"/>
<pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
max_xmit_size="8192" up_thread="false" down_thread="false"/>
<UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
down_thread="false"/>
<pbcast.STABLE desired_avg_gossip="20000"
up_thread="false" down_thread="false"/>
<FRAG frag_size="8192"
down_thread="false" up_thread="false"/>
<pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
shun="true" print_local_addr="true"/>
<pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
<!--
Whether or not to fetch state on joining a cluster
-->
false
<!--
The max amount of time (in milliseconds) we wait until the
initial state (ie. the contents of the cache) are retrieved from
existing members in a clustered environment
-->
120000
<!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
-->
10000
<!-- Max number of milliseconds to wait for a lock acquisition -->
25000
<!-- Name of the eviction policy class. -->
org.jboss.cache.eviction.LRUPolicy
600
10000
0
<!-- Uncomment to get a graphical view of the TreeCache MBean above -->
<!-- -->
<!-- jboss.cache:service=TreeCache-->
<!-- jboss.cache:service=TreeCache-->
<!-- -->
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038813#4038813
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038813
19 years
[JBoss Messaging] - Re: Failover scenario is not working
by sabdulkareem
Thanks a lot!
I have replaced the jboss-remoting related jars to the version2.2.0 in my application. Now the Sender application able to get Connection on Node1, if the Node0 fails. But the Receiver application throws the exception like:
anonymous wrote : 2007-04-19 15:20:44,861 [main] WARN - Application re-initialization attempted
| Got Message: [File1 - Message1File1 - Message2File1 - Message3File1 - Message4]
| 2007-04-19 15:21:12,059 [Timer-1] WARN -
| org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@1342a67: detected
| failure on control connection Thread[control: Socket[addr=ddp4344.cptdomain.com/192.168.51.48,port=3197,
| localport=2112],5,]: requesting new control connection
| 2007-04-19 15:22:03,914 [Thread-8] WARN - Client attempted failover,
| but no failover attempt has been detected on the server side.
| We will now try again on the original server in case there was a
| temporary glitch on the client--server network
| 2007-04-19 15:22:15,900 [Thread-8] ERROR - Unable to retrieve address/port of secondary server socket
| org.jboss.remoting.CannotConnectException: Can not get connection to server.
| Problem establishing socket connection for InvokerLocator
| [bisocket://192.168.51.48:4457/?NumberOfCallRetries=2&clientMaxPoolSize=50&clientSocketClass=
| org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=
| org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=1&serializationtype=
| jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
|
What could be the reason?
Please Suggest me.
Thanks & Regards,
Abdul Kareem
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038810#4038810
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038810
19 years
[Installation, Configuration & Deployment] - Service MBean dependencies
by gsferra＠imnet.it
Hello,
I've a standard JBoss Service MBean that depends on two EJB 3.0, an entity (accessed by a stateless facade bean) and a message driven (that create and bind a JMS queue).
The Service MBean implementation
| import org.jboss.system.ServiceMBean;
|
| public interface MyServiceMBean extends ServiceMBean {
| }
|
| import org.jboss.system.ServiceMBeanSupport;
|
| public class MyService extends ServiceMBeanSupport implements MyServiceMBean {
| ...
| }
|
jboss-service.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server PUBLIC "-//JBoss//DTD MBean Service 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd">
| <server>
| <mbean code="MyService" name="test:service=MyService">
| <depends>jboss.j2ee:service=EJB3,name=MyEntityFacadeBean</depends>
| <depends>jboss.j2ee:service=EJB3,name=MyMessageDrivenBean</depends>
| </mbean>
| </server>
|
When I start up JBoss AS I got these messages:
...
11:36:58,286 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=test.ear,jar=test-bl.jar,name=MyMessageDrivenBean,service=EJB3 with dependencies:
11:36:58,286 INFO [JmxKernelAbstraction] persistence.units:ear=test.ear,jar=test-bl.jar,unitName=testpu
11:36:58,457 INFO [EJBContainer] STARTED EJB: MyMessageDrivenBean ejbName: MyMessageDrivenBean
11:36:58,457 WARN [MessagingContainer] Could not find the queue destination-jndi-name=queue/test
11:36:58,457 WARN [MessagingContainer] destination not found: queue/test reason: javax.naming.NameNotFoundException: test not bound
11:36:58,473 WARN [MessagingContainer] creating a new temporary destination: queue/test
11:36:58,488 INFO [test] Bound to JNDI name: queue/test
...
11:36:58,769 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=test.ear,jar=test-bl.jar,name=MyEntityFacadeBean,service=EJB3 with dependencies
11:36:58,769 INFO [JmxKernelAbstraction] persistence.units:ear=test.ear,jar=test-bl.jar,unitName=testpu
11:36:58,832 INFO [EJBContainer] STARTED EJB: MyEntityFacadeBean ejbName: MyEntityFacadeBean
...
--- MBeans waiting for other MBeans ---
ObjectName: test:service=MyService
State: CONFIGURED
I Depend On:
jboss.j2ee:service=EJB3,name=MyEntityFacadeBean
jboss.j2ee:service=EJB3,name=MyMessageDrivenBean
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:service=EJB3,name=MyEntityFacadeBean
State: NOTYETINSTALLED
Depends On Me:
test:service=MyService
Looking at the JMX console everything seems to be ok, the service is registered (but it doesn't work), the EJB 3.0 its working and bounded and the message driven bean JMS queue is bounded. What I missing?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038806#4038806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038806
19 years