Input File Data Read By BatchFTP Adapter And Sent To JMS Queue Is Lost When Project Is Redeployed

(Doc ID 1383136.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.2 to R6.2 [Release 6.0]
Information in this document applies to any platform.
***Checked for relevance on 12-May-2014***

Symptoms

Have a repository based project that uses the BatchFTP Adapter to fetch files and send data to a stcms JMS queue using the JMS send() method. After each file is processed it is renamed as per the BatchFTP PostTransferCommand setting. The project was redeployed whist messages were being processed. Afterwards it was noticed that the file was renamed on the FTP server but the message was not processed and sent to the stcms JMS queue.

The following exception appeared in the server.log file when the problem occurred:

[#|2011-10-18T09:21:10.359+0200|SEVERE|sun-appserver2.1|com.stc.codegen.JMSImpl.runtime.JMS|_ThreadID=367;_ThreadName=JMS Async S1529288;Context=Kages | prj_Bef/svcDokMedocsIn/queBefLookupIN;_RequestID=581decc0-6c29-485e-9908-ed3a95bf6fa1;|javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/stc/deployedServices/AssistantServiceBean [Root exception is java.lang.NullPointerException]
javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/stc/deployedServices/AssistantServiceBean [Root exception is java.lang.NullPointerException]
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:224)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:407)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.stc.codegen.JMSImpl.runtime.JMS.send(JMS.java:465)
at Kages_KonfigprjBefTransfer.jcdDokMedocsIn.receive(Kages_KonfigprjBefTransfer.jcdDokMedocsIn:1217)
at prj_Bef.svcDokMedocsIn.jcdDokMedocsIn_Runtime_Handler.handleRequest(prj_Bef.svcDokMedocsIn.jcdDokMedocsIn_Runtime_Handler:459)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:853)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173)
... 40 more
|#]

Cause

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