|
Q1
|
When calling Magic xpi from a browser, why do I get an HTTP error?
|
|
A1
|
There are scenarios where you might receive the "HTTP Error 500.19 - Internal Server Error. The requested page cannot be accessed because the related configuration data for the page is invalid." error.
In these cases, add the Authenticated Users to the Magic xpi installation folder’s permissions, as the Web requester needs to access the installation’s JRE and GigaSpaces folders.
|
| | |
|
Q2
|
When calling Magic xpi from a browser, why do I get a configuration error?
|
|
A2
|
There are scenarios where you might receive the "Configuration Error. Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'GigaSpaces.JavaToNet.DLL' or one of its dependencies. The specified module could not be found." error.
In these cases, the MS VC++ 2010 Redistributable package is probably missing. You should install this package to fix the issue.
|
| | |
|
Q3
|
Why won't Messaging Mode work properly?
|
|
A3
|
If you have problems with using Messaging Mode, you should check the [MAGIC_IBOLT] file's ActivityLogSynchronizationMode flag. This flag can be set to either Async or Sync, and governs how the Activity Log is handled:
-
Async is the default option. If you select this, the Magic xpi Server waits and enters a batch of activities in a single thread. This increases the speed, and therefore the performance, of the system.
-
Sync indicates that each thread logs its own activities. If you select this, the Magic xpi Server can log the activities in real time on the same thread that the activity is executed. Alternatively, you can balance the load for projects with many activities.
If you find that you have a problem changing this flag, in some cases this may help you to identify the particular component where the problem can be found.
|
| |
|
|
Q4
|
Why am I getting an error that the service is not in the Service table?
|
|
A4
|
The error indicates that the Magic.ini file is missing from the Web Service definition. The two most common causes for this problem are:
-
The Magic.ini is marked as read only.
-
The project was created on one machine and is now running on another.
To solve this issue, try to rebuild the .ibp (Build menu ->Build Solution). If this does not help, or you cannot do this, open your Magic.ini file, go to the [MAGIC_SERVICES] section and add the following:
= SOAP,,,,,,\resource\\.jar,0,M,
For example:
Web Services Client Example = SOAP,http://mui.magicsoftware.com/eDevCountri+
esDemo/Service1.asmx,,,,http://mui.magicsoftware.com/eDevCountriesDemo/Serv+
ice1.asmx?WSDL,D:\Magic xpi\projects\Project1\resource\Web Services Client +
Example\Web Services Client Example.jar,0,M
|
| |
|
|
Q5
|
Why can't I change the case (upper or lower) of the variable names?
|
|
A5
|
If you try and change the case of variable names, you will get the "Variable was already entered" error. This is because variable names are not case sensitive.
|
| |
|
|
Q6
|
What should I do if I get a "System Date is incorrect" error?
|
|
A6
|
An incorrect system date error is generated when a local file or directory has an accessed/modified/created future date-stamp. Solve this issue by restoring any such files or directories to the present date, through re-dating (that is, changing their date stamp). It is recommended to restart your computer after this process.
|
| |
|
|
Q7
|
Why was the Magic.ini file deleted while the project was running?
|
|
A7
|
In some cases, where there is not enough space on the disc where Magic xpi is installed, the Magic.ini file is deleted.
|
| |
|
|
Q8
|
What should I do if I get an error saying that a Magic xpa cabinet file ecf does not exist?
|
|
A8
|
To fix this error, regenerate the ifs.ini file for that particular project.
To regenerate the ifs.ini file:
-
Delete or rename the previous ifs.ini file from the project's folder
-
Save/build the project again.
This generates the new ifs.ini file.
Note: This error may occur if you copy the project from another location or from a different installation, and you have environment variables that point to a location that does not exist.
|
| |
|
|
Q9
|
When trying to run a project, the "Java Virtual Machine: Cannot be loaded (status: -4) >> Application : c:\Magic xpi\, program: Read Data.Initialize Java Parameters."error appears in the log. What does this error mean?
|
|
A9
|
The JVM load's -4 status code means out of memory. The JVM needs a continuous memory chunk, and the error indicates that it was not able to allocate this chunk.
The memory allocation for Java is set in the Magic.ini. To set the allocation, follow these steps:
-
Open the Magic.ini file and go to the JVM_ARGS= flag in the [MAGIC_JAVA] section. This flag shows the Java process's memory allocation. By default it is set to -Xms256m -Xmx256m.
-
Change the value to -Xms32m -Xmx128m and check if the error is resolved.
There is also a utility called sysinternals VMMap which displays the machine's memory usage and can help find the problem.
http://stackoverflow.com/questions/3400292/jni-enomem-from-jni-createjavavm-when-calling-dll-that-uses-jni-from-vb6
|
| |
|
|
Q10
|
Why does the flow’s Abort timeout policy not terminate the thread (flow) as expected upon reaching the specified time?
|
|
A10
|
When you set the Abort policy on a flow, the flow should be aborted and the thread terminated when the timeout value is reached.
However, there are situations where the Magic xpi server is unable to release the thread.
This behavior mostly affects the project’s thread consumption (if the thread is not released and a new one is launched). It also generates repeated "Max instance was exceeded" error messages if the flow is set with a Max instance flag.
Magic xpi has a preset internal ‘grace’ time value of five minutes. This allows a step to end if a flow was timed out and aborted, and the server was unable to terminate the executing thread.
At the end of the five minutes grace time, the process will be terminated forcefully, thus ending the flow.
|
| |
|
|
Q11
|
When I open the Magic xpi Studio, I get the following message and the Studio crashes: "Component used by the task does not exist or could not be opened". How can I fix this?
|
|
A11
|
This error indicates that Magic xpi is not able to reach one or more of the files it needs in order to open the Studio.
You should check the [MAGIC_LOGICAL_NAMES] section of the Magic.ini file and verify that the Magic xpi environment variable points to the Magic xpi installation directory.
|
| |
|
|
Q12
|
When I use Magic xpi's Text Search tool, pressing F3 or Shift+F3 does not let me navigate forwards or backwards. Why is this?
|
|
A12
|
This is a keyboard mapping issue. To fix the problem, select the Magic xpi Studio's Tools menu, followed by Options. In the Options dialog box, under Environment, select Keyboard. Then, click the Reset button. This will restore your default keyboard mapping, and F3 and Shift+F3 should then work properly with the Text Search tool.
|
| |
|
|
Q13
|
Why am I getting the following error when opening Magic xpi: "The 'MagicSoftware.iBolt.iBProjectPackage, iBolt, Version=4.5.209.1, Culture=neutral, PublicKeyToken=38692e95ed3f1bbe' package did not load correctly"?
|
|
A13
|
This error may happen when using Magic xpi on a non-supported operating system. For information about supported operating systems, see the Compatibility Guide.
|
