[Clustering/JBoss] - Re: JBoss Cluster on Multihomed zone
by rajeshchande
I have specified the bind_addr to 3.183.158 and the cluster works fine (Instances form a cluster while startup).
I have followed the http://docs.hp.com/en/5991-5569/ar01s07.html and made session replication successfully worked in scenario 1.
The session replication FAILS to work in scenario 2, What specific changes in tc5-cluster-service.xml required? and why so? Why difference in scenario 1 and 2?
In scenario 2:
When accessing the counter application:
instance 1 log is:
##############
2007/11/12 04:24:37 | 04:24:37,268 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)] Started in 1m:5s:486ms
| 2007/11/12 05:22:17 | 05:22:17,583 INFO [TreeCache] viewAccepted(): new members: [int-app-devlc1-01:60788, int-app-devlc1-02:61593]
| 2007/11/12 06:00:54 | 06:00:54,828 INFO [FarmMemberService] farmDeployment(), deploy locally: farm/counter.war
| 2007/11/12 06:00:55 | 06:00:55,802 INFO [TomcatDeployer] deploy, ctxPath=/counter, warUrl=.../tmp/deploy/tmp698counter.war/
| 2007/11/12 06:00:56 | 06:00:56,360 INFO [JBossCacheManager] init(): replicationGranularity_ is 1 and invaldateSessionPolicy is 2
| 2007/11/12 06:00:56 | 06:00:56,481 INFO [JBossCacheManager] Starting JBossManager
| 2007/11/12 06:00:56 | 06:00:56,493 INFO [JBossCacheManager] We are using mod_jk(2) for load-balancing. Will add JvmRouteValve.
| 2007/11/12 06:02:52 | 06:02:52,146 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker2, refresh count:1
| 2007/11/12 06:03:01 | 06:03:01,552 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker2, refresh count:2
| 2007/11/12 06:03:03 | 06:03:03,249 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker2, refresh count:3
| 2007/11/12 06:03:04 | 06:03:04,308 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker2, refresh count:4
| 2007/11/12 06:03:33 | TERM trapped. Shutting down.
| 2007/11/12 06:03:34 | 06:03:34,487 INFO [Server] Runtime shutdown hook called, forceHalt: true
##############
After shutting instance 1 down, instance 2 has the following on aacceing the counter application:
##############
2007/11/12 05:41:36 | 05:41:36,061 INFO [TreeCache] viewAccepted(): new members: [int-app-devlc1-01:60788]
| 2007/11/12 05:41:41 | 05:41:41,652 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker2, refresh count:1
| 2007/11/12 05:41:44 | 05:41:44,902 INFO [STDOUT] 4Gv6Zk8uMNFykr6fX1vOCw**.worker1, refresh count:2
##############
The count should BEGIN from "5"
Any suggestions why session replication is failing?
Regards,
Rajesh
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103549#4103549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103549
18 years, 8 months
[Installation, Configuration & DEPLOYMENT] - Deploying error with JBoss 4.x
by sridharkumarch
Hello,
I'm trying to configure and deploy a project with JBoss (Jboss connection with Oracle datasource)
so I get the following error.
10:55:18,032 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer
ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: CONFIGURED
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=StateManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq.destination:service=Queue,name=A
jboss.mq.destination:service=Queue,name=B
jboss.mq.destination:service=Queue,name=C
jboss.mq.destination:service=Queue,name=D
jboss.mq.destination:service=Queue,name=ex
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq:service=PersistenceManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Topic,name=testTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=testQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=A
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=B
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=C
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=D
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=ex
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=Invoker
State: CONFIGURED
I Depend On:
jboss.mq:service=TracingInterceptor
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=UIL2
ObjectName: jboss.mq:service=TracingInterceptor
State: CONFIGURED
I Depend On:
jboss.mq:service=SecurityManager
Depends On Me:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=SecurityManager
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq.destination:service=Queue,name=DLQ
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq:service=InvocationLayer,type=JVM
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
Can any one help me...
Regards
Sridhar Kumar Chinchili
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103545#4103545
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103545
18 years, 8 months