[jboss-jira] [JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL

[Igor Shulika (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944073#comment-12944073 ] 

Igor Shulika commented on WFLY-2898:
------------------------------------

Eduardo,
I found the root cause of the issue - JavaMelody SessionListener.
My web.xml file has the net.bull.javamelody.SessionListener registered, without it application is deploying normally on WildFly.
Here is the SessionListener section:
  <!-- Java Melody Listener -->
  <listener>
    <listener-class>net.bull.javamelody.SessionListener</listener-class>
  </listener>
I'm using the latest 1.49.0 version of JavaMelody.

                
> JNDI Name lookup of the DataSource returns NULL
> -----------------------------------------------
>
>                 Key: WFLY-2898
>                 URL: https://issues.jboss.org/browse/WFLY-2898
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Naming, Web (Undertow)
>    Affects Versions: 8.0.0.CR1, 8.0.0.Final
>            Reporter: Igor Shulika
>            Assignee: Eduardo Martins
>         Attachments: 1.PNG, 2.PNG, 3.PNG, jaffa-oracle-driver-6.0.0.Alpha2-SNAPSHOT.jar
>
>
> Hi,
> I'm having a problem to obtain DataSource using JNDI Name lookup.
> Please see my code below:
> Connection connection = null;
> DataSource dataSource = null;
> try { 
>   final Context initContext = new InitialContext(); 
>   dataSource = (DataSource) initContext.lookup("java:/MyDataSource");  connection = dataSource.getConnection(); 
> } catch (Exception e) { 
>   LOGGER.error(e); 
> } 
> I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14).
> Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira