1TISIGINFO Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" "Failed to create a thread: retVal -1073741830, errno 11" received
Your e.g. 's JVM is running out of memory. you will need to check if that is due to message size or memory leak in your JCN.
Have fun
we are not using java compute node and also message size are 8KB on an average.. Out of memory can come due to mqm user has reached max thread utilization ?. how to calculate actual threads being used by MQ and IIB as they are running in NFS. Total number of msgflow threads are nearly 2000.
1TISIGINFO Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" "Failed to create a thread: retVal -1073741830, errno 11" received
Your e.g. 's JVM is running out of memory. you will need to check if that is due to message size or memory leak in your JCN.
Have fun
we are not using java compute node and also message size are 8KB on an average.. Out of memory can come due to mqm user has reached max thread utilization ?. how to calculate actual threads being used by MQ and IIB as they are running in NFS. Total number of msgflow threads are nearly 2000.
Each of those 2000 threads needs some memory... so it looks like you have hit some scaling limit. You may need to distribute the flow across multiple execution groups (Integration Servers) or even across multiple Integration nodes and reduce the max number of threads to keep the global e.g. (i.e. jvm ) memory withing limits. I trust you already looked into using a bigger memory / heap stack for the e.g. _________________ MQ & Broker admin
1TISIGINFO Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" "Failed to create a thread: retVal -1073741830, errno 11" received
Your e.g. 's JVM is running out of memory. you will need to check if that is due to message size or memory leak in your JCN.
Have fun
we are not using java compute node and also message size are 8KB on an average.. Out of memory can come due to mqm user has reached max thread utilization ?. how to calculate actual threads being used by MQ and IIB as they are running in NFS. Total number of msgflow threads are nearly 2000.
Each of those 2000 threads needs some memory... so it looks like you have hit some scaling limit. You may need to distribute the flow across multiple execution groups (Integration Servers) or even across multiple Integration nodes and reduce the max number of threads to keep the global e.g. (i.e. jvm ) memory withing limits. I trust you already looked into using a bigger memory / heap stack for the e.g.
It seems like mqm user number threads restrictions of about 10240 at etc/security/limits.conf . Am thinking to double it and retest again
It seems like mqm user number threads restrictions of about 10240 at etc/security/limits.conf . Am thinking to double it and retest again
tested one round of end-end testing, performance was smooth. Didn't see any messages getting piled up input queues. Earlier we were seeing messages piled up and processing slowly.
Any suggestion increase values for mqm user at /etc/security/limits.conf ?.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum