I get this error when trying to generate the unit test code: There is no further info on reason. It is like no go from here.
E062 - Analysis service JVM exited unexpectedly Diffblue Cover was unable to start its analysis service (used to dynamically analyze code and create tests). Service failed to start due to a JVM problem, exit code 1.
Hello @Sreedhar_Singaraju ,
Welcome to our community forum, thank you for reaching out.
We can certainly take a look at this with you.
Are you able to confirm the version of IntelliJ and the Diffblue Plugin you are currently using?
This environment event could be caused by a few reasons. The most likely two are:
Blocking of connectivity to the analysis service port or address, potentially by tools like firewall settings.
That the system was under load at the time of the execution, or the memory management recommendations are not met.
Please could you check:
That the system in question is not under significant load during execution, and also check that the memory allocation recommendations described in our doc page HERE are being met?
If there are any firewall or other restrictions/tools on the system in question that may be blocking use of specific ports/connections?
Additionally, during execution Cover will output information on the progress and steps in log files. One of these logs is a support log which can hold additional debugging information. This is usually stored in the .diffblue/log subdirectory of the project.
We recommend reviewing the log as it may contain additional information or recommendations. If you are comfortable securely sharing the log file with us (I can provide separate instructions for sharing the log file), we are happy to review this for you.
Depending on the stage at which the process progressed, there may also be a cover-server.log generated, which would be beneficial to review or share. For Windows users this would normally be located %USERPROFILE%\AppData\Local\Temp\diffblue\log, if not windows then /tmp/diffblue/log.
Kind Regards,
This happens when the number of lines of code in the source is more. Can you please let me know if there is any such limitations?
Are you able to provide an indication on the total number of lines where you see this behaviour being experienced?
We do have differences between packages (details on these can be found HERE ). For example the community edition sets out boundaries around tests per month, and test writing for individual classes or methods rather than specified lines of code. Usage that reaches the boundaries would present a message highlighting that the license constraints had been reached.
Kind Regards,
YEs the lines of code where we are seeing is ~4k.
I understand if exceed based on license it will not be E062. Thats why raised this question
Thank you for confirming on that. We would certainly not expect issues relating to the lines of code. As you say, E062 is not something presented on the lines of code, E is for environmental checks so i would want to rule out any potentially blocking or resource constraints. Were you able to review the previous suggestions?
We also have a few additional suggestions to help further diagnose the E062 code being returned. These can be found on our docs page HERE. We would also recommend reviewing these suggestions to rule out any possible file/configuration related causes.
Kind Regards,