on 03-10-2017 3:54 PM
Hi,
We noticed earlier some health warnings on the webi proc. servers - we have 4 of them whereby number of active sessions seemed to be rising and is more than the number of cmc/sessions -0 it is as if sessions not being released/recycled back into the pool.
One thought is we have some external users and there are networking problems out of our control at moment with these and if their session is interrupted guess this will leave active session?
Is there anything we can do to ensure sessions are released in such circumstances ?
Anyone else aware of anything which causes sessions to continue to rise without extra reports/users logging in - seems occasionally problem with recycling sessions back to pool.
All looks o.k. now but wonder on people's thoughts aimed to keep number of active sessions down - we already have session timeouts set but need these a certain length to allow reports to complete.
Thanks
If same user opens multiple webi reports - that will create multiple sessions on webi proc server.
If user is not logging off from BILP or WRC - the sessions will remain till timeout or webi ps restart.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for replies - hand't noticed them as not sure possible to set up e-mail notification when get replies to questions. external network problem was resolved but good to know options above
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the steps below. This should release the session.
Please do the steps below to get the sessions released after the processing is completed:
1. Stop Tomcat.
2. Go to the following path and find the dsws.properties file:
C:\Program Files (x86)\SAPBusinessObjects\Tomcat6\webapps\dswsbobje\WEB-INF\classes
3. Find the following parameter:
# uncomment line below to deactivate the WebiSession/WebiDocumentcache on the appserver side (DAAWS only)
#qaaws.closedocument=true
4. Change the parameter as below:
# uncomment line below to deactivate the WebiSession/WebiDocumentcache on the apppserver side (DAAWS only)
qaaws.closedocument=true
5. Restart Tomcat and SIA.
If the steps above didn't help I'll definetely need a BI Landscape tohave a look on your configuration.
Please seeKBA 1922012 if you need any furtherassistance about this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the setting of webi processing server "Max connections"? Once it hits the limit, if there is any other requests coming to webi processing server Idle connection timeout for about 20 minutes or what ever the setting you have in your environment, WEBI processing server recycle by itself.
Is there any schedules running?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.