[erlang-questions] Erlang Nodes Reconnection problem

[sandhya.adabala@REDACTED]

Hi Again,

        Here is the snippet of the ERL Snoop log captured after the
Linux PC Node is up:

########################################################################
#############


09:19:24.634965 [ aims-pc-75:32773 (gmc@REDACTED) > Jupiter:56689
(aimsserver@REDACTED) ] 141
  REG_SEND from: #Pid<gmc@REDACTED> to: global_name_server

09:19:24.638970 [ Jupiter:56689 (aimsserver@REDACTED) > aims-pc-75:32773
(gmc@REDACTED) ] 69
  MONITOR from: #Pid<aimsserver@REDACTED> to: net_kernel
   ref: #Ref<aimsserver@REDACTED>

09:19:24.642976 [ Jupiter:56689 (aimsserver@REDACTED) > aims-pc-75:32773
(gmc@REDACTED) ] 86
  REG_SEND from: #Pid<aimsserver@REDACTED> to: net_kernel

09:19:24.643224 [ aims-pc-75:32773 (gmc@REDACTED) > Jupiter:56689
(aimsserver@REDACTED) ] 67
  SEND to: #Pid<aimsserver@REDACTED>

09:19:24.646930 [ Jupiter:56689 (aimsserver@REDACTED) > aims-pc-75:32773
(gmc@REDACTED) ] 123
  REG_SEND from: #Pid<aimsserver@REDACTED> to: global_name_server

09:19:24.647133 [ Jupiter:56689 (aimsserver@REDACTED) > aims-pc-75:32773
(gmc@REDACTED) ] 72
  SEND to: #Pid<gmc@REDACTED>

09:19:24.647178 [ aims-pc-75:32773 (gmc@REDACTED) > Jupiter:56689
(aimsserver@REDACTED) ] 56
  SEND to: #Pid<aimsserver@REDACTED>

09:19:24.647201 [ Jupiter:56689 (aimsserver@REDACTED) > aims-pc-75:32773
(gmc@REDACTED) ] 37
  DEMONITOR from: #Pid<aimsserver@REDACTED> to: net_kernel
   ref: #Ref<aimsserver@REDACTED>

09:19:24.647552 [ aims-pc-75:32773 (gmc@REDACTED) > Jupiter:56689
(aimsserver@REDACTED) ] 54
  SEND to: #Pid<aimsserver@REDACTED>
"
"
"
"
"
"
########################################################################
#############


Below is the snippet of my application log which displays the messages
received:

2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:19.24 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
[Here the solaris application is sending messages but is not getting
replies]
'
'
'
'
'
'
'
'
''
'
'

2006.11.09, 09:41.37 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:41.37 ---hw_erl (#0): sending {admin,{aloha,0,[0,[]]}}
2006.11.09, 09:41.37 hw: from_hw <0.75.0>: {admin,{aloha,3,[0,[]]}} [It
is getting message only after 20 minutes]




#################################################################



Let me know if you want further details..

________________________________

From: Chandru [mailto:chandrashekhar.mullaparthi@REDACTED]
Sent: Thursday, November 09, 2006 3:42 PM
To: Sandhya Adabala (WT01 - IP-Multimedia Carrier & Ent Networks)
Cc: erlang-questions@REDACTED
Subject: Re: [erlang-questions] Erlang Nodes Reconnection problem


On 09/11/06, sandhya.adabala@REDACTED <sandhya.adabala@REDACTED>
wrote:

	Hi Chandru ,
	
	            Thanks for your inputs.Actually I have tried
checking the erlang messages using erlsnoop on solaris pc.
	            I observed flow of erlang messages from Linux node
to solaris node once it is up after a 12hrs halt.But the
	            strange thing is that the erlang node is printing
those messages very late say after 15-20 minutes.
	            This strange behaviour is not observed if the linux
pc is rebooted after less than 3 hrs halt.


Can you post the capture file or traces so we can have a look?

Chandru





The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20061109/d144786d/attachment.htm>