Some problems with stability – JS Application Server
Hi Stene & Mayada,
Just like some of the solutions discussed here, when dealing with omnis web servers I have always had these (and probably some more) tricks to keep the omnis web servers functional & responsive.
1. set the timeout in $destruct of the remote task to 1min
2. have multiple omni web servers running behind the Omnis LSP
3. have a “ping” remote task that I regularly make a curl call to to establish if omnis process is alive, if not have a mechanism to kill it.
4. build a framework to monitor and manage remote tasks.
Also as Stene duly noted, if Apache is involved, try to tinker with the server configuration a bit, just to make it more load-resistant.
Regards,
Vik Shah
Director
Keys2Solutions
AU: +61 411 493 495
US: +1 (415) 413 4172
US: +1 (646) 583 2403
> On 8 Feb 2018, at 19:21, 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…
>
> Stene
>
> ______
>
>> 7 feb. 2018 kl. 22:10 skrev Mayada Al-Kishtini
>>
>> Stene,
>>
>> 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 smoother 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 connection 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 but 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 web 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 stop 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 might find that help in solving the connection to your web app.
>>
>> HTH,
>> Mayada
>
>
>
> Sten-Erik Björling
> Enviro Data
> Kyrkogatan 5A 2 tr
> SE-972 32 Luleå
> Sweden
>
> E-Mail: s-e.bjorling@enviro.se
> Mobile: +46-70-655 11 72
> Wire: @stenerikbjorling
> Skype: stenerikbjorling
> iChat: stene@mac.com
> FaceTime: stene@mac.com
> Hotmail / Messenger: stenerikbjorling@hotmail.com
> GMail: stenerikbjorling@gmail.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:omnisdev-en@lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
