[jboss-jira] [JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL
Emeric Vernat (JIRA)
issues at jboss.org
Thu Feb 13 07:49:29 EST 2014
[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944226#comment-12944226 ]
Emeric Vernat commented on WFLY-2898:
-------------------------------------
Note that JavaMelody currently does not recognize WildFly, so it considers WildFly like Tomcat and not like JBoss.
(But your JavaMelody log above says that this works at first).
It would help to see your JavaMelody filter logs, just after the JavaMelody listener logs.
This would show if the WildFly Server Info is one of the following (and if JavaMelody could consider WildFly like JBoss):
- "Undertow", like in 8.0.0.CR1
- or "WildFly 8.0.0"
- or "WildFly 8.0.0 (Ex-JBoss AS)"
> 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
More information about the jboss-jira
mailing list