Re: Email Restriction - ARS 7.1 Patch 005
Thanks for both responses. We too are 64bit W2003 servers (Chris - we've gone back and forth many times on mid-tier issues). I need to get supports buy off on the suggestions and if they don't apply to a 64 bit OS then... We've been up in production (finally) now for a whole 4 days and bave generated 46,000 notifications. R5 didn't have such a bottleneck so there was never an issue and in testing we never generated but a few hundred a day. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Re: Email Restriction - ARS 7.1 Patch 005
FYI, we have been running with the settings Tauf listed below for quite some time (2, 5a, and 5b). Our memory is -Xms512m and -Xmx 1024m, but we are on a 64-bit Win2K3 server with 12 gb RAM so the only limitation is the 32-bit Java. Our ChunkSize=100, but our OutgoingConnectionRecycleSize=500 Polling Interval in the configuration form is 5 minutes. These settings have been scrutinized by support MANY times since we have been working on an issue with the 7.1.00.002 and 004 email engine dying silently since June 2008. Sometimes it dies on a failure to parse incoming mail, but frequently it is just a silent death where the service is hung. The latest armapi71.dll we are using appears to have solved the parsing problem, but the jury is still out on long-term stability (the latest is the dll in patch 7.1.00.006). I have not been seeing a backlog of messages (except when it hangs), but we normally have only 1000 to 2000 outgoing messages on a work day. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Chowdhury, Tauf Sent: Tuesday, March 24, 2009 4:37 PM To: arslist@ARSLIST.ORG Subject: Re: Email Restriction - ARS 7.1 Patch 005 ** Todd, I think your issue might be the java heap size. The following will show you how to increase the # of threads used to 4. You can try the following (assuming windows here): 1. Open up the registry and go to: HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>BMC Remedy Email Engine>Parameters 2. Edit the JVM Option Count. Should be set to 2. Change it to 4. 3. Create a new String. Value name should be JVM Option Number 2 Value data should be -Xms128m 4. Create another new String. Value name should be JVM Option Number 3 Value data should be -Xmx512m 5. Now in the emaildaemon.properties file, use these params: a. com.bmc.arsys.emaildaemon.NumberOfSenderThreads=4 b. com.bmc.arsys.emaildaemon.FetchUserGroupInfoOnDemand=true Hope this helps your performance woes. It helped me a great deal. Tauf Chowdhury Analyst, Service Management Office: 631.858.7765 Mobile:646.483.2779 From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Pasterski, t...@dts Sent: Tuesday, March 24, 2009 5:23 PM To: arslist@ARSLIST.ORG Subject: Email Restriction - ARS 7.1 Patch 005 ** In the emaildaemon.properties (7.1 P5) there is a parm: which restricts the number of messages sent with each poll to 100. I suppose that normally that is adequate if you poll every minute but during heavy message traffic even then it can cause significant delays. You cannot increase the parm or the email engine will fail to start. Support suggested adding parms: com.bmc.arsys.emaildaemon.NumberOfSenderThreads=1 com.bmc.arsys.emaildaemon.OutgoingConnectionRecycleSize=200 But for what I don't know, didn't change a thing. I tried to remove the ChunkSize parm and raise the RecycleSize and no change also. 100 is just inadequate, we have 9000 in the queue now! Anyone else experience this / have a solution? Todd __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Re: Email Restriction - ARS 7.1 Patch 005
Todd, I think your issue might be the java heap size. The following will show you how to increase the # of threads used to 4. You can try the following (assuming windows here): 1. Open up the registry and go to: HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>BMC Remedy Email Engine>Parameters 2. Edit the JVM Option Count. Should be set to 2. Change it to 4. 3. Create a new String. Value name should be JVM Option Number 2 Value data should be -Xms128m 4. Create another new String. Value name should be JVM Option Number 3 Value data should be -Xmx512m 5. Now in the emaildaemon.properties file, use these params: a. com.bmc.arsys.emaildaemon.NumberOfSenderThreads=4 b. com.bmc.arsys.emaildaemon.FetchUserGroupInfoOnDemand=true Hope this helps your performance woes. It helped me a great deal. Tauf Chowdhury Analyst, Service Management Office: 631.858.7765 Mobile:646.483.2779 From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Pasterski, t...@dts Sent: Tuesday, March 24, 2009 5:23 PM To: arslist@ARSLIST.ORG Subject: Email Restriction - ARS 7.1 Patch 005 ** In the emaildaemon.properties (7.1 P5) there is a parm: which restricts the number of messages sent with each poll to 100. I suppose that normally that is adequate if you poll every minute but during heavy message traffic even then it can cause significant delays. You cannot increase the parm or the email engine will fail to start. Support suggested adding parms: com.bmc.arsys.emaildaemon.NumberOfSenderThreads=1 com.bmc.arsys.emaildaemon.OutgoingConnectionRecycleSize=200 But for what I don't know, didn't change a thing. I tried to remove the ChunkSize parm and raise the RecycleSize and no change also. 100 is just inadequate, we have 9000 in the queue now! Anyone else experience this / have a solution? Todd __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ ** This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Email Restriction - ARS 7.1 Patch 005
In the emaildaemon.properties (7.1 P5) there is a parm: which restricts the number of messages sent with each poll to 100. I suppose that normally that is adequate if you poll every minute but during heavy message traffic even then it can cause significant delays. You cannot increase the parm or the email engine will fail to start. Support suggested adding parms: com.bmc.arsys.emaildaemon.NumberOfSenderThreads=1 com.bmc.arsys.emaildaemon.OutgoingConnectionRecycleSize=200 But for what I don't know, didn't change a thing. I tried to remove the ChunkSize parm and raise the RecycleSize and no change also. 100 is just inadequate, we have 9000 in the queue now! Anyone else experience this / have a solution? Todd ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
