Webi processing server exceeded maximum connections

[Former Member]

Hi guys

Webi crashed as the webi processing server exceeded the maximum connections which is set to 450 in our case. Maximum concurrent sessions allowed is 55.

What is the difference in Webi sessions and maximum connections?

We had to restart the server to make it work.... What is the way out to make sure this does not happen in future?

We are on BO 4.1

[Former Member]

Thanks for all the suggestions guys

[former_member187093]

Hi There, Actually, outproc parameter open a new child process for each job(it will not share the same process for more than one job).

you can increase the no of connections or add one more webi processing server based on the resource availability (RAM and processing power)

hope this helps!

[amitrathi239]

Hi,

check mentioned sap note.

2236804 - In Business Intelligence 4.1, when the current active sessions is higher than the Maximum ...

Amit

[Former Member]

Thanks Amit

I did try replicating this issue in our dev environment but I could not generate that error.

I set the maximum connections to 5 and when I ran multiple webi reports, I made the active session count in webi processing server to 9 but I did not get any error messages ..

Is active session count same as total connections? how can I monitor the total connections?

[former_member191664]

It'd be premature to jump to conclusion that max webi session kills your server.  I suspect one of the webi report has some dirty data or something triggers your WIReportServer to crash.

If you are on Linux/UNIX, look for core to gdb it, and gdb will tell you what process and what library it crashes at that time.  Then, you can use this finding for SAP BO support.

If Windows, tracing and try and error is the way to find the trouble maker.

Regards,

Jin-Chong

[Former Member]

whats the best way to identify most time consuming report at a particular time?

[former_member205194]

Hi Nutty,

1) Max connections exceeded - you would have got this error, as load of the WebI servers was high at that time.

2) Load could be HIGH for 2 reasons -

a. due to large number of Webi reports scheduled at that time. This generally happens when reports are scheduled in BULK using some utility

b. due to adhoc running of reports directly from BILaunchpad by lots of users. This could happen if there is a new project just gone LIVE in production, or there is some month-end period going on.

3) You can find the exact load from the Audit DB. Find the number of reports that were run/refreshed/scheduled during that time interval.

4) How to avoid this going forward -

a. You will have to monitor the load on Webi servers from the Audit DB on a daily basis

b. If the load if nearing threshold regularly, then that implies that time has come to expand the system to accommodate more load.

c. If the CPU / Memory of the servers are still under-utilized, you might want to create a new WEBI server on the same node.

d. If the CPU/Memory are also nearing threshold, then you would have to think adding new nodes to the platform.

Do let me know if you have any queries.

Hope this helps.

Regards,

Monish

[Former Member]

In Adaptive Job Server add -outproc force terminate and it will kill all child process

[Former Member]

This SAP note has not been released I guess. I get the below message :-

This note has not been released

Error Code: /SVT/SNO_MSG_ODATA/004

[DellSC]

There is nothing I can find in the Webi Processing Server properties about sessions - are you talking about your concurrent licenses?  If so, they have nothing to do with this issue - it's just the number of users who can log in to the system at the same time.

The "Maximum Connections" setting is how many users and/or running schedules can be connected to the Webi Processing Server at the same time.  Since some users may have multiple reports open and you may be running multiple schedules, this can add up fairly quickly.  The default value is, I think, 200.

Instead of adding connections to the Webi Processing server, I would "clone" so that you have multiple instances of it.  It will give you automatic fail-over if one of them goes down.  Some of this will depend on the RAM and CPU resources on the server, though.  What are the specs for the server where BO is installed?

-Dell

[Former Member]

Thanks Dell

Is there a way I can identify the root cause of this issue... As in what report/scheduled were run at the time when the 'connection' count reached at its peak?

[mhmohammed]

Hi Nutty,

Did you check the log files under .../SAP BusinessObjects Enterprise XI 4.0/logging/? That should have some traces.

And/or try updating the level of logging level for WebiProcessingServer -> Properties -> Trace Log Service -> Log Level -> set it to High and run the job again.

How about the parameters in Adaptive Job Server -> Properties -> Webi Scheduling Service? Is that relevant at all?

Thanks,
Mahboob Mohammed

[Former Member]

I am not sure how relevant it is.

[DellSC]

You can also look at the Audit database (if you have auditing turned on) to see what was running during that time period.

-Dell