Thanks for the reply.
Both the client and the server is on same VM and database is on remote machine.
I have already gone through that link you provided to me and still I am having the same problem.
Ok, then I assume you are doing a straight lookup of a DataSource...in a J2EE client, application client, or a Application component. What I don't understand, and what you should kind of question is...why the property stuff?
If you are actually running in a EJB, there should be no need for this right?
You can do
InitialContext initCtx= new InitialContex();
with no worries...right?
If not, then you are probably trying to access a DS outside of the container. Which means you want remote access to a datasource...
So, which is it?
Post your datasource configuration file.
I have solve that problem because I was trying to get the DataSource object from out side the container in a custom Java File. NOw I got the connection object within the container.
Actually I was integrating connection pooling of JBoss with TopLink and I am still fighting with it because toplink is not able to get that JNDI lookup but I think it is a matter of TopLink not JBoss so I am looking for it in TopLink forum but if you can provide any help to me on it then it will be very helpful to me.
Now I am not having issue with connection pooling of JBoss because I executed a sample query with the connection object and it is working fine.
Thanks to you for your help.