Java in hung status(at start framework phase) due to lock collision

[Former Member]

#2.0^H#2015 05 09 06:59:05:669#+00#Error#com.sap.uddi.server.handlers.UddiConfigurationHandler#

#BC-ESI-UDDI#tc~esi~uddi~server~core~service#E839359D440E00160000000300006C66#587797350000002564##com.sap.uddi.server.handlers.UddiConfigurationHandler####B817A690F61811E4C9FDE839359D440E#b817a690f

61811e4c9fde839359d440e#b817a690f61811e4c9fde839359d440e#0#Service Runner [tc~esi~uddi~server~core~service]#Plain##

An ConfigurationLockedException occured while trying to obtain configuration in write mode

[EXCEPTION]

com.sap.engine.frame.core.configuration.ConfigurationLockedException: Can not lock Configuration "uddi_service" because it is already locked.

        at com.sap.engine.core.configuration.impl.ServerEnvironment.lockConfiguration(ServerEnvironment.java:600)

        at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:862)

        at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:932)

        at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:890)

        at com.sap.uddi.server.handlers.UddiConfigurationHandler.getConfiguration(UddiConfigurationHandler.java:1085)

        at com.sap.uddi.server.handlers.UddiConfigurationHandler.saveApplicationProperties(UddiConfigurationHandler.java:823)

        at com.sap.uddi.server.handlers.ParameterHandler.saveParamMapToDb(ParameterHandler.java:804)

        at com.sap.uddi.server.services.PropsServices.saveParamsToDB(PropsServices.java:1048)

        at com.sap.uddi.server.services.BootServices.saveParams(BootServices.java:426)

        at com.sap.uddi.server.ServiceInitializer.initializeUddiService(ServiceInitializer.java:74)

        at com.sap.uddi.server.UddiCoreServiceFrame.start(UddiCoreServiceFrame.java:39)

        at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:160)

        at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)

        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)

        at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)

        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [I2015050906585753500000friaxs70.eame.syngent.....587797350, !J2EE_CONFIGURATION_MANAGER, ed1b8cca/@@@@@@@@@@@@@@@@@@@@@@@@@@

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@, X]; it is in use by another owner. The lock collision occurred with user <intern

1.We could see in default trace some services like  uddi_service & 587797350, !J2EE_CONFIGURATION_MANAGER, ed1b8cca has been locked

2.Kindly suggest a way to unlock this services,as java is down so nwa & telnet admin console cant be accessed

Any other way for it

[former_member198633 · Accepted solution]

Hello Gopinath,

When LockExceptions occur it is important to create thread dumps exactly when the problem is present. The administrator has only a few minutes to act and create the dumps. Then gather the corresponding defaultTrace files as well and note the timestamp. Whenever such issue occurs these steps should be followed:

1. Thread dumps, defaultTrace, screenshot, timestamp

2. Find the locking thread for the corresponding timestamp in the default trace.

3. Find the stack trace of that thread in the std_serverX.out file.

4. Determine the status and the application.

The thread dumps are also helpful when we need to investigate hangup situations.

Best Regards,

Peter Tari

[former_member185239]

Hi Gopinath,

Have you tried to clear the locks from MMC?

check the below link , how to clear the lock

(JSTTSG)(HOWTO)RemoveLocks - Technology Troubleshooting Guide - SCN Wiki

With Regards

Ashutosh Chaturvedi

[former_member185239]

Hi Gopinath,

Kindly check the sapnote http://service.sap.com/sap/support/notes/1911632

If you can change the error message to warning then the phase will pass.

Also do paste the std_serverX and default profle.

With Regards

Ashutosh Chaturvedi

[manumohandas82]

Hi

Do you have multiple server nodes  / application servers ?

Why dont you try starting one by one .

Check the following Note

1911632 - ConfigurationLockedException when open configuration in UDDI

Shouldn't be the reason if java is not starting

Thanks ,

Manu