Skip to Content
0
Former Member
Jun 24, 2008 at 07:07 PM

EWA GCA TASK for portals

38 Views

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