cancel
Showing results for 
Search instead for 
Did you mean: 

Sesion LockException

Former Member
0 Kudos

Hi

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 [4] failed to acquire exclusive lock on client session ClientSession(id=(J2EE8518000)ID0200294550DB11707589215029835099End) due to thread HTTP Worker [2]. The details of the locking thread are shown in the following stacktrace.

at com.sap.mw.rfc.driver.CpicDriver.nativeCpic_coxread(Native Method)

at com.sap.mw.rfc.driver.CpicDriver.cpic_coxread(CpicDriver.java:992)

at com.sap.mw.rfc.driver.CpicDriver.coxread(CpicDriver.java:229)

at com.sap.mw.rfc.driver.RfcTypeDirectCpic.read(RfcTypeDirectCpic.java:38)

at com.sap.mw.rfc.engine.RfcIoOpenCntl.ab_rfcread(RfcIoOpenCntl.java:304)

... 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 .

Priyanka

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Priyanka,

I had encountered this kind of error in a similar situation. The Web Dynpro application was taking a lot of processing time for some operation and while it was loading, I had redeployed the application. after the redeployment I got the error mentioned.

As the object is locked by the application server, we had restarted our J2EE Server.

After the restart the application was running fine.

This sounds a bit crude, but worked for me.

Regards,

Alka.

former_member185086
Active Contributor
0 Kudos

Hi

If the problem is same as alka mentioned, other reason could be for this is ,performing heavy task (too many initialization of backend )at WdDoinit() of component controller and further same on view controller .

(It might be the possibility so check the code again.)

Best Regards

Satish Kumar

Former Member
0 Kudos

Hello,

Restart your sdm and try deploying and running the application again.

Former Member
0 Kudos

I already restarted it but that does not seem to help.