Weblogic datasource disappears from JNDI tree

Question

We are using weblogic version 12C. Steps to reproduce the issue: -

1. Create the datasource.
2. Deploy the application to weblogic.
3. Application wor

Answer 1

I had the same problem. Adding destroyMethod="" fixed it for me.

Apparently if there is no destroyMethod, Spring tries to determine what the destroy method is. This is apparently causing the datasource to be closed and the JNDI key to be removed from the tree. Changing it to "" forces it to not look for a destroyMethod.

@Bean(destroyMethod = "")
public DataSource dataSource() throws NamingException{
    Context context = new InitialContext();
    return (DataSource)context.lookup("jdbc.mydatasource");
}

Answer 2

WebLogic Server: Most Recent Configuration Changes get Rolled Back after an Admin Server Restart (Doc ID 1479592.1) To BottomTo Bottom

In this Document Symptoms Cause Solution APPLIES TO:

Oracle Weblogic Server - Version 9.2.3 and later Information in this document applies to any platform. SYMPTOMS

The most recent domain configuration changes get rolled back after an admin server restart.

After setting debug level logging, you can also see the following messages in the server logs at the time of the issue:

<> <000000>

ervers/domain_bak/config_prev_bak' to: /data/bea92/user_projects/domains/ko_webapp_domain/servers/domain_bak/config_prev>

CAUSE

A config_bak directory is present in the domain_bak directory. This causes the previous config.xml to replace the current config.xml.

SOLUTION

Remove the config_Bak directory.