6 Replies Latest reply on Apr 2, 2009 7:39 PM by brian.stansberry

Node's joining the wrong partition

meetoblivion Mar 31, 2009 8:14 PM

So I'm trying to get a hand on this cool new technology called "clustering." ON my local machine I have 2 installs of jboss as 5.0.1 running. I can get them to work together on the same partition, but when I put them in different partitions they're still working together. I have the load balancer still pointing to both of them, are these results because of that? Here's node 2..

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /opt/jboss/jboss-5.0.1.GA-2

JAVA: java

JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true

CLASSPATH: /opt/jboss/jboss-5.0.1.GA-2/bin/run.jar

=========================================================================

20:04:40,667 INFO [ServerImpl] Starting JBoss (Microcontainer)...
20:04:40,668 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
20:04:40,668 INFO [ServerImpl] Bootstrap URL: null
20:04:40,668 INFO [ServerImpl] Home Dir: /opt/jboss/jboss-5.0.1.GA-2
20:04:40,669 INFO [ServerImpl] Home URL: file:/opt/jboss/jboss-5.0.1.GA-2/
20:04:40,669 INFO [ServerImpl] Library URL: file:/opt/jboss/jboss-5.0.1.GA-2/lib/
20:04:40,669 INFO [ServerImpl] Patch URL: null
20:04:40,669 INFO [ServerImpl] Common Base URL: file:/opt/jboss/jboss-5.0.1.GA-2/common/
20:04:40,670 INFO [ServerImpl] Common Library URL: file:/opt/jboss/jboss-5.0.1.GA-2/common/lib/
20:04:40,670 INFO [ServerImpl] Server Name: all
20:04:40,670 INFO [ServerImpl] Server Base Dir: /opt/jboss/jboss-5.0.1.GA-2/server
20:04:40,670 INFO [ServerImpl] Server Base URL: file:/opt/jboss/jboss-5.0.1.GA-2/server/
20:04:40,670 INFO [ServerImpl] Server Config URL: file:/opt/jboss/jboss-5.0.1.GA-2/server/all/conf/
20:04:40,670 INFO [ServerImpl] Server Home Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all
20:04:40,670 INFO [ServerImpl] Server Home URL: file:/opt/jboss/jboss-5.0.1.GA-2/server/all/
20:04:40,670 INFO [ServerImpl] Server Data Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/data
20:04:40,671 INFO [ServerImpl] Server Library URL: file:/opt/jboss/jboss-5.0.1.GA-2/server/all/lib/
20:04:40,671 INFO [ServerImpl] Server Log Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/log
20:04:40,671 INFO [ServerImpl] Server Native Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/tmp/native
20:04:40,671 INFO [ServerImpl] Server Temp Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/tmp
20:04:40,671 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/tmp/deploy
20:04:41,258 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss/jboss-5.0.1.GA-2/server/all/conf/bootstrap.xml
20:04:41,779 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
20:04:41,782 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
20:04:42,095 INFO [CopyMechanism] VFS temp dir: /opt/jboss/jboss-5.0.1.GA-2/server/all/tmp
20:04:42,096 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
20:04:43,407 INFO [ServerInfo] Java version: 1.6.0_0,Sun Microsystems Inc.
20:04:43,407 INFO [ServerInfo] Java Runtime: IcedTea6 1.4 (suse-24.3.1-x86_64) Runtime Environment (build 1.6.0_0-b14)
20:04:43,407 INFO [ServerInfo] Java VM: OpenJDK 64-Bit Server VM 14.0-b08,Sun Microsystems Inc.
20:04:43,408 INFO [ServerInfo] OS-System: Linux 2.6.27.19-3.2-default,amd64
20:04:43,450 INFO [JMXKernel] Legacy JMX core initialized
20:04:46,034 INFO [ProfileServiceImpl] Loading profile: all from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@b83d59c(root=/opt/jboss/jboss-5.0.1.GA-2/server, key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all])
20:04:46,036 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@b83d59c(root=/opt/jboss/jboss-5.0.1.GA-2/server, key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all])
20:04:46,036 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@763861e6{key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all]}
20:04:48,078 INFO [WebService] Using RMI server codebase: http://ja-laptop-lnx.ja:8083/
20:04:54,194 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
20:04:54,194 INFO [NativeServerConfig] 3.0.5.GA
20:05:03,402 INFO [CorbaNamingService] CORBA Naming Started
20:05:07,028 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://ja-laptop-lnx.ja/jndi/rmi://ja-laptop-lnx.ja:1090/jmxconnector
20:05:07,307 INFO [MailService] Mail Service bound to java:/Mail
20:05:08,095 INFO [SnmpAgentService] SNMP agent going active
20:05:10,223 INFO [Webapps] Initializing partition Webapps
20:05:10,310 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:46934
-------------------------------------------------------
20:05:10,523 INFO [PlatformMBeanServerRegistration] JBossCache MBeans were successfully registered to the platform mbean server.
20:05:10,703 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:46934
-------------------------------------------------------
20:05:12,397 INFO [Webapps] Number of cluster members: 1
20:05:12,397 INFO [Webapps] Other members: 0
20:05:12,766 INFO [RPCManagerImpl] Received new cluster view: [127.0.0.2:46934|0] [127.0.0.2:46934]
20:05:12,773 INFO [RPCManagerImpl] Cache local address is 127.0.0.2:46934
20:05:12,801 INFO [ComponentRegistry] JBoss Cache version: JBossCache 'Naga' 3.0.2.GA
20:05:12,801 INFO [Webapps] Fetching serviceState (will wait for 30000 milliseconds):
20:05:12,801 INFO [Webapps] State could not be retrieved (we are the first member in group)
20:05:13,048 INFO [HANamingService] Started HAJNDI bootstrap; jnpPort=1100, backlog=50, bindAddress=/0.0.0.0
20:05:13,056 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /0.0.0.0:1102, group=230.0.0.4, HA-JNDI address=127.0.0.2:1100
20:05:13,924 INFO [UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha
20:05:14,532 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:05:14,566 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
20:05:14,893 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
20:05:14,893 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
20:05:15,214 INFO [TransactionManagerService] Initializing recovery manager
20:05:15,423 INFO [TransactionManagerService] Recovery manager configured
20:05:15,423 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
20:05:15,458 INFO [TransactionManagerService] Starting transaction recovery manager
20:05:16,104 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
20:05:16,105 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8029
20:05:16,105 INFO [StandardService] Starting service jboss.web
20:05:16,108 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
20:05:16,173 INFO [Catalina] Server startup in 132 ms
20:05:16,206 INFO [TomcatDeployment] deploy, ctxPath=/juddi
20:05:16,836 INFO [RegistryServlet] Loading jUDDI configuration.
20:05:16,837 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
20:05:16,838 INFO [RegistryServlet] Initializing jUDDI components.
20:05:17,081 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
20:05:17,145 INFO [TomcatDeployment] deploy, ctxPath=/invoker
20:05:17,264 INFO [TomcatDeployment] deploy, ctxPath=/web-console
20:05:17,716 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-2/server/all/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
20:05:17,735 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-2/server/all/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
20:05:17,798 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-2/server/all/deploy/jms-ra.rar/META-INF/ra.xml
20:05:17,854 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-2/server/all/deploy/mail-ra.rar/META-INF/ra.xml
20:05:17,919 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-2/server/all/deploy/quartz-ra.rar/META-INF/ra.xml
20:05:18,138 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
20:05:18,299 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
20:05:18,302 INFO [RAMJobStore] RAMJobStore initialized.
20:05:18,303 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
20:05:18,303 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
20:05:18,304 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
20:05:18,872 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
20:05:19,586 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
20:05:19,830 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:46934
-------------------------------------------------------
20:05:21,834 INFO [GroupMember] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@37c70c75 got new view [127.0.0.2:46934|0] [127.0.0.2:46934], old view is null
20:05:21,845 INFO [GroupMember] I am (127.0.0.2:46934)
20:05:21,845 INFO [GroupMember] New Members : 1 ([127.0.0.2:46934])
20:05:21,846 INFO [GroupMember] All Members : 1 ([127.0.0.2:46934])
20:05:21,875 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:7900
-------------------------------------------------------
20:05:27,053 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:4457 has leasing enabled, lease period 10000 milliseconds
20:05:27,053 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@b94cd40 started
20:05:27,079 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:05:27,804 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:05:28,309 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:4457 has leasing enabled, lease period 10000 milliseconds
20:05:28,309 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@52080030 started
20:05:28,311 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:05:28,345 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:4457 has leasing enabled, lease period 10000 milliseconds
20:05:28,380 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@7f91667 started
20:05:28,485 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
20:05:28,499 INFO [TomcatDeployment] deploy, ctxPath=/
20:05:28,562 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
20:05:28,752 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
20:05:28,789 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8029
20:05:28,803 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 48s:130ms
20:06:13,656 INFO [GroupMember] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@37c70c75 got new view [127.0.0.2:46934|1] [127.0.0.2:46934, 127.0.0.2:39352], old view is [127.0.0.2:46934|0] [127.0.0.2:46934]
20:06:13,657 INFO [GroupMember] I am (127.0.0.2:46934)
20:06:13,661 INFO [GroupMember] New Members : 1 ([127.0.0.2:39352])
20:06:13,661 INFO [GroupMember] All Members : 2 ([127.0.0.2:46934, 127.0.0.2:39352])
20:06:15,119 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

And here's node 50.

20:05:34,293 INFO [ServerImpl] Starting JBoss (Microcontainer)...
20:05:34,294 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
20:05:34,294 INFO [ServerImpl] Bootstrap URL: null
20:05:34,294 INFO [ServerImpl] Home Dir: /opt/jboss/jboss-5.0.1.GA-1
20:05:34,294 INFO [ServerImpl] Home URL: file:/opt/jboss/jboss-5.0.1.GA-1/
20:05:34,295 INFO [ServerImpl] Library URL: file:/opt/jboss/jboss-5.0.1.GA-1/lib/
20:05:34,295 INFO [ServerImpl] Patch URL: null
20:05:34,295 INFO [ServerImpl] Common Base URL: file:/opt/jboss/jboss-5.0.1.GA-1/common/
20:05:34,296 INFO [ServerImpl] Common Library URL: file:/opt/jboss/jboss-5.0.1.GA-1/common/lib/
20:05:34,296 INFO [ServerImpl] Server Name: all
20:05:34,296 INFO [ServerImpl] Server Base Dir: /opt/jboss/jboss-5.0.1.GA-1/server
20:05:34,296 INFO [ServerImpl] Server Base URL: file:/opt/jboss/jboss-5.0.1.GA-1/server/
20:05:34,296 INFO [ServerImpl] Server Config URL: file:/opt/jboss/jboss-5.0.1.GA-1/server/all/conf/
20:05:34,296 INFO [ServerImpl] Server Home Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all
20:05:34,297 INFO [ServerImpl] Server Home URL: file:/opt/jboss/jboss-5.0.1.GA-1/server/all/
20:05:34,297 INFO [ServerImpl] Server Data Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/data
20:05:34,297 INFO [ServerImpl] Server Library URL: file:/opt/jboss/jboss-5.0.1.GA-1/server/all/lib/
20:05:34,297 INFO [ServerImpl] Server Log Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/log
20:05:34,297 INFO [ServerImpl] Server Native Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/tmp/native
20:05:34,297 INFO [ServerImpl] Server Temp Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/tmp
20:05:34,297 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/tmp/deploy
20:05:34,902 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss/jboss-5.0.1.GA-1/server/all/conf/bootstrap.xml
20:05:35,426 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
20:05:35,429 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
20:05:35,728 INFO [CopyMechanism] VFS temp dir: /opt/jboss/jboss-5.0.1.GA-1/server/all/tmp
20:05:35,728 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
20:05:37,043 INFO [ServerInfo] Java version: 1.6.0_0,Sun Microsystems Inc.
20:05:37,043 INFO [ServerInfo] Java Runtime: IcedTea6 1.4 (suse-24.3.1-x86_64) Runtime Environment (build 1.6.0_0-b14)
20:05:37,043 INFO [ServerInfo] Java VM: OpenJDK 64-Bit Server VM 14.0-b08,Sun Microsystems Inc.
20:05:37,043 INFO [ServerInfo] OS-System: Linux 2.6.27.19-3.2-default,amd64
20:05:37,077 INFO [JMXKernel] Legacy JMX core initialized
20:05:39,802 INFO [ProfileServiceImpl] Loading profile: all from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1d7aaa0e(root=/opt/jboss/jboss-5.0.1.GA-1/server, key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all])
20:05:39,804 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1d7aaa0e(root=/opt/jboss/jboss-5.0.1.GA-1/server, key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all])
20:05:39,804 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@b83d59c{key=org.jboss.profileservice.spi.ProfileKey@b8292623[domain=default,server=default,name=all]}
20:05:41,758 INFO [WebService] Using RMI server codebase: http://ja-laptop-lnx.ja:18083/
20:05:48,271 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
20:05:48,271 INFO [NativeServerConfig] 3.0.5.GA
20:05:57,415 INFO [CorbaNamingService] CORBA Naming Started
20:06:00,670 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://ja-laptop-lnx.ja/jndi/rmi://ja-laptop-lnx.ja:11090/jmxconnector
20:06:01,066 INFO [MailService] Mail Service bound to java:/Mail
20:06:01,761 INFO [SnmpAgentService] SNMP agent going active
20:06:04,083 INFO [DefaultPartition] Initializing partition DefaultPartition
20:06:04,162 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:39352
-------------------------------------------------------
20:06:04,430 INFO [PlatformMBeanServerRegistration] JBossCache MBeans were successfully registered to the platform mbean server.
20:06:04,483 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:39352
-------------------------------------------------------
20:06:06,371 INFO [DefaultPartition] Number of cluster members: 1
20:06:06,371 INFO [DefaultPartition] Other members: 0
20:06:06,490 INFO [RPCManagerImpl] Received new cluster view: [127.0.0.2:39352|0] [127.0.0.2:39352]
20:06:06,498 INFO [RPCManagerImpl] Cache local address is 127.0.0.2:39352
20:06:06,519 INFO [ComponentRegistry] JBoss Cache version: JBossCache 'Naga' 3.0.2.GA
20:06:06,519 INFO [DefaultPartition] Fetching serviceState (will wait for 30000 milliseconds):
20:06:06,519 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
20:06:06,702 INFO [HANamingService] Started HAJNDI bootstrap; jnpPort=11100, backlog=50, bindAddress=/0.0.0.0
20:06:06,707 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /0.0.0.0:1102, group=230.0.0.4, HA-JNDI address=127.0.0.2:11100
20:06:07,525 INFO [UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha
20:06:08,079 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:06:08,097 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
20:06:08,346 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
20:06:08,346 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
20:06:08,659 INFO [TransactionManagerService] Initializing recovery manager
20:06:08,863 INFO [TransactionManagerService] Recovery manager configured
20:06:08,863 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
20:06:08,905 INFO [TransactionManagerService] Starting transaction recovery manager
20:06:09,629 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8081
20:06:09,630 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8019
20:06:09,630 INFO [StandardService] Starting service jboss.web
20:06:09,643 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
20:06:09,755 INFO [Catalina] Server startup in 242 ms
20:06:09,782 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
20:06:10,440 INFO [TomcatDeployment] deploy, ctxPath=/juddi
20:06:10,495 INFO [RegistryServlet] Loading jUDDI configuration.
20:06:10,497 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
20:06:10,497 INFO [RegistryServlet] Initializing jUDDI components.
20:06:10,751 INFO [TomcatDeployment] deploy, ctxPath=/invoker
20:06:10,833 INFO [TomcatDeployment] deploy, ctxPath=/web-console
20:06:11,239 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-1/server/all/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
20:06:11,258 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-1/server/all/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
20:06:11,352 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-1/server/all/deploy/jms-ra.rar/META-INF/ra.xml
20:06:11,390 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-1/server/all/deploy/mail-ra.rar/META-INF/ra.xml
20:06:11,428 INFO [RARDeployment] Required license terms exist, view vfszip:/opt/jboss/jboss-5.0.1.GA-1/server/all/deploy/quartz-ra.rar/META-INF/ra.xml
20:06:11,523 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
20:06:11,551 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
20:06:11,554 INFO [RAMJobStore] RAMJobStore initialized.
20:06:11,555 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
20:06:11,555 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
20:06:11,555 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
20:06:12,476 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
20:06:13,183 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [50] started
20:06:13,526 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:39352
-------------------------------------------------------
20:06:13,674 INFO [GroupMember] org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener@247de4f1 got new view [127.0.0.2:46934|1] [127.0.0.2:46934, 127.0.0.2:39352], old view is null
20:06:13,674 INFO [GroupMember] I am (127.0.0.2:39352)
20:06:13,675 INFO [GroupMember] New Members : 2 ([127.0.0.2:46934, 127.0.0.2:39352])
20:06:13,675 INFO [GroupMember] All Members : 2 ([127.0.0.2:46934, 127.0.0.2:39352])
20:06:13,800 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.2:7901
-------------------------------------------------------
20:06:14,332 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:06:15,664 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:06:15,961 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:06:15,998 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:14457 has leasing enabled, lease period 10000 milliseconds
20:06:15,998 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@4a7799a4 started
20:06:16,048 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:14457 has leasing enabled, lease period 10000 milliseconds
20:06:16,048 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@20173fce started
20:06:16,060 INFO [ConnectionFactory] Connector bisocket://ja-laptop-lnx.ja:14457 has leasing enabled, lease period 10000 milliseconds
20:06:16,060 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1dd843f1 started
20:06:16,062 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:06:16,271 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
20:06:16,308 INFO [TomcatDeployment] deploy, ctxPath=/
20:06:16,429 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
20:06:16,615 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8081
20:06:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8019
20:06:16,689 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 42s:390ms

As you can see in the log, they're on different partitions.

Thanks!

1. Re: Node's joining the wrong partition

meetoblivion Mar 31, 2009 8:16 PM (in response to meetoblivion)

and now that i'm thinking about it a bit more, it seems like it's more of a jgroups problem - even though the servers are on different partitions (just realized the cluster was showing 1 on each), the jms is showing 2 nodes.
Actions
2. Re: Node's joining the wrong partition

brian.stansberry Mar 31, 2009 9:07 PM (in response to meetoblivion)

Please post the contents of your server/all/deploy/messaging/xxx-persistence-service.xml file (where xxx depends on the database you are using).

Also, when you start the two nodes you should pass different multicast addresses to each via the -u switch.
Actions
3. Re: Node's joining the wrong partition

frankthetank Apr 1, 2009 3:03 AM (in response to meetoblivion)

Dunno about 5.0 but in 4.2.3 I had noticed that simply changing the name of the partition in clustering-service.xml was the wrong way to do this, as many other systems use the jboss.partition.name variable.

So when I, instead of setting it in the clustering-service.xml, rather set JAVA_OPTS with -Djboss.partition.name=[whatever] everything worked again.

HTH
Actions
4. Re: Node's joining the wrong partition

brian.stansberry Apr 1, 2009 9:52 AM (in response to meetoblivion)

Note that JBoss AS accepts a startup switch with shorter syntax. Instead of

-Djboss.partition.name=whatever

you can just use

-g whatever

or

--partition whatever

Internally all that happens is the value you pass is used to set the jboss.partition.name system property.
Actions
5. Re: Node's joining the wrong partition

meetoblivion Apr 2, 2009 7:29 PM (in response to meetoblivion)

yeah sorry as I tried pointing out, it's not the partition, it's the JMS. i don't see why i should point out a datasource as it's not connected to any database. thoughts?
Actions
6. Re: Node's joining the wrong partition

brian.stansberry Apr 2, 2009 7:39 PM (in response to meetoblivion)

My thoughts are perhaps you should post the server/all/deploy/messaging/xxx-persistence-service.xml file I asked for because the configuration that drives how JGroups work for JBoss Messaging is there.

The -g/-Djboss.partition.name discussion is relevant because in the standard AS configuration that system property is also used to create a unique name for the JBM JGroups channels.
Actions

Go to original post