SSO - logon session exists in R/3 even after EP logoff

[lakshmikanthaiah_s]

Dear EP friends,

I am facing a strange and serious problem.

I am doing RFC invocation and displaying some reports on EP screen.

I have some 5 EP users, where all are mapped to a single R/3 user.

My problem is, even after EP user logoff, the R/3 connection session exists in R/3. It is not getting logoff.

This problem is really making overload on R/3 server, and making a queue of logon sessions.

Is anybody faced this sort of problem?

Please any body help me on this.

Thanx in advacen.

Early reply apprciated

kantha

[Former Member]

Lakshmikantha -

Someone asked this, and I will ask it: Which version of the portal and WAS are you using?

I have seen this problem before in EP6 SP2. The problem was solved by upgrading to a new patch level for EP6 SP2 (actually - specifically the patch for WAS) - sorry I cannot remember which one. If you are still on SP2, are you up to the latest patch level?

[Former Member]

Hi Kantha,

I am not sure abt what you want. But I think you are asking about creating a login to the Visual Admin. If so:

When you run the go.bat, a popup window comes up, where you will find a tab "new", select that. Provide a display name, select the connection as "direct to dispatcher" , provide the login name of an already existing portal administrator. Port by default is 50004.After configuring this, click on the login and say "connect"; provide the password for the user & login.

Hope this helps,

Best Regards,

Nibu.

[lakshmikanthaiah_s]

hi Wilson,

i gave 60 sec on connection life time . and restarted the server.

but still my problem not got solved

any other way?

plz reply me

[Former Member]

What version and Pack level are you @ on Portal?

We solved the same problem on SP12.

Regards!

[Former Member]

Hi Kantha,

60 seconds? Usually values like 1800 or 3600 are entered for performance reasons.

What are the other pooling properties?

Do new rfc connections appear in the backend? Do they remain open forever? The number of new rfc connections should not be more as specified in max connections.

Old "hanging" connection have to be closed manually in the backend.

regards, Karsten

[lakshmikanthaiah_s]

hi Karsten,

As you said, i gave 1800 for connectionlifetime property.

others are

runCleanupthreadInterval=60

maxTimeToWaitConnection=60

maximumConnections=20

ya in my code i have single function where at the beginning i do create the connection and execute RFC and close the connection at the end of the same function.

Any problem here??

kantha

[Former Member]

Hi Kantha,

the only tipp I can add is closing the connection in a finally block.

Like this:

finally {
  if(connection!=null)
  {
    connection.close();
  }
}

Regards, Karsten

[lakshmikanthaiah_s]

hi Karsten,

Even i did that in my code block and tried the same.

Let me make u clear the things what i am doing.

Multiple EP users are mapped to Single R/3 User.

and as i told u earlier, i did changes in Visual Administrator.

In my work, i did RFC invokation using JCA to display R/3 reports, where a single function is going to do all. With in that, i used to create connection and closing the connection using JCA APIs.

Hope it clears, what i am trying to do.

So, now problem is even after all EP user logged off R/3 user sessions exists.

reply me now

kantha

[Former Member]

Hi Lakshmikantha

Single user? Are you performing connection management (client creation , closure etc) through code or through the framework. If managed manually you will have take care of the connection life cycle yourself. Maybe posting some code here would help

Regards

Pran

[lakshmikanthaiah_s]

hi

thanx for the reply

Ya, single R/3 user,

I am establishing connection user JCA.

With in a single function, i am creating connection object and closing the same.

plz find the code below

IConnection con = null;

try {

Object connectorService =

PortalRuntime.getRuntimeResources().getService(

IConnectorService.KEY);

IConnectorGatewayService gateway =

(IConnectorGatewayService) connectorService;

ConnectionProperties connProps =

new ConnectionProperties(

request.getLocale(),

request.getUser());

con = (IConnection) gateway.getConnection(SAP.getSystem(), connProps);

...... executing RFC ..........

con.close();

} catch(Exception ex)

{

}

I am not maintaining any connection pool are something like that.

reply me

kantha

[Former Member]

Hi Kantha,

please see this thread for your solution:

You have to define a connection lifetime for the SAP Connector, otherwise the connections will never be decomposed.

You can come back to me if you have further questions.

Regards, Karsten

[lakshmikanthaiah_s]

Dear friend,

I think i am going to get answer for my problem from ur reply.

Can you help me one more thing

Basically, i tried to log on to Visual Administrator many times before, even i tried now.

And as my knowledge goes, no one ever logged on.

can u give me logon details like login, password, port and other details

plz reply me

kantha