Skip to Content

Problem with Tomcat for BI 4.1

My company is experiencing an ongoing issue with a customer-facing Web site. When the BusinessObjects 4.1 report is executed everything is fine. However, if they attempt to drill down to any detail level they are prompted a second time for their BusinessObjects credentials. Restarting Tomcat services fixes this issue but only for about 30 minutes, and then the problem resumes. SAP support believed that increasing the amount of RAM on the server, which hosts both Tomcat and BusObj, would resolve the issue. We increased it from 8 GB to 32 GB and it had no effect. We then increased the Maximum Memory Pool for Java in Tomcat from 2 GB to 4 GB. This gave us a few more minutes but the problem still happens.

Needless to say, this is a serious problem. SAP says they have no technician available to address my incident until next week, so my team has no idea what to do next to get this working.

Any ideas are appreciated.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Oct 22, 2018 at 11:53 AM

    there could be several reasons for what you see.
    You will need to investigate further and also provide more details on your environment architecture.
    1. 8gb of RAM on a productive system is absolutely below even minimum recommended values, so you need to review sizing guide and size your environment accordingly :
    2. Depending on what viewer is used, the issue also can be local to the user who is drilling. So, the user browser and machine setttings can be in play.
    3. The issue could be due to webi processing server inability to process the report either due to sizing or due to report design not being efficient.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 22, 2018 at 01:34 PM

    1) As stated, increasing server RAM to 32 GB and memory pool to 4 GB did not change the behavior.

    2) I believe the webi viewer is being used, but it doesn't matter who the user is or who is executing the reports. It always happens after a certain length of time.

    3) That doesn't seem logical since the reports work until a certain amount of time lapses.

    Add a comment
    10|10000 characters needed characters exceeded

    • on 1 your earlier statement said that it added time before it happens, so it made a difference. And simply adding memory is not a proper sizing. It is more complicated than that.

      on #2 - you still haven't shared the architecture of this environment, but if it is a single server if the user is prompted again to login - either a timeout was reached or a backend server crashed and killed a user session.

      on 3 - it is logical , long processing times lead to increased resource usage on the server, which could lead to hangs/crashes.

      there is not enough information to provide any additional analysis.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.