AnsweredAssumed Answered

weblogic deployment

Question asked by Tahir Ahmed on Dec 2, 2016
Latest reply on Dec 6, 2016 by Tahir Ahmed

Hello,

 

Aveksa 6.9 Installed on weblogic, after a application server restart the aveksa is unable to load properly. Have checked the data-sources and re-created them again, but error persists. Any insights to resolve, much appreciated.

 

 

12/02/2016 14:41:48.162 INFO ([ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)') 
[com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization Start ********************
12/02/2016 14:41:48.186 INFO ([ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)')
[com.aveksa.migration.jdbctool.AveksaSystemCfg] Loaded Aveksa_System.cfg from aveksa.war/WEB-INF directory
12/02/2016 14:41:48.190 ERROR ([ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)')
[com.aveksa.migration.jdbctool.CheckDatabase] Unable to get the avdb datasource javax.naming.LinkException:
[Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jdbc.avdb' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/avdb']; Link Remaining Name: 'jdbc/avdb'
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:104)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:884)
at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:187)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:132)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)

Outcomes