Issue With Ftp Proxy Services Starting Up. Errors like JMSPool:169803, BEA-381602

(Doc ID 1433974.1)

Last updated on AUGUST 13, 2016

Applies to:

Oracle Service Bus - Version 10.3.1 and later
Information in this document applies to any platform.

Symptoms


We have a lot of SFTP, FTP and also FILE based messaging proxies services. We've recently done a deployment of a new OSB Project jar which included more FILE based proxies, upon restarting those proxies and others in other project jars has the same exception, they all want to use the jms resource, but its not available until the managed server is in a running mode, but it can't get to a running mode as it just keeps looping around between admin mode and fails to startup. Below is the error we are facing:


####<Mar 8, 2012 9:42:11 AM GMT> <Error> <WliSbTransports> <albmzs2> <alsbppdManagedServer11> <[ACTIVE] ExecuteThread: '0' for q
ueue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1331199731005> <BEA-381602> <Error encountered while polling
the resource for the service endpoint ProxyService$SynapseII-InstrumentPrices$ProxyServices$MdmInstrumentContractSender: javax.
jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory weblogic.wlsb.jms.transporttask.QueueConnectionFacto
ry failed: weblogic.jndi.internal.AdminModeAccessException: Unable to resolve 'QueueConnectionFactory'. Resolved 'weblogic.wlsb.
jms.transporttask'; remaining name ''
javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory weblogic.wlsb.jms.transporttask.QueueConnectio
nFactory failed: weblogic.jndi.internal.AdminModeAccessException: Unable to resolve 'QueueConnectionFactory'. Resolved 'weblogic
.wlsb.jms.transporttask'; remaining name ''
at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:29)
at weblogic.deployment.jms.JMSConnectionHelper.lookupConnectionFactory(JMSConnectionHelper.java:485)
at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:268)
at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:184)
at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:503)
at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:353)
at weblogic.deployment.jms.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:247)
at com.bea.wli.sb.security.SecurityModuleImpl$5.run(SecurityModuleImpl.java:544)
at com.bea.wli.sb.security.SecurityModuleImpl$5.run(SecurityModuleImpl.java:542)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at com.bea.wli.sb.security.SecurityModuleImpl.runAlsbPrivilegedAction(SecurityModuleImpl.java:399)
at com.bea.wli.sb.security.SecurityModuleImpl.createJmsConnection(SecurityModuleImpl.java:547)
at com.bea.wli.sb.transports.poller.PollEngine.initJMSArtifacts(PollEngine.java:86)
at com.bea.wli.sb.transports.poller.TransportTimerListener.timerExpired(TransportTimerListener.java:74)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

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