Skip to Content
avatar image
Former Member

RFC(?) on first Application call low performance

Hello All,

I've got a problem with a JCO connection. I have a WD application, that connects via aRFC to an R/3 system. When I open this application, it takes about 20 seconds, until I get the first screen. When pressing reload, it takes just about 1 or 2 seconds. Well, I thought, this could be the initialisation of the connections to the R/3 system. So I closed all the connection from the application server via SM04 on the R/3 system. But again, it takes just 1 or 2 seconds until the connections are established and the application is shown, when reloading the application. So I assume, the connections aren't the reason for the long waiting time at initial application start.

I don't think, it's J2EE compilation time, because the server isn't restartet over night, but the first time I open the application on the next day, it takes again 20 seconds.

The application runs on the same WAS as the enterprise portal. Even if I first log in to the Portal and after this open the appliation (in the same browser window without logging off), the first time it takes 20 seconds. So it shouldn't hava to do anything with the login.

I'm using 5 Models in this applications with TASK_Scope connections. Defined is a poolsize of 50 and 100 max connections, so this should be enough for me and shouldn't be the problem either. Metadata connections are configured to 1 pool and 5 max.

I've already read different threads, blogs and PDFs like "How to Configure the JCO Destination Settings". But nowhere I got an idea, why the initial start of this application should take so long and how I could find out, what the problem is.

It's NW04 SPS19, R/3: 6.40, SPS19

I hope, anybody here has a clue about this.

Best regards,

Christian Schebesta

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Oct 11, 2007 at 09:38 AM

    Hi Christian,

    One possibility I see here is( I am not sure whether you have checked it or not) runtime analysis of RFC.

    Please check that by going to function module(SE37), menu(Function Module->Test->Runtime Analysis)



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      when it only sometimes occurs, you should maybe try to run it always with the sap-wd-showinfo parameter to verify if it is the backend or the J2EE Engine.

      Maybe you have sometimes a slow connection to R3 or the J2EE Server is busy and needs more time to create the pages.

      If you would implement some tracing in your application, you could maybe find out which method take the most time.