Jboss Migration from 4.0.5 to 4.2.3 (getting context.lookup = NULL)

[Hitesh Thakkar]

Hi Everyone,

my application with same code and abc-ds.xml is working fine on Jboss 4.0.5 but if i am deploying it on 4.2.3, i get some error in my login page, i found root cause to be:

getting ds=NULL in following line

    

try {

              context = new  InitialContext();
              System. out .println( "2" );
             ds = (DataSource)context.lookup( "java:abc" );
              System. out .println( "3" );
              if (ds== null )
  {
  System. out .println( "DS is Null" );
  }
  else {
  System. out .println( "DS is not Null" );
  }

i get output as:
2
3
DS is Null

my abc-xml.ds is as follows: (userid and password , all data in the datasource are correct)

<datasources>
  <local-tx-datasource>
    <jndi-name>abc</jndi-name>
    <connection-url>jdbc:oracle:thin:@machine:1521:webdev</connection-url>
    <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
    <user-name>id</user-name>
    <password>password</password>
 
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
 
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
    <metadata>
      <type-mapping>Oracle9i</type-mapping>
    </metadata>
    <min-pool-size>0</min-pool-size>
    <max-pool-size>10</max-pool-size>
  </local-tx-datasource>
</datasources>

but if i am using

 Connection conn = DriverManager.getConnection(url, user, password);

instead of connecting via jndi, its getting connected and application is working fine.

Please, reply if you have any clue.
NOTE: my abc is getting bounded in both Jboss, but giving NULL in Jboss 4.2.3

[Jaikiran Pai]

Are you packaging any JBoss specific jar files in your application (for ex: jboss-common-core.jar). If yes, remove them from your application packaging.

[Hitesh Thakkar]

hey Jaikiran Pai

Thanks alot, i was stuck to this from last one week.

its working now.

If possible please can you let me know why it was giving issue.
Thanks & Regard,
Hitesh Thakkar.

[Jaikiran Pai]

Hitesh Thakkar wrote:
If possible please can you let me know why it was giving issue.

It's a typical classloading issue, although in this case it doesn't result in the usual ClassCastException. More on classloading issues can be found here