Some problems with stability – JS Application Server
Yes – I think he means the load sharing. Also see here: http://www.omnis.net/documentation/webdev/index.jsp?detail=07Deployment.html#server-load-sharing
> Am 09.02.2018 um 14:01 schrieb Mayada Al-Kishtini
> Hi Jan,
> Excuse my ignorance; when you say >> ” 8 omnis servers behind an LSP that handles the web calls.”, I assume this is per site/database.
> What is LSP? Is it an Omnis server load balancer or something else? I’m new to this area.
> Do you know if there is any documentation that I can read about how to do this setup?
> Thank you,
> —–Original Message—–
> From: omnisdev-en [mailto:firstname.lastname@example.org] On Behalf Of Jan Eskilsson
> Sent: Thursday, February 08, 2018 12:34 PM
> To: OmnisDev List – English
> Subject: Re: Some problems with stability – JS Application Server
> Hi Mayada and Stene
> We had similair problems with users compalaining from time to time that they cold not connect, we found 2 main reasons for this one was that the server was busy and the second that it had crashed.
> To solve this we have moved to similair setup as you, we have 4 omnis servers that are dedicated to only process backrground or long lasting jobs and 8 omnis servers behind an LSP that handles the web calls. We also dropped Windows Server 2012 in favour of Windows 2016 and all of a sudden the Omnis servers became really stable and rarely crashes. All the Omnis servers are restarted every night and since we run on Windows we also restart the hardware once a week.
> Since the move to this setup we haven’t had any connection issues at all and as a side effect we got a huge performance improvement. We have also found that its a good idea to have a couple less omnis servers than cores in the server otherwise the performance degrades. This makes sence ofcource since one Omnis server seems to never uses more than one core.
> Best Regards
> 2018-02-08 10:21 GMT+01:00 Sten-Erik Björling
>> Hi Mayada,
>> I have earlier done the script modifications in the template, a bit
>> uncertain about the use of the multiplier though. In the remote task I
>> have in the construct assigned a 60 minutes limit for inactivity and
>> in the destruct I have assigned 1 minute. These actions seems to have
>> resolved the problem so far – will stress test to the best of my
>> ability during the following days.
>> One note though…
>> It is important that the same changes are made to the jstempl in the
>> Omnis application html-folder since that eventually is involved in the
>> creation of the js-forms dynamically created by the server. I also
>> cleared out the earlier dynamically created js-files for the subforms
>> and then starting the Omnis app server.
>> I am running macOS X Server with Apache and Postgres – do not think I
>> can help in regard to the cron-jobs issue. Sorry… For those using
>> macOS X Server it is a good idea to look into different parameters to
>> increase performance of the server – Apple have really been setting
>> the parameters low.
>> Take care, all the best…
>>> 7 feb. 2018 kl. 22:10 skrev Mayada Al-Kishtini
>>> Look in the achieve for a thread with this subject ” JS Client app &
>> busy Omnis server”.
>>> The recommendation there solved various issues for me:
>>> In brief, I did these changes and things seemed to be running
>> for me (let’s keep our fingers crossed):
>>> 1- added onbeforeunload=”jOmnis.onUnload()” to your html template:
>>> So change this tag:
>>> >> “margin:0;overflow:auto”>
>>> To read :
>>> >> *onbeforeunload=”jOmnis.onUnload()” *style=”margin:0;overflow:auto”>
>>> 2- added a time out to my remote task to disconnect any idle
>> after 30 mins..you can adjust that based on your need to avoid running
>> out of licenses.
>>> Not sure if any of above solutions will solve your issue, but just
>> wanted to share my experience.
>>> We use IIS and not Apache..But I don’t think that will make a difference.
>>> More notes on this:
>>> I’m running now into some other issues (where the server is running
>> user can’t connect), our OS server runs a number of cron jobs and
>> handle web calls at the same time. I’m thinking that this is causing
>> some issues with connecting to the web form when the server is busy
>> with processing a job (which might be an http call to a third party
>> API and might take a long time to get the response or when it process a long list).
>>> So I’m investigating now the option of separating the jobs from the
>> calls. I started installing 2 servers at some sites, one to handle web
>> calls only and the other one (with no web configuration) will be
>> dedicated to process the jobs, so any issue there won’t affect the web
>> traffic. Still testing this approach.
>>> I also started installing a windows scheduled task on our sites to
>> and re-start the Omnis serer once daily to make sure that the server
>> is running until we manage to solve all its issues.
>>> I’ll appreciate if you could share any further solutions that you
>> find that help in solving the connection to your web app.
>> Sten-Erik Björling
>> Enviro Data
>> Kyrkogatan 5A 2 tr
>> SE-972 32 Luleå
>> E-Mail: email@example.com
>> Mobile: +46-70-655 11 72
>> Wire: @stenerikbjorling
>> Skype: stenerikbjorling
>> iChat: firstname.lastname@example.org
>> FaceTime: email@example.com
>> Hotmail / Messenger: firstname.lastname@example.org
>> GMail: email@example.com
>> This email and any files transmitted with it are confidential, may be
>> legally privileged and are intended solely for the use of the
>> individual or entity to whom they are addressed. If you are not the
>> intended recipient, please note that any use, distribution, or
>> reproduction of the contents of this email is strictly prohibited and
>> may be unlawful. If you are not the intended recipient, please notify
>> the sender by return email and destroy all copies of the original
>> message including any attachments thereto. Thank you.
>> Please note that we take reasonable precautions to prevent the
>> transmission of viruses; however, we cannot guarantee that this email
>> or its attachments are free from viruses. We only send and receive
>> emails on the basis that we are not be liable for any loss or damage
>> resulting from the opening of this message and/or attachments.
>> Manage your list subscriptions at lists.omnis-dev.com Start a
>> new message -> mailto:firstname.lastname@example.org
> Titles mean nothing. The one with a servant’s heart is the leader.
> Please consider the environment before you print this email.
> (1) The contents of this transmission are privileged and confidential and intended solely for the use of the addressee. Any disclosure, distribution or copying of the contents, other than by the addressee, is strictly prohibited. If you receive this transmission in error, please notify us immediately and destroy the material received.
> (2) All incoming and outgoing emails and any attachments are subjected to a virus scanner and are believed to be free of any virus, or any other defect which might affect any computer or IT system into which they are received and opened. Therefore, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Jan Eskilsson for any loss or damage arising in any way from receipt or use thereof.
> Manage your list subscriptions at lists.omnis-dev.com Start a new message -> mailto:email@example.com
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:firstname.lastname@example.org