Hi Community,
Over the last few months we encountered a serious problem when launching reports and macros (that created PDF files of models). Every time any of the modelers launched one of these reports or macros the server simply crashed and ejected all users.
With the assistance of ARIS Support we have been looking for a solution to this problem. Log files did not give any direct clue on the cause. Aris Community articles hinted towards a possible problem with the available memory. Another proposed cause was a bug in the JRE when painting round things in a graphic.
Several updates of the ARIS software were executed. We actually work now with version 7.2. And everytime we had the impression on the acceptance server that the issue had been resolved. However when updating the production server the problem reappeared.
So after increasing the software memory and updating to 7.2 standard, we discovered an oddity with the Java versions of the acceptance and production server. The former was running version 1.6.0_24 and the latter 1.6.0_17.
So we decided to manually replace the Java version on the production server by the one of the acceptance server and now the problem seems to be solved completely. Over 50 tests with the reports and macros never led to a server crash.
So if ever the same problem would happen to you, a lead would be to check your Java versions. We will keep an eye on the Java versions with every update of the ARIS software in the future.
Hope this can help someone.
Regards
Hi Bruno,
So to be sure, we should be using the 1.6.0_24 version? I would also be interested in why you would need the JRE installed on the server. In general when installing the server, I never install the JRE, unless I want to run/test the web client directly on the server. Is the JRE required on the server? If so, why? What do you normally do in testing, do you just run the tests directly on the server?
Thx,
Francois
Hi François,
I don't know if you need to use 1.6.0_24 as such. I only know that only the versions of Java on acceptance and production server were different. Since the report worked on acceptance and not on production, it was the most probable cause we found. Replacing the Java version on the server just did the trick.
As for the root cause of the problem, honestly we do not know.
regards
