Troubleshooting when Developer Studio stops responding
When using Developer Studio , you might encounter certain issues such as Developer Studio stops responding while you perform the create or modify operations or you get the "Stack Overflow" error message. See the guidelines described here to troubleshoot when Developer Studio stops responding. Alternatively, you can create a BMC Support case.
Symptoms
- Developer Studio stops responding while you perform the create or modify operations.
- You get the "Out of Memory" or "Stack Overflow" error message.
Scope
One or more users might experience the symptoms.
Resolution
Perform the following steps to troubleshoot when Developer Studio stops responding:
Step | Task | Description |
---|---|---|
1. | Clear the Developer Studio cache. |
|
2. | Increase the Java Heap size for Developer Studio . |
|
3. | Review the default Developer Studio logs. | The default log file is available for Developer Studio at the following location:
Copy the log file to another location and then review it so that it does not get overwritten. The log file might be huge in size depending upon the volume. See the table to troubleshoot issues based on the symptoms and error messages. |
4. | Enable Developer Studio API logging. | Enable the Developer Studio client-side API logging to view more information. See Enabling API logging for Developer Studio or see the knowledge article 000206926 . |
5. | Enable Developer Studio Java logging. | Enable the Developer Studio client-side Java API logging to view more information. See Enabling Java debug logging for Developer Studio or see the knowledge article 000210649 . |
6. | Enable AR Server logs. | Perform the following steps to enable the AR server-side API logs and SQL logs:
|
7. | Reproduce the behavior. |
|
8. | Collect the logs and review. | Copy the following log files to another location and then review them so that they do not get overwritten. A few log files might be huge in size depending upon the use case that was run.
See the table to troubleshoot issues based on the symptoms and error messages. |
9. | Create a BMC Support case. | Collect and send logs and detailed information when creating a case with BMC Support:
|
After you determine a specific symptom or error message, use the following table to identify the solution:
Symptom | Location | Action |
---|---|---|
When you perform the create or modify operation, you get an Out of Memory error. | On screen | Edit the devstudio.ini file available in the same folder as that of the DevStudio.exe file, typically
to a larger value in increments of 1024, for example:
|
Comments
Log in or register to comment.