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

Ask Your Question

Client proxies and gigaspace agent

Hi all,

I have one issue with gigaspace connectivity. I've got a client service which is just a proxy to the real space service (single manager and single container). It is all working fine untill of the space container is restarted (but the client is still working) - after restart is completed, all calls to the service throw

org.openspaces.core.RemoteDataAccessException: Connect Failed to [NIO://OLGAVRYLENKO:62090/pid[8536]/4622194109_4_1333754749046052802]; nested exception is: java.net.ConnectException: Connection refused: no further information; nested exception is java.rmi.ConnectException: Connect Failed to [NIO://OLGAVRYLENKO:62090/pid[8536]/4622194109_4_1333754749046052802]; nested exception is: java.net.ConnectException: Connection refused: no further information

The problem occurs only when I run Gigaspace through Gigaspace agent. If i run space manager and space container on their own (without agent) then i do not have any problems.

But i need to use GSA in my project. Is there any solution for such problem?


Edited by: Oleksandr Gavrylenko on Dec 22, 2011 2:30 AM

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=3806]{quote}

asked 2011-12-21 13:45:21 -0500

agav gravatar image

updated 2013-08-08 09:52:00 -0500

jaissefsfex gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

The GSA is a process manager that starts and monitors child processes. So, when you restarted the container, if you are killing the GSA process, and you are also terminating the GSM child processes as well. When the single GSM process is restarted, you have to also redeploy the space, since there was no backup. If you were now using a proxy that was obtained when the space existed, you would receive such an exception.

(When you ran the GSM and GSC as separate processes, if you only restarted the GSC process, then the GSM was still alive and able to automatically redeploy the space when it detected the new GSC/container)

The recommended configuration for High Availability is to run the GSA process on multiple machines, configured for two global GSMs. In this configuration, the available GSA processes will automatically work together to ensure that primary and backup (always have at least one GSM available in the grid.) So if you were to kill an entire machine or GSA process, you would never destroy all instances of GSM.

Let me know if this helps.


answered 2011-12-21 23:29:07 -0500

staceyf 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


Asked: 2011-12-21 13:45:21 -0500

Seen: 168 times

Last updated: Dec 21 '11