Hi Eduard,
Just to be clear, I am not saying that changing the timers from the
default values is necessarily bad. Just that you should think about it
and be aware of the consequences of such a change beyond just "fixing"
some specific issue.
All the best, Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Eduard Sluis <eduard_sluis@xxxxxxxxx>
To: "Web Enabling the IBM i \(AS/400 and iSeries\)"
<web400@xxxxxxxxxxxx>,
Date: 2013-01-25 08:01
Subject: Re: [WEB400] Webfaced Menu not displaying messages
Sent by: web400-bounces@xxxxxxxxxxxx
Thanks Mike,
I agree that fiddling with the timers is not the appropriate way to go.
We will look into our options as the RFE path bears uncertainty and off
course untimeliness whilst we can not 'sell' the 500 error to our valued
clients.
Thanks again!
Kind regards, Eduard.
________________________________
From: Mike Hockings <hockings@xxxxxxxxxx>
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Sent: Wednesday, January 23, 2013 2:33 PM
Subject: Re: [WEB400] Webfaced Menu not displaying messages
Hi Eduard,
There are a number of timers running in WebFacing to handle cases where
things might stop responding.
WAS session inactivity timer (default 30 mins) if there is no activity in
the app. The value of this timer is also used to time-out the IBM i user
job at about the same time.
IBM i job transaction timer (default 5 mins) times the response of the IBM
i job handling a request from the webapp. This prevents stuck
transactions on the IBM i from constipating things. This value can be
changed via config of the WF server
WF server TCP/IP read timer (default 10 mins IIRC). This is a hard-coded
TCP/IP read time-out on most blocked reads by the server. It prevents a
session from being zombie'd by an unresponsive webapp.
Plus there are the normal TCP/IP communications timers set on the
platforms used.
In general I would say that WF was designed to present an interactive
program on the Web not necessarily handle long waits for big compute jobs
or uploads. Making drastic changes to the timer values might provide
short-term solutions but could be detrimental to the app stability in the
long haul. So what _I_ would consider is to do it a different way - maybe
spin off a separate thread or batch job to just do the upload and have a
way to check it's status.
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Eduard Sluis <eduard_sluis@xxxxxxxxx>
To: "Web Enabling the IBM i \(AS/400 and iSeries\)"
<web400@xxxxxxxxxxxx>,
Date: 2013-01-23 11:29
Subject: Re: [WEB400] Webfaced Menu not displaying messages
Sent by: web400-bounces@xxxxxxxxxxxx
Thanks Mike,
Not in the webfacing part/team anymore though.....
I will do the RFE path.
Now I have problems that the webfacing sessions timesout when doing rather
longrunning upload processes (compliancy databases).
Webfacing thinks that the server does not react on the request so after 5
minutes it gives an 500 error while the process is nicely running
and regularly provides update messages.
Would not give this problem when I would do the same (send update
messages) but to a MSGSFL in a program.
From my perspective (ignorance) it is however exactly the same for the
system.
Kind regards,
Eduard.
From: Mike Hockings <hockings@xxxxxxxxxx>
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Sent: Friday, January 18, 2013 3:16 PM
Subject: Re: [WEB400] Webfaced Menu not displaying messages
Hi Eduard,
It has been a couple of years or so since I worked on WebFacing
development but at that time there was no mechanism to asynchronously push
messages to the screen.
You could always open an RFE to request the change on the RFE Community
site
http://www.ibm.com/developerworks/rfe/
All the best, Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Eduard Sluis <eduard_sluis@xxxxxxxxx>
To: "Web Enabling the IBM i \(AS/400 and iSeries\)"
<web400@xxxxxxxxxxxx>,
Date: 2013-01-18 11:39
Subject: [WEB400] Webfaced Menu not displaying messages
Sent by: web400-bounces@xxxxxxxxxxxx
Hi all,
We have our application Webfaced through Webfacing which is also
using MNUDDS menus.
Several called programs are sending status messages to the *EXT
MessageQueue on the level of the menu.
In 5250 they are nicely displayed in the bottom of the menu.
In Webfacing we do not see these messages.
I've searched around to find a solution for this as we also want to have
these messages visible on the Webfaced menu.
I could however not find anything related.
That leads to the questions:
- Is it possible to see these messages on a Webfaced menu?
- If possible: What would be needed to do to get them??
Kind regards,
Eduard Sluis
midrange.com
