Batch eWay collaboration hangs after processing a few records

(Doc ID 1273429.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Java CAPS - Version 5.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 28-August-2013***


A JCD that is using Batch FTP in manual connection mode might hang after processing a few records. This hang is usually identified by the fact that the JCD stops logging anything after a specific point in the code.

When creating a java thread dump for the Integration Server JVM, a call stack similar to the following can be seen for the hanging thread:

"JMS Async S412" daemon prio=10 tid=6000000009df2940 nid=483 lwp_id=4410245 in Object.wait() [9ffffffef10fe000..9ffffffef1100a40]
at java.lang.Object.wait(Native Method)
- waiting on <9fffffff7ba28c70> (a java.lang.Object)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(
- locked <9fffffff7ba28c70> (a java.lang.Object)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(
at com.sun.enterprise.resource.PoolManagerImpl.getResource(
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(
at ch.uhbs.jcaps.prjusb_eai.mdm.dokumenttohydmedia.jcdHyddocQueryBo.getPdfFromFtp(ch.uhbs.jcaps.prjusb_eai.mdm.dokumenttohydmedia.jcdHyddocQueryBo:279)
at ch.uhbs.jcaps.prjusb_eai.mdm.dokumenttohydmedia.jcdHyddocQueryBo.receive(ch.uhbs.jcaps.prjusb_eai.mdm.dokumenttohydmedia.jcdHyddocQueryBo:98)
at FromH1N1.svcHyddocQueryBo.jcdHyddocQueryBo_Runtime_Handler.handleRequest(FromH1N1.svcHyddocQueryBo.jcdHyddocQueryBo_Runtime_Handler:387)


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms