Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
Developing Analytics Applications
Reports on JBoss 5.2 JNDI "env not bound" error
Migrateduser
We have integrated our BIRT reports within our web application. The jndi name is configured, and the integration works fine on Tomcat and Websphere.
While deploying it on Jboss 5.2 we get the error "env not bound". We have given the jndi name as "jdbc/examplejndi".
The rptdesign reports have jndiparameter as "java:comp/env/jdbc/examplejndi" which throws error "env not bound".
The same application works on Jboss 6 and 7 and also on tomcat and websphere.
If I change the jndi configuration in the rptdesign to "java:jdbc/examplejndi", it works on jboss but fails on tomcat and websphere.
The "java:comp/env/jdbc/examplejndi" works on sevlets/jsps/code-base (even on Jboss 5.2), though it fails when we given this setting on rptdesign.
We have copied the birt plugins into WEB-INF/lib, and web.xml defines default parameters for BIRT.
Exception traces gives NullPointerException, which I think ebcause of the default connection if jndi fails.
We have to support tomcat/websphere and jboss, and looking for a common solution. So the possibility of changing the jndi configuration for every deployment is not possible.
I have tried various things available on the web, though I couldnt find any successful solution. It seems the BIRT logs we are using BaseClassLoader, which doesnt specify the context of the application. In tomcat deployment we see BIRT logs showing WebAppClassLoader and displying the context of the application.
Any help will be highly appreciated.
Find more posts tagged with
Comments
There are no comments yet