NameNotFoundException Received While Submitting Request XML To ASAP 7.0.2 (Doc ID 1389718.1)

Last updated on JULY 05, 2013

Applies to:

Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.
***Checked for Currency 05-07-2013***

Symptoms

After installing ASAP 7.0.2, unable to submit work order requests to ASAP.

Following errors were observed in Weblogic logs:

<16-Dec-2011 9:31:08,841 EST AM> <ERROR> <jdbc.JdbcRequestManagerFactory> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <Cannot lookup RPC DataSource>
javax.naming.NameNotFoundException: Unable to resolve 'System.SVT2.ApplicationType.ServiceActivation.Application.1-0;7-0;ASAP.Comp.RPCDataSource'. Resolved 'System.SVT2.ApplicationType.ServiceActivation.Application.1-0;7-0;ASAP.Comp'; remaining name 'RPCDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.mslv.asap.activation.srp.dao.jdbc.JdbcRequestManagerFactory.<init>(JdbcRequestManagerFactory.java:35)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
.....
......




<16/12/2011 9:04:18 AM EST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'SVT2.RPCDataSource' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)

at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace

Caused By: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource
at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:301)

at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:75)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:131)
at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:686)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:230)
Truncated. see log file for complete stacktrace
>


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