Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

GSM Failed to provision with (timeout) java.rmi.ConnectIOException

We have GSM running on server1 and it started provisioning pu1 on gsc on server2. After around 25 min GSM failed with provisioning with below timeout exception. Though the gsc on server2 was running. Is this network timeout issue? Do we need to configure timeout settings somewhere?

2014-03-25 17:45:37,911 INFO [com.gigaspaces.grid.gsm.provision] [LoggingDispatcher] - GSM Attempting to allocate processing unit instance [pu1] on [GSC pid[12345] host[server2]] 2014-03-25 18:12:34,836 WARNING [com.gigaspaces.grid.gsm.provision] [LoggingDispatcher] - GSM Failed to provision service [pu1] on [GSC pid[12345] host[server2]], GSC reported: java.rmi.ConnectIOException: LRMI transport protocol over NIO broken connection with ServerEndPoint: [NIO://server2:port/pid[12345]/1625098613768234_2_3837737538744720547]; nested exception is: java.net.SocketTimeoutException: connect timed out; Nested cause: java.net.SocketTimeoutException: connect timed out; Caused by: java.rmi.ConnectIOException: LRMI transport protocol over NIO broken connection with ServerEndPoint: [NIO://server2:port/pid[12345]/1625098613768234_2_3837737538744720547]; nested exception is: java.net.SocketTimeoutException: connect timed out 2014-03-25 18:27:27,613 WARNING [com.gigaspaces.grid.gsm] [LoggingDispatcher] - GSM Unable to destroy failed service [pu1] on [GSC pid[12345] host[server2]], GSC reported: java.rmi.ConnectIOException: LRMI transport protocol over NIO broken connection with ServerEndPoint: [NIO://server2:port/pid[12345]/1625098613768234_2_3837737538744720547]; nested exception is: java.net.SocketTimeoutException: connect timed out; Nested cause: java.net.SocketTimeoutException: connect timed out; Caused by: java.rmi.ConnectIOException: LRMI transport protocol over NIO broken connection with ServerEndPoint: [NIO://server2:port/pid[12345]/1625098613768234_2_3837737538744720547]; nested exception is: java.net.SocketTimeoutException: connect timed out 2014-03-25 18:27:27,614 SEVERE [com.gigaspaces.grid.gsm.provision] [LoggingDispatcher] - GSM Provision attempt failed for [pu1] on [GSC pid[12345] host[server2]]

asked 2014-03-27 02:23:07 -0600

grtsantu gravatar image
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

Hi,

Can you please elaborate about the following

Does it happened all the time? Check the gsc log and see if there is an exception? Are you using Uni-cast or multicast? Run it again and verify there is a ping from end point to server. Any Network problems?

Yuval

answered 2014-03-31 04:46:22 -0600

Yuval gravatar image
edit flag offensive delete link more

Comments

Hi Yuval, Thanks a lot for your answer. It happened only once and when restarted it worked fine. But because its production box we are trying to find out which caused this problem. There was no network problems as such during this error. We are using unicast. Not sure if there is any timeout config which can be increased to avoid such problem.

grtsantu gravatar imagegrtsantu ( 2014-03-31 05:13:02 -0600 )edit
0

Hi,

There is "-deploy-timeout" which you can use for setting the deployment timeout. You can find details here: http://docs.gigaspaces.com/xap97/depl...

But in your case it does't make sense to increase it. I need the client and the gsc logs in order to find what cause the deployment to fail.

Yuval

answered 2014-04-01 09:03:45 -0600

Yuval gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-03-27 02:23:07 -0600

Seen: 755 times

Last updated: Apr 01 '14