[jboss-user] [Clustering/JBoss] - Re: Rollout deployment on a cluster

2007-11-06 Thread canty28
Well i have been doing that way only. Deleting the war from the farm folder and 
dropping the new war. But that would still make the app unavilable for sometime 
( atleast a few mins ). The application owners want the app to be available 
24/7. They do not want any distruption as they are users connected from all 
over the world. This is what concerns me ..how can we deploy the app without 
disrupting ? 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102267#4102267

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4102267
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Rollout deployment on a cluster

2007-11-05 Thread canty28
Hi All,

Here is my situation. we have a cluster of 6 JVM's with 3 on each node. we are 
currently using farm deployment whenever we do an deployment. Till date 
whenever we do an deployment we delete the war files first and then stop the 
server. Copy the new war file onto one JVM and then start the JVM's one after 
another. Now the app team wants no interruption to the app when an update goes 
on. Can someone give any suggestions ? 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101982#4101982

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101982
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Re: change default partition name

2007-07-26 Thread canty28
We are using JBOSS 4.0.3SP1 . Is there a way of changing the default partition 
name.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067954#4067954

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4067954
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Re: JBoss instances don't find each other

2007-07-13 Thread canty28
Elko,

I have found couple of things in the cluster. JBOSS by default it uses UDP 
protocol for clustering and UDP protocol has a restriction on send and receive. 
I initially had problems because the war file which i use is around 100MB and i 
had problems sending it over to the other clusters. I used TCP protocol and it 
was click..boom ...way too fast. As part of clustering, I did 2 things modified 
the following 2 files

1. tc5-cluster-service.xml
2. cluster-service.xml

I commented out the UDP protocol and uncommented the TCP protocol information, 
gave the ip's of the boxes which i needed in the cluster and started them back 
and each node was able to recognize the other. 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064037#4064037

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4064037
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Re: Horizontal Clustering not working _ need help

2007-04-17 Thread canty28
Here is my tc5-Cluster.xml 


!--
The default UDP stack:
- If you have a multihomed machine, set the UDP protocol's 
bind_addr attribute to the
appropriate NIC IP address, e.g bind_addr=192.168.0.2.
- On Windows machines, because of the media sense feature being 
broken with multicast
(even after disabling media sense) set the UDP protocol's loopback 
attribute to true
--

UDP mcast_addr=${jboss.partition.udpGroup:230.1.2.7} 
mcast_port=45577
ip_ttl=8 ip_mcast=true
mcast_send_buf_size=15 mcast_recv_buf_size=8
ucast_send_buf_size=15 ucast_recv_buf_size=8
loopback=false /
PING timeout=2000 num_initial_members=3
up_thread=false down_thread=false/
MERGE2 min_interval=1 max_interval=2/
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=2
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/




View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4037950#4037950

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037950
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Re: Horizontal Clustering not working _ need help

2007-04-17 Thread canty28
Here is the error i receive when i actually put the binding address in the 
cluster-service.xml file

09:18:17,523 ERROR [JChannel] exception: java.lang.Exception: exception caused 
by UDP.start(): java.lang.Exception: UDP.createSockets(): cannot list on any 
port in range 0-1
  | 09:18:17,528 WARN  [ServiceController] Problem starting service 
jboss:service=DefaultPartition
  | ChannelException: java.lang.Exception: exception caused by UDP.start(): 
java.lang.Exception: UDP.createSockets(): cannot list on any port in range 0-1
  | at org.jgroups.JChannel.connect(JChannel.java:328)
  | at 
org.jboss.ha.framework.server.ClusterPartition.startService(ClusterPartition.java:298)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
  | at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
  | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
  | at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
  | at 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
  | at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)
  | at $Proxy0.start(Unknown Source)
  | at 
org.jboss.system.ServiceController.start(ServiceController.java:428)
  | at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
  | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
  | at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
  | at 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
  | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
  | at $Proxy4.start(Unknown Source)
  | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
  | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
  | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
  | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
  | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
  | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  | at 
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
  | at 
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
  | at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
  | at 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
  | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
  | at $Proxy10.deploy(Unknown Source)
  | at 
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
  | at 
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
  | at 
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
  | at 
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
  | at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | 

[jboss-user] [Clustering/JBoss] - Re: Horizontal Clustering not working _ need help

2007-04-17 Thread canty28
Please also find my cluster-service.xml


UDP mcast_addr=${jboss.partition.udpGroup:228.1.2.3} 
mcast_port=45566
   ip_ttl=8 ip_mcast=true
   mcast_send_buf_size=8 mcast_recv_buf_size=15000
   ucast_send_buf_size=8 ucast_recv_buf_size=15000
   loopback=false bind_addr=${jboss.bind.address} /
PING timeout=2000 num_initial_members=3
   up_thread=true down_thread=true/
MERGE2 min_interval=1 max_interval=2/
FD shun=true up_thread=true down_thread=true
   timeout=2500 max_tries=5/
VERIFY_SUSPECT timeout=3000 num_msgs=3
   up_thread=true down_thread=true/
pbcast.NAKACK gc_lag=50 
retransmit_timeout=300,600,1200,2400,4800
   max_xmit_size=8192
   up_thread=true down_thread=true/
UNICAST timeout=300,600,1200,2400,4800 window_size=100 
min_threshold=10
   down_thread=true/
pbcast.STABLE desired_avg_gossip=2
   up_thread=true down_thread=true/
FRAG frag_size=8192
   down_thread=true up_thread=true/
pbcast.GMS join_timeout=5000 join_retry_timeout=2000
   shun=true print_local_addr=true/
pbcast.STATE_TRANSFER up_thread=true down_thread=true/
 


The reason why we had to increase the mcast and ucast buffer sizes was mainly 
because the war file which we were deploying is around 107 M.  Please help me 
in this matter. I have been following the forums. I have also tried adding 
route and also adding bind address to the cluster-service.xml but that 
eventually throws an error.We are running JBOSS 4.0.3SP1 on SLES9. Any help in 
this matter or previous experiences would be helpful.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4037951#4037951

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037951
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Clustering/JBoss] - Horizontal Clustering not working _ need help

2007-04-16 Thread canty28
Hi Everyone,

I am currently running JBOSS 4.0.3 SP1. Currently i am configuring UAT 
environment. I am trying to acheive horizontal clustering. Box A has 3 jvm's 
-bduat_server1, bduat_server2,bduat_server3. Box B has 3 JVM's - 
bduat2_server1,bduat2_server2,bduat2_server3. Currently vertical clustering 
works fine. When i start up all instances on Box A, all the instances pick up 
the ear file from the farm. But when box B is started it is being recognized 
but the ear file doesnt get pushed on from Box A to Box B. 

I am currently pasting the logs of Box B . 

=

  JBoss Bootstrap Environment

  JBOSS_HOME: /servers/jboss

  JAVA: /usr/java/j2sdk1.4.2_11/bin/java

  JAVA_OPTS: -Djava.net.preferIPv4Stack=true -server -Xms512m -Xmx768m 
-Dprogram.name=run.sh

  CLASSPATH: /servers/jboss/bin/run.jar:/usr/java/j2sdk1.4.2_11/lib/tools.jar

=

17:50:20,127 INFO  [Server] Starting JBoss (MX MicroKernel)...
17:50:20,129 INFO  [Server] Release ID: JBoss [Zion] 4.0.3SP1 (build: 
CVSTag=JBoss_4_0_3_SP1 date=200510231054)
17:50:20,130 INFO  [Server] Home Dir: /servers/jboss
17:50:20,131 INFO  [Server] Home URL: file:/servers/jboss/
17:50:20,131 INFO  [Server] Patch URL: null
17:50:20,132 INFO  [Server] Server Name: bdgkmuat2_server1
17:50:20,132 INFO  [Server] Server Home Dir: 
/servers/jboss/server/bdgkmuat2_server1
17:50:20,133 INFO  [Server] Server Home URL: 
file:/servers/jboss/server/bdgkmuat2_server1/
17:50:20,133 INFO  [Server] Server Temp Dir: 
/servers/jboss/server/bdgkmuat2_server1/tmp
17:50:20,133 INFO  [Server] Root Deployment Filename: jboss-service.xml
17:50:20,615 INFO  [ServerInfo] Java version: 1.4.2_11,Sun Microsystems Inc.
17:50:20,616 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 
1.4.2_11-b06,Sun Microsystems Inc.
17:50:20,616 INFO  [ServerInfo] OS-System: Linux 2.6.5-7.282-smp,i386
17:50:21,224 INFO  [Server] Core system initialized
17:50:23,976 INFO  [ServiceBindingManager] Initializing store
17:50:23,976 INFO  [ServiceBindingManager] Using StoreURL: 
file:/servers/jboss/docs/examples/binding-manager/sample-bindings.xml
17:50:24,711 INFO  [WebService] Using RMI server codebase: 
http://ss1kmbat02.usa.wachovia.net:8183/
17:50:24,792 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: 
resource:log4j.xml
17:50:25,223 INFO  [NamingService] Started jndi bootstrap jnpPort=1199, 
rmiPort=1198, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, 
Server [EMAIL PROTECTED]
17:50:31,077 INFO  [SnmpAgentService] SNMP agent going active
17:50:32,055 INFO  [DefaultPartition] Initializing
17:50:32,120 INFO  [STDOUT]
---
GMS: address is 0.0.0.0:32969 (additional data: 17 bytes)
---
17:50:34,168 INFO  [DefaultPartition] Number of cluster members: 1
17:50:34,168 INFO  [DefaultPartition] Other members: 0
17:50:34,171 INFO  [DefaultPartition] Fetching state (will wait for 3 
milliseconds):
17:50:34,178 INFO  [DefaultPartition] New cluster view for partition 
DefaultPartition (id: 0, delta: 0) : [170.13.57.43:1199]
17:50:34,187 INFO  [DefaultPartition] I am (170.13.57.43:1199) received 
membershipChanged event:
17:50:34,187 INFO  [DefaultPartition] Dead members: 0 ([])
17:50:34,188 INFO  [DefaultPartition] New Members : 0 ([])
17:50:34,188 INFO  [DefaultPartition] All Members : 1 ([170.13.57.43:1199])
17:50:34,260 INFO  [HANamingService] Started ha-jndi bootstrap jnpPort=1200, 
backlog=50, bindAddress=/0.0.0.0
17:50:34,279 INFO  [DetachedHANamingService$AutomaticDiscovery] Listening on 
/0.0.0.0:1102, group=230.0.0.4, HA-JNDI address=170.13.57.43:1200
17:50:35,715 INFO  [orb] ORB run
17:50:35,849 INFO  [CorbaNamingService] Naming: 
[IOR:002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3200D80001020D3137302E31332E35372E34330E2C00114A426F73732F4E616D696E672F726F6F740500084A414301001C00010001000105010001000101090001050100010021005100240020007E0001000D3137302E31332E35372E34330DC90024001F00040003000100220024001F00040003]
17:50:35,994 INFO  [CorbaTransactionService] TransactionFactory: