BAPI still active

[nicola_blasi]

Hy

we have a problem in a java portal SRM connected with UME to abap SRM system EHP2 FOR SAP SRM 7.0.

During normal activity we have an hang of system because it reaches the maximum number of connection defined by parameter "connection pool size" in portal UME configuration .

Looking for logs in default trace we have this situation:

Backend function BAPI_USER_GET_DETAIL, started 266139929 ms ago, still active

      Backend function BAPI_USER_GET_DETAIL, started 8428969 ms ago, still active

      Backend function BAPI_USER_GET_DETAIL, started 255266355 ms ago, still active

      Backend function BAPI_USER_GET_DETAIL, started 5563053 ms ago, still active

....the number of these BAPI reaches the number set in connection pool size and the system goes in hang and the only solution is restart the java portal.

We increased that parameter from 10 to 50 but after few days the problem is the same.

The portal talk with UME through the definition in System Landscape and the connection is ok ..for example for other BAPI i can see:

BAPI_USER_CHANGE@PQMCLNT010: ID=01, NUMBER=410, MESSAGE=Maintenance of user  *****etc

How can i check how BAPI_USER_GET_DETAIL is used and is it possible to set a disconnection after a defined period? Why this BAPI remains in stuck?

I found a forum sdn  but didn't help.

Thanks

Nick

[nicola_blasi]

As i supposed , the problem was in network environemnt.

It was switched in new platform , the network configuration and from that time we had problems , confirmed by the default trace that continued to givr error to lost connection to the ABAP Ume .

After the solved their configuration network problem ..also the dump didn't occurred anymore.

Bye

Nick