Please file a bug report on this.
This occurs when another deployment is using stale classes from deployment which has been replaced. In this case, the jdbc driver container deployment has presumably been redeployed which the datasource configuration has not.
Has this been posted as a bug? I have searched the sourceforge bug page but can't find a reference to it.
I ask because I am having a similar problem in JBoss 3.2.3 (i.e. I have an MBean in a SAR and an app in an EAR that share a common jar... everything works fine from a cold startup until you try and hot re-deploy the SAR... the NPE is thrown as described above).
Note the problem goes away if I put the shared jar in server/default/lib instead, but isn't this generally bad practice?
Thanks in advance.
Advance thanks for your help...
I can able to deploy ny EJB application in JBoss3.2.1 under Linux7.3 ,NetBeans3.6IDE.But Iam unable to do it in JBoss3.2.3.Is there any changes I have to made.
Iam getting Exception :jmx:hostname:rmi not bound....
Need ur help..