Bugs item #887648, was opened at 2004-01-30 14:59
Message generated for change (Comment added) made by generalgen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=887648&group_id=22866
Category: Clustering
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim McCune (javajedi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Failed to connect to server
Initial Comment:
I've got a clustered environment (JBoss 3.2.2) where
one cluster node (not always the same one) will
sometimes just disappear from the cluster. If I invoke
calls directly on that node, everything works fine, and
it can see the rest of the cluster fine. However, the
rest of the cluster can't find it. On the disappearing
node, I get this in my server.log at the time that it
disappears:
2004-01-29 19:53:49,630 INFO [STDOUT]
-------------------------------------------------------
GMS: address is blackwidow:32844
-------------------------------------------------------
On the other cluster nodes, I get this:
2004-01-29 19:53:36,889 INFO
[DefaultPartition:ReplicantManager] Dead members: 1
2004-01-29 19:53:36,889 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Controller,service=EJB
2004-01-29 19:53:36,890 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,890 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,890 DEBUG
[DefaultPartition:ReplicantManager] notifying 2
listeners for key change:
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Controller,service=EJB
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key HAJNDI
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] notifying 1
listeners for key change: HAJNDI
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/PlanScheduler,service=EJB
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,896 DEBUG
[DefaultPartition:ReplicantManager] notifying 2
listeners for key change:
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/PlanScheduler,service=EJB
2004-01-29 19:53:36,899 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Historian,service=EJB
2004-01-29 19:53:36,899 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,899 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,899 DEBUG
[DefaultPartition:ReplicantManager] notifying 2
listeners for key change:
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Historian,service=EJB
2004-01-29 19:53:36,902 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/PlanController,service=EJB
2004-01-29 19:53:36,902 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,902 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,902 DEBUG
[DefaultPartition:ReplicantManager] notifying 2
listeners for key change:
jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/PlanController,service=EJB
2004-01-29 19:53:36,905 DEBUG
[DefaultPartition:ReplicantManager] trying to remove
deadMember 192.168.1.127:1099 for key
DCacheBridge-DefaultJGBridge
2004-01-29 19:53:36,905 DEBUG
[DefaultPartition:ReplicantManager] 192.168.1.127:1099
was removed
2004-01-29 19:53:36,905 DEBUG
[DefaultPartition:ReplicantManager] notifyKeyListeners
2004-01-29 19:53:36,906 DEBUG
[DefaultPartition:ReplicantManager] notifying 1
listeners for key change: DCacheBridge-DefaultJGBridge
2004-01-29 19:53:53,425 INFO
[DefaultPartition:ReplicantManager] Dead members: 0
2004-01-29 19:53:59,629 WARN
[org.jnp.interfaces.NamingContext] Failed to connect to
192.168.1.127:32844
javax.naming.CommunicationException: Failed to connect
to server 192.168.1.127:32844 [Root exception is
javax.naming.ServiceUnavailableException: Failed to
connect to server 192.168.1.127:32844 [Root exception
is java.net.ConnectException: Connection refused]]
at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215)
at
org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at
javax.naming.InitialContext.lookup(InitialContext.java:347)
...
It appears that the node has decided to change the port
that it's listening on, told the other nodes in the
cluster this, they have received the message, and are
trying to communicate with it on this new port, but in
fact it is not listening on this new port, so it is now
gone from the cluster?
----------------------------------------------------------------------
Comment By: general (generalgen)
Date: 2004-10-16 07:22
Message:
Logged In: YES
user_id=1140365
Hi,
Does it occur only under the cluster environment? It seems
not. I have a web server and an app server, where hosts the
EJBs. The same exception occurs sometimes when web server
calls the EJBs of the app server.
2004-10-14 11:29:44,716 WARN
[org.jnp.interfaces.NamingContext] Failed to connect to
10.50.0.36:2099
javax.naming.CommunicationException: Failed to connect to
server 10.50.0.36:2099 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect
to server 10.50.0.36:2099 [Root exception is
java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer
(NamingContext.java:215)
at org.jnp.interfaces.NamingContext.checkRef
(NamingContext.java:1183)
at org.jnp.interfaces.NamingContext.lookup
(NamingContext.java:514)
at org.jnp.interfaces.NamingContext.lookup
(NamingContext.java:507)
at javax.naming.InitialContext.lookup
(InitialContext.java:347)
......
I really don't know how to study and resolve this exception.
Do you reslove it?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=887648&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
