Salesforce

Verifying that the Applications Started Properly (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Verifying that the Applications Started Properly (Magic xpa 3.x)

By default, the projectsStartup.xml file is defined with a test application named GSTest.

The cabinet file of this application is located in the GigaSpaces-xpa\Test folder.

As mentioned above, when the grid is started, a Magic xpa server will be started with this application.

To verify that a runtime engine was started and that the application is ready for use:

  1. From the installation shortcuts in the Start menu, click Magic xpa GigaSpaces Monitor.

  2. The Magic xpa GigaSpaces Monitor will open. By default, it will connect to the current space, but you can change the connection from the Connection Details menu.

  3. If the connection to the space was successful, the monitor’s window title will display the server being monitored. For example: Monitoring eyalr-8-lp.

  4. The monitor should also show the entries defined at the projectsStartup.xml file in the Servers list. The Status of the application entry should be Available.

Troubleshooting

Waiting for GS Agent status

If you see the application in the Magic xpa GigaSpaces Monitor, but the application status is Waiting for GS Agent, this means that Magic xpa will keep retrying, every 60 seconds, to restart the Magic xpa server, until the GSA is started on the target machine (Since version: 3.1). This status is used in the following scenario:

  • Two or more machines are running on the grid.

  • A Magic xpa server is started on one machine.

  • The second machine is shut down for maintenance and restarted after a while (for example: two hours).

Failed to start status

If you see the application in the Magic xpa GigaSpaces Monitor, but the application status is Failed to start, this means that the engine was not started properly for one of the following reasons.

1. Lack of permission to start the Magic xpa Runtime engine.

In this case, the GSA log (such as ‘2015-02-16~09.58-gigaspaces-gsa-eyalr-8-lp-10152.log’) located in the Logs folder under the Magic xpa installation will show the following error:

“2015-02-16 09:58:57,507 GSA WARNING [com.gigaspaces.grid.gsa] - [mgxpa][6/]: Failed to start process. Caused By Cannot run program "C:\Magicxpa30\GigaSpaces\..\MgxpaRuntime.exe" (in directory "C:\Magicxpa30\GigaSpaces\.."): CreateProcess error=740, The requested operation requires elevation; Caused by: java.io.IOException: Cannot run program "C:\Magicxpa30\GigaSpaces\..\MgxpaRuntime.exe" (in directory "C:\Magicxpa30\GigaSpaces\.."): CreateProcess error=740, The requested operation requires elevation”

Solution: Make sure that the user that starts the GSA has administrator rights. If you started the grid manually via the gs-agent.bat file, make sure that you start the Command Prompt app with the Run as Administrator option set.

2. The host in the projectsStartup.xml was not defined properly.

In this case, the GS log (such as ‘MgxpaGS_9744.log’) located in the Logs folder under the Magic xpa installation will show the following error:

“ERROR: 2015-02-16 10:40:37,636 [Admin GS-startRequestedWatcher-1]: locateAgent - no GSA found.Looking for Host:[EYALR-8-bad]”

The log will also contain the following line before the error line:

“INFO: 2015-02-16 10:40:37,636 [Admin GS-startRequestedWatcher-1]: locateAgent - located Host:[EYALR-8-LP],IP:[10.111.2.21].Looking for Host:[EYALR-8-bad]”

You can see from this line that the host property in the projectsStartup.xml was defined as EYALR-8-bad, but the machine host name is EYALR-8-LP and the IP is 10.111.2.21.

Solution: Change the host property in the projectsStartup.xml to contain a valid host name or IP address.

3. The lookup locator's server address was not defined properly.

In this case, the mgerror.log file located in the project folder (the default Test project folder is GigaSpaces-xpa\Test) under the Magic xpa installation will show the following error:

“<-1> 17/03/2015 19:14:39.931 [Error ] - Error: "Cannot connect to the middleware" (-150), program: Main Program”

Solution: Make sure that the address of the lookup locators server is properly defined in the GigaSpaces-xpa\bin\setenv.bat file.

Reference
Attachment 
Attachment