-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
Mindville - Pre Bundled
-
None
-
3
-
Severity 1 - Critical
-
1
-
Issue Summary
Performance - loading a lot of objects with avatars causes the macro to make too many requests. Based on: https://jira.mindville.com/browse/IMFC-72
Steps to Reproduce
- The way I was able to reproduce this bug was by doing the following :
- Setup an LDAP with 3000 Users, connect it to Jira
- set for some/all of these users avatars
- Setup a Jira user import in Insight
- Connect the macro to user import schema
- Look at the network tab for the images tab requests
Expected Results
The macro should request one avatar per object
Actual Results
The macro actually doubles that number for the number of requests which overloads the server when viewing many objects per macro (500), causes application crash
# # Fatal error in CALL_AND_RETRY_LAST # Allocation failed - process out of memory # # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x00007f89e298fa19, pid=657, tid=1680 # # JRE version: OpenJDK Runtime Environment AdoptOpenJDK (11.0.10+9) (build 11.0.10+9) # Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK (11.0.10+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libj2v8_linux_x86_64.so+0xae3a19] v8::base::OS::Abort()+0x9
Workaround
Setting the macro to load small number of objects (25 while testing). You can defined more than one macro per page loading 25 each and the correct number of avatars will be called-
- duplicates
-
JSDSERVER-7387 Insight Macro for Confluence causes JVM crash
-
- Closed
-
[JSDSERVER-7193] Performance - loading a lot of objects with avatars causes the macro to make too many requests
Remote Link | New: This issue links to "Page (Confluence)" [ 587791 ] |
Link |
Original:
This issue relates to |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Link |
New:
This issue duplicates |
Link |
New:
This issue relates to |
UIS | New: 1 |
Description |
Original:
h3. Issue Summary
Performance - loading a lot of objects with avatars causes the macro to make too many requests. Based on: [https://jira.mindville.com/browse/IMFC-72] h3. Steps to Reproduce # The way I was able to reproduce this bug was by doing the following : ## Setup an LDAP with 3000 Users, connect it to Jira ## set for some/all of these users avatars ## Setup a Jira user import in Insight ## Connect the macro to user import schema ## Look at the network tab for the images tab requests h3. Expected Results The macro should request one avatar per object h3. Actual Results The macro actually doubles that number for the number of requests which overloads the server when viewing many objects per macro (500) {code:java} # # Fatal error in CALL_AND_RETRY_LAST # Allocation failed - process out of memory # # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x00007f89e298fa19, pid=657, tid=1680 # # JRE version: OpenJDK Runtime Environment AdoptOpenJDK (11.0.10+9) (build 11.0.10+9) # Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK (11.0.10+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libj2v8_linux_x86_64.so+0xae3a19] v8::base::OS::Abort()+0x9{code} h3. Workaround Setting the macro to load small number of objects (25 while testing). You can defined more than one macro per page loading 25 each and the correct number of avatars will be called- |
New:
h3. Issue Summary
Performance - loading a lot of objects with avatars causes the macro to make too many requests. Based on: [https://jira.mindville.com/browse/IMFC-72] h3. Steps to Reproduce # The way I was able to reproduce this bug was by doing the following : ## Setup an LDAP with 3000 Users, connect it to Jira ## set for some/all of these users avatars ## Setup a Jira user import in Insight ## Connect the macro to user import schema ## Look at the network tab for the images tab requests h3. Expected Results The macro should request one avatar per object h3. Actual Results The macro actually doubles that number for the number of requests which overloads the server when viewing many objects per macro (500), causes application crash {code:java} # # Fatal error in CALL_AND_RETRY_LAST # Allocation failed - process out of memory # # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x00007f89e298fa19, pid=657, tid=1680 # # JRE version: OpenJDK Runtime Environment AdoptOpenJDK (11.0.10+9) (build 11.0.10+9) # Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK (11.0.10+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libj2v8_linux_x86_64.so+0xae3a19] v8::base::OS::Abort()+0x9{code} h3. Workaround Setting the macro to load small number of objects (25 while testing). You can defined more than one macro per page loading 25 each and the correct number of avatars will be called- |
Support reference count | Original: 1 | New: 3 |
Remote Link | New: This issue links to "Page (Confluence)" [ 550673 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 550483 ] |