On 05/14/2012 10:56 AM, vaibhavkhare wrote:
>
> Hi,
> I tried to install JBoss and UserApp.
> Installation was successful but when i am trying to start JBoss server
> it try to connect with some unknown IP and getting Time Out.
> logs are as :
>
> 2012-05-14 07:34:41,749 INFO [org.jboss.web.WebService] (main) Using
> RMI server codebase: http://turing-userapp.hss.hns.com:8183/
> 2012-05-14 07:34:45,523 INFO
> [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services
> - Stack Native Core
> 2012-05-14 07:34:45,523 INFO
> [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.GA
> 2012-05-14 07:34:46,118 INFO
> [org.jboss.dependency.plugins.AttributeCallbackItem] (main) Owner
> callback not implemented.
> 2012-05-14 07:34:46,879 INFO
> [org.jboss.logbridge.LogNotificationListener] (main) Adding notification
> listener for logging mbean
> "jboss.system:service=Logging,type=Log4jServic e" to server
> org.jboss.mx.server.MBeanServerImpl@1b59919[ defaultDomain='jboss' ]
> 2012-05-14 07:35:03,493 INFO
> [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
> deployment
> AbstractVFSDeploymentContext@770107{...ce-secured.jar/}
> 2012-05-14 07:35:03,493 INFO
> [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
> deployment
> AbstractVFSDeploymentContext@770107{...ce-secured.jar/}
> 2012-05-14 07:35:03,493 INFO
> [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
> deployment
> AbstractVFSDeploymentContext@770107{...ce-secured.jar/}
> 2012-05-14 07:35:03,494 INFO
> [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
> deployment
> AbstractVFSDeploymentContext@770107{...ce-secured.jar/}
> 2012-05-14 07:35:04,240 INFO [org.jboss.iiop.CorbaNamingService]
> (main) CORBA Naming Started
> 2012-05-14 07:35:06,028 INFO
> [org.jboss.mx.remoting.service.JMXConnectorServerSe rvice] (main) JMX
> Connector server:
> service:jmx:rmi://turing-userapp.hss.hns.com/jndi/rmi://turing-userapp.hss.hns.com:1190/jmxconnector
> 2012-05-14 07:35:06,188 INFO [org.jboss.mail.MailService] (main) Mail
> Service bound to java:/Mail
> 2012-05-14 07:35:06,600 INFO
> [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] (main) SNMP agent
> going active
> 2012-05-14 07:35:08,150 INFO
> [org.jboss.ha.framework.interfaces.HAPartition.Defa ultPartition] (main)
> Initializing partition DefaultPartition
> 2012-05-14 07:35:08,209 INFO [STDOUT] (JBoss System Threads(1)-3)
> ---------------------------------------------------------
> GMS: address is 172.16.100.233:39799 (cluster=DefaultPartition)
> ---------------------------------------------------------
> 2012-05-14 07:35:08,424 INFO
> [org.jboss.cache.jmx.PlatformMBeanServerRegistratio n] (main) JBossCache
> MBeans were successfully registered to the platform mbean server.
> 2012-05-14 07:35:08,581 INFO [STDOUT] (main)
> ---------------------------------------------------------
> GMS: address is 172.16.100.233:39799
> (cluster=DefaultPartition-HAPartitionCache)
> ---------------------------------------------------------
> 2012-05-14 07:35:11,285 WARN [org.jgroups.protocols.pbcast.GMS] (JBoss
> System Threads(1)-3) join(172.16.100.233:39799) sent to
> 172.16.100.216:32773 timed out (after 3000 ms), retrying
> 2012-05-14 07:35:11,609 WARN [org.jgroups.protocols.pbcast.GMS] (main)
> join(172.16.100.233:39799) sent to 172.16.100.216:32773 timed out (after
> 3000 ms), retrying
> 2012-05-14 07:35:14,287 WARN [org.jgroups.protocols.pbcast.GMS] (JBoss
> System Threads(1)-3) join(172.16.100.233:39799) sent to
> 172.16.100.216:32773 timed out (after 3000 ms), retrying
> 2012-05-14 07:35:14,614 WARN [org.jgroups.protocols.pbcast.GMS] (main)
> join(172.16.100.233:39799) sent to 172.16.100.216:32773 timed out (after
> 3000 ms), retrying
> 2012-05-14 07:35:17,289 WARN [org.jgroups.protocols.pbcast.GMS] (JBoss
> System Threads(1)-3) join(172.16.100.233:39799) sent to
> 172.16.100.216:32773 timed out (after 3000 ms), retrying
> 2012-05-14 07:35:17,618 WARN [org.jgroups.protocols.pbcast.GMS] (main)
> join(172.16.100.233:39799) sent to 172.16.100.216:32773 timed out (after
> 3000 ms), retrying
> 2012-05-14 07:35:20,291 WARN [org.jgroups.protocols.pbcast.GMS] (JBoss
> System Threads(1)-3) join(172.16.100.233:39799) sent to
> 172.16.100.216:32773 timed out (after 3000 ms), retrying
> 2012-05-14 07:35:20,619 WARN [org.jgroups.protocols.pbcast.GMS] (main)
> join(172.16.100.233:39799) sent to 172.16.100.216:32773 timed out (after
> 3000 ms), retrying
> 2012-05-14 07:35:23,293 WARN [org.jgroups.protocols.pbcast.GMS] (JBoss
> System Threads(1)-3) join(172.16.100.233:39799) sent to
> 172.16.100.216:32773 timed out (after 3000 ms), retrying
> ..................
> ........................
>
> Please Help
>
>

Greetings,
The above is because you elected to install as a cluster. In that,
it would appear you switched JGroups from utilizing UDP to TCP protocol.
When utilizing TCP, you must supply the actual IP Addresses and ports
for each node in the JBoss Cluster (including the current server).


JGroups (which is what JBoss uses to communicate with the other cluster
members) is not able to connect to the server 172.16.100.216 on port
32773. This could happen because:

1) The other server is not running at the moment
2) A firewall is blocking the port
3) Incorrect IP address for the 2nd JBoss cluster node.


If JGroups is not able to connect, it should allow the start-up of the
JBoss Application Servercontinue on after a delay.

--
Sincerely,
Steven Williams
Lead Software Engineer
NetIQ