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

Ask Your Question
0

Managing a remote deployment using a local GS-UI

We have a deployment in a data center using the latest greatest 6.5 version of GS. The deployment itself is relatively simple (clustered deployment across two machines). We run the gs-all.sh on each machine and the deploy a space into each container. We are using Java version 1.6.0-b105.

Running the GUI across the VPN tunnel from the remote system does not work well at all. So, we have been running it locally and trying to manage/view the remote system. I have seen several issues with this solution.

The most pressing issue right now is that the GUI is locking up and we have to kill the app from the command line. It seems to be locking up at random times doing seemingly random operation in the GUI. It will always happen but I can not find a pattern.

If I am dealing with a space which is auto-discovered I do not seem to have these freezing issues. The problem arises when I attempt to deal with a remote space for which I must type in the complete URL:

rmi://dev1/engmr_container1/engmr?groups=engmr

I assume this is the only and correct way to find and manage a deployment outside the multi-cast environment?

Just having the connection to the remote space seems to cause issues. At some point the GUI will lock up and will need to be killed and restarted.

Maybe we can start with the basics and go fro there.

Remotely managing,starting, stopping, etc. is supported using the GS UI?
To connect to a remote space or a specific space you must use the rmi protocol with the SpaceFinder?
Managing and manipulating the cluster is supported with remote space management?

What log files can I provide to you which will give you the necessary information to help diagnose the GUI freezes?

Thanks!

Mike

Attachments

  1. loc.jpg

This thread was imported from the previous forum.
For your reference, the original is available here

asked 2008-08-04 13:06:15 -0500

mcnoche gravatar image

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

jaissefsfex gravatar image
edit retag flag offensive close merge delete

4 Answers

Sort by ยป oldest newest most voted
0

I strongly suggest you running the UI from within the environment and access it via terminal tools such as vnc or NX (better).

Please drop me a line to shay at gigaspaces.com if u need more help here.

Shay

answered 2008-08-04 14:06:49 -0500

shay hassidim gravatar image
edit flag offensive delete link more
0

OK, that is kind of what I figured since it does not work very well when dealing with a remote space. It seems strange that this does not come up more often as this is what I would expect to be a standard way installation, maintenance and monitoring. You suggest NX which I will look into and see if that will work sufficiently for our use.

I do have a followup to the "remote" space issue...

Are there any known issues for client applications using a remote space using the same rmi url from above? We have a distributed development environment and we have a main centralized core in our main office and other pieces are being worked on remotely. h4. Attachments

[loc.jpg|/upfiles/13759717017975588.jpeg]

answered 2008-08-04 16:44:00 -0500

mcnoche gravatar image
edit flag offensive delete link more

Comments

If you still must use 1.6 - Please make sure you use the latest 1.6 JDK. 1.6.0_03 which seems to be the build you use has knows issues that manifest themselves with Jini Lookup discovery.

If there are no problems accessing the ports needed for the UI - you should be able to connect to the remote spaces without any problem and perform what ever operation you need.

You can use the jini protocol using unicast discovery to access remote spaces via the following URL format: jini://HOSTNAME_RUNNING_LUS/*/SpaceName

You can also configure the locators (list of host name running LUS) via the Setting -> Discovery -> Locator Management. See attached.

To control the UI logging levels modify \gigaspaces-xap-6.5.0-ga\config\gs_logging.properties to have the following: com.gigaspaces.admin.ui.level = ALL com.gigaspaces.admin.ui.cluster.view.level = ALL com.gigaspaces.admin.ui.spacebrowser.level = ALL

If you are running on windows change also gs-ui.bat to use the java and not the javaw. This will show some logging at the console.

If you have more than 20 spaces as part of your cluster make sure you have at least 1g Xmx for the gs-ui.

Shay h4. Attachments

[loc.jpg|/upfiles/13759717029054808.jpeg]

shay hassidim gravatar imageshay hassidim ( 2008-08-05 10:08:42 -0500 )edit
0

Thanks for the responses.

We must use Java 6 and since upgrading to the latest and greatest we have seen a significant reduction in the issues we are having. The tips for running the GS-UI are also working great and we are able to do everything we need to remotely.

answered 2008-08-07 09:52:03 -0500

mcnoche 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: 2008-08-04 13:06:15 -0500

Seen: 66 times

Last updated: Aug 07 '08