Agile Content Service (ACS) Destination Is Not Working for FTP Protocol Error "<BEA-000337> <[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,393" seconds working on the request "com.agile.acs.destination (Doc ID 2238521.1)

Last updated on MAY 01, 2024

Applies to:

Symptoms

ACS FTP protocol is failing during Test Destination with below error in the agileDomain.log file which is located under [Agile home]\agileDomain\servers\xxxAgileServer\logs

Error

<BEA-000337> <[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,393" seconds working on the request "com.agile.acs.destination.DestinationSessionBean_l2zeo0_EOImpl"

java.net.PlainSocketImpl.socketAccept(Native Method)
	java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:535)
	java.net.ServerSocket.implAccept(ServerSocket.java:545)
	java.net.ServerSocket.accept(ServerSocket.java:513)
	org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:806)
	org.apache.commons.net.ftp.FTPClient._storeFileStream(FTPClient.java:1106)
	org.apache.commons.net.ftp.FTPClient.storeFileStream(FTPClient.java:3852)
	org.apache.commons.net.ftp.FTPClient.storeFileStream(FTPClient.java:3885)
	com.agile.acs.op.util.DestinationUtil.ftpDestinationTest(DestinationUtil.java:255)
	com.agile.acs.destination.Destination.testDestination(Destination.java:480)
	com.agile.acs.destination.DestinationSessionBean.testDestination(DestinationSessionBean.java:279)
	com.agile.acs.destination.DestinationSessionBean_l2zeo0_EOImpl.__WL_invoke(Unknown Source)
	weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invokeInternal(SessionRemoteMethodInvoker.java:54)
	weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:21)
	com.agile.acs.destination.DestinationSessionBean_l2zeo0_EOImpl.testDestination(Unknown Source)
	com.agile.acs.destination.DestinationSessionBean_l2zeo0_EOImpl_WLSkel.invoke(Unknown Source)
	weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:685)
	weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:246)
	weblogic.rmi.internal.BasicServerRef$3.run(BasicServerRef.java:564)
	weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386)
	weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
	weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:561)
	weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:138)
	weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
	weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
	weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
	weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
	weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
	weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
	weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

Fact

- When manually accessing to FTP server from the Agile Application Server machine with the same username/password, the file can be uploaded successfully

Steps to Reproduce

1. Login to Java Client as admin user
2. Go to the Admin tab, Settings > System Settings > Agile Contents Service > Destination
3. Create Destination with below settings:
   Protocol: FTP
   ftp://{server_name}.{domain_name}
4. Set username and password
5. Click Test Destination

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.