My Oracle Support Banner

Java CAPS 5.1.2 - Batch (Record, FTP, LF) with streaming:|_ThreadID=29; ThreadName=JMS Async S3;|getEmptyWorkContainer(): still waiting (Doc ID 1025580.1)

Last updated on JULY 22, 2013

Applies to:

Oracle Java CAPS - Version 5.1.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
***Checked for relevance on 22-July-2013***


There appears to be a problem in Batch eWay(Record, FTP, LF) with streaming.

JCD consumes JMS messages, writes them to a remote file system using FTP adapter. After consuming exactly 10 messages, the JCD hangs. At this time, I am not able to stop/re-start or disable or undeploy. After recycling IS, the eWay consumes another 10 JMS messages to produce 10 more files.

I changed it to use streaming - use batch LF to write to local file system and then stream to remote file system. This did not help and noticed the same problem.

In stcms.log, you will find similar log entries as below:

[#|2007-10-16T13:58:38.339-0400|FINE|IS5.1.2||_ThreadID=29; ThreadName=JMS Async
S3;|getEmptyWorkContainer(): still waiting|#]


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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