Unsolved
This post is more than 5 years old
4 Posts
0
664
Connection to Centera getting lost after 30 seconds
In Unix platform, after connecting to Centera using org.snia.xam.XSystem connect, the connection is getting lost after 30 seconds
Getting below error in debug log
1340109780433 2012-06-19 12:43:00.433 [debug] 27696.92 [CORE] ClusterCloud::getPrimaryCluster(0) -> 0e0360a4-1dd2-11b2-892f-fc35c0b4e682
1340109780433 2012-06-19 12:43:00.433 [debug] 27696.92 [RETRY] Cluster::selectAccessNodeWithoutProbe(true) -> node #0=10.9.202.71, load=1-1
1340109900434 2012-06-19 12:45:00.434 [debug] 27696.92 [POOL] Close FPSocket (mSocket=32) Connection closed,unlocked marked(GOOD)
1340109900435 2012-06-19 12:45:00.435 [debug] 27696.92 [EXCEPTION] In 'Connection.cpp' at line 328: Exception
error=-10101
syserror=150
message=open: waitForWritingData(120000) returned zero. Connect failed for 10.9.202.71 after 120000 secs
trace=No trace available
1340109900435 2012-06-19 12:45:00.435 [debug] 27696.92 [POOL] Close FPSocket (mSocket=-1) Connection closed,unlocked marked(GOOD)
1340109900435 2012-06-19 12:45:00.435 [debug] 27696.92 [RETRY] AN(10.9.202.71) Unavailable (for 30 secs)
1340109900435 2012-06-19 12:45:00.435 [debug] 27696.92 [POOL] Close connections for addr=10.9.202.71 (num=0,max=0)
1340109900435 2012-06-19 12:45:00.435 [debug] 27696.92 [POOL] End close connections (num=0,max=0) ----
1340109900436 2012-06-19 12:45:00.436 [debug] 27696.92 [CORE] retry (0) Getpoolinfo because Exception
error=-10101
syserror=150
message=open: waitForWritingData(120000) returned zero. Connect failed for 10.9.202.71 after 120000 secs
trace=FPSocket.open(10.9.202.71,2)
Does anyone come across this issue?
What is the solution to make the connection available without getting lost after sometime?
mckeown_paul
409 Posts
0
June 20th, 2012 04:00
as i mentioned in our email discussion please log a call with EMC Support for this