The problem: You started a client application and got an error message ending with:
Solving this problem...
Possible cause |
Checking if this is the cause |
Solution |
Cluster did not deploy, or cluster has wrong name. |
- In the GS-UI, switch to Deployments view using the button on the left (in GigaSpaces 5.X) or click the Deployments, Details tab on the left (in GigaSpaces 6.X).
- In the tree under Service Grid Network on the left, expand Service Deployments.
If you do not see a deployment called myDataGrid, this is what caused the problem.
|
Shut down all GigaSpaces instances and the GS-UI, and go back to Deploying the Data Grid above. |
You changed the default lookup group in setenv.bat. |
- Open the following file in a text editor: <GigaSpaces Root>\bin\setenv.bat.
- Search for the string LOOKUPGROUPS=
If the string following the = is something other than gigaspaces-XY (where X is your version number and Y indicates your product edition), this is what caused the problem.
- Take note of the current value of the LOOKUPGROUPS variable.
|
You need to re-run the application with a different space connection URL (substitute the current value of the LOOKUPGROUPS parameter for X):
- If there are no arguments at the end of your URL, append ?groups=X to the end of the URL.
- If you already have an argument at the end of the space URL, such as ?useLocalCache, append &groups=X to the end of the URL.
|
The problem: You started a client application and got the following error message:
Solving this problem...
Cause |
Solution |
Example was placed in incorrect path. |
Copy the example into the following path: <GigaSpaces Root>\examples\Basic\example-name. |