While executing a web dynpro application which uses adaptive RFC models, I encountered the following exception:
com.sap.tc.webdynpro.services.session.LockException: Thread HTTP Worker  failed to acquire exclusive lock on client session ClientSession(id=(J2EE8518000)ID0200294550DB11707589215029835099End) due to thread HTTP Worker . The details of the locking thread are shown in the following stacktrace.
at com.sap.mw.rfc.driver.CpicDriver.nativeCpic_coxread(Native Method)
... 127 more
On going through the trace what I could make out was that since the RFC was taking unexpectedly longer time, it resulted in active request holding the lock for longer than expected. Could there be other possible reasons?
Also, SSO is configured for portal-backend. Could changing some setting there could help? Should the bapi be looked into to perform better or tehre are some ways from portal end as well? Please suggest some pointers .